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

Kubernetes v1.19+ ingress and certificates deprecation issues #1249

Closed
lilic opened this issue Oct 5, 2020 · 2 comments · Fixed by #1260
Closed

Kubernetes v1.19+ ingress and certificates deprecation issues #1249

lilic opened this issue Oct 5, 2020 · 2 comments · Fixed by #1260
Assignees
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-2.0

Comments

@lilic
Copy link
Member

lilic commented Oct 5, 2020

We get the following warning when using v1.19 kuberentes cluster:

Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:32:58Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}

Warning msg when running kube-state-metrics:

W1005 14:47:25.621123 93191 warnings.go:67] certificates.k8s.io/v1beta1 CertificateSigningRequest is deprecated in v1.19+, unavailable in v1.22+; use certificates.k8s.io/v1 CertificateSigningRequest
W1005 14:47:25.706963 93191 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W1005 14:47:25.757402 93191 warnings.go:67] certificates.k8s.io/v1beta1 CertificateSigningRequest is deprecated in v1.19+, unavailable in v1.22+; use certificates.k8s.io/v1 CertificateSigningRequest
W1005 14:47:25.758390 93191 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

We should migrate to newer versions of CertificateSigningRequest and Ingress.

@lilic lilic added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Oct 5, 2020
@tariq1890
Copy link
Contributor

We should incorporate these changes into the release-2.0 branch

@lilic
Copy link
Member Author

lilic commented Oct 6, 2020

Sounds good, created a label for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-2.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants