Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EKS resources are considered unused #62

Closed
sheerun opened this issue Dec 3, 2019 · 1 comment
Closed

EKS resources are considered unused #62

sheerun opened this issue Dec 3, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@sheerun
Copy link

sheerun commented Dec 3, 2019

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:

  1. Create cluster with EKS
  2. Run popeye

Expected behavior

Default setup on EKS has no warnings

@derailed derailed added the bug Something isn't working label Dec 3, 2019
@derailed
Copy link
Owner

derailed commented Jan 7, 2020

@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!

@derailed derailed closed this as completed Jan 7, 2020
derailed added a commit that referenced this issue Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants