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

Question: Getting Deprecated API error for ingress. #99

Closed
collbrain opened this issue Apr 29, 2020 · 3 comments
Closed

Question: Getting Deprecated API error for ingress. #99

collbrain opened this issue Apr 29, 2020 · 3 comments
Labels
question Further information is requested

Comments

@collbrain
Copy link

I am getting following error for ingress, understand that have to change the api but i am running 1.14. Should i changed for that as well ?. Basically, is popeye version aware ?

[POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead.

@derailed
Copy link
Owner

@collbrain Popeye is not version aware in the sense that we don't check the cluster version prior to sanitization. Popeye does expect a recent k8s version. Since 1.16 deprecated apis, the sanitizers will report on these deprecation warnings. As a general rule especially in light of CVEs it is a recommended practice to keep your cluster closer to the latest k8s as possible. Does this make sense?

@collbrain
Copy link
Author

Is there an older branch that i could pull for 1.13 and 1.14 ?.

The reason is i am running gke cluster, one is 1.14 and prod is 1.13. I don't have permission to upgrade or don't see this getting upgraded in 2-3 months. Meanwhile wanted to check popeye on how it works...

@derailed
Copy link
Owner

derailed commented May 8, 2020

@collbrain I don't recall which version of Popeye added the deprecation checks. I think just about the time k8s 1.16 came out. I would recommend staying up with the latest Popeye if you can and lower the deprecation warnings (see spinach.yml) to info until you have a change to upgrade your clusters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants