You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying on AWS, EKS creates some default namespaces popeye complains about them:
Describe the bug
· kube-node-lease................................................................................🔊
🔊 [POP-400] Used? Unable to locate resource reference.
· kube-public....................................................................................🔊
🔊 [POP-400] Used? Unable to locate resource reference.
To Reproduce
Steps to reproduce the behavior:
Create cluster with EKS
Run popeye
Expected behavior
Default setup on EKS has no warnings
The text was updated successfully, but these errors were encountered:
@sheerun Thank you for this report! Indeed there are used internally and Popeye can't pick up the references. So you will have to exclude these using a spinach.yml file. Please see the release notes for 0.6.0 and the example spinach file in this repo. Thank you!
When deploying on AWS, EKS creates some default namespaces popeye complains about them:
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Default setup on EKS has no warnings
The text was updated successfully, but these errors were encountered: