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

[BUG] - Kubernetes v1.22+ deprecates v1beta1.Ingress API #1488

Closed
iameskild opened this issue Oct 11, 2022 · 1 comment · Fixed by #1489
Closed

[BUG] - Kubernetes v1.22+ deprecates v1beta1.Ingress API #1488

iameskild opened this issue Oct 11, 2022 · 1 comment · Fixed by #1489
Labels
area: k8s ⎈ impact: high 🟥 This issue affects most of the nebari users or is a critical issue type: bug 🐛 Something isn't working

Comments

@iameskild
Copy link
Member

iameskild commented Oct 11, 2022

See k8s v1.22 release notes.

Traefik versions older than 2.5.0 rely on this now deprecated API version. See Traefik 2.5.0 release notes.

This issue was a little tricky to track identify as it was causing trouble for the network. Most recently and most clearly, I witnessed a deployment fail on the very next stage, the Keycloak deployment. Viewing the traefik pod logs, you see the following:

pkg/mod/k8s.io/client-go@v0.20.2/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource (get ingresses.extensions)

Possibly related to:
#1329
#1334
#1415

@iameskild iameskild added type: bug 🐛 Something isn't working impact: high 🟥 This issue affects most of the nebari users or is a critical issue area: k8s ⎈ labels Oct 11, 2022
@iameskild iameskild added this to the Release v0.4.5 milestone Oct 11, 2022
@viniciusdc
Copy link
Contributor

It might also be affecting the recent #1491

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: k8s ⎈ impact: high 🟥 This issue affects most of the nebari users or is a critical issue type: bug 🐛 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants