Skip to content

Upgrading ingress add-on (ingress-nginx) to v1.12.1 #20610

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

Open
awarberg opened this issue Apr 10, 2025 · 1 comment
Open

Upgrading ingress add-on (ingress-nginx) to v1.12.1 #20610

awarberg opened this issue Apr 10, 2025 · 1 comment

Comments

@awarberg
Copy link

What Happened?

I am attempting to reproduce an issue with a configuration snippet that occurred after upgrading to ingress-nginx v1.12.1. I am using minikube v1.35.0 with the ingress add-on, but the ingress-nginx version is only v1.11.3 and I can't reproduce the issue.

What does the timeline look like to update the ingress add-on or is there another way I can update ingress-nginx myself?

Thanks for the help.

Attach the log file

PS C:> minikube version
minikube version: v1.35.0
commit: dd5d320-dirty
PS C:> kubectl get deployment ingress-nginx-controller -n ingress-nginx -o jsonpath='{.spec.template.spec.containers[0].image}'
registry.k8s.io/ingress-nginx/controller:v1.11.3@sha256:d56f135b6462cfc476447cfe564b83a45e8bb7da2774963b00d12161112270b7

Operating System

None

Driver

None

@awarberg
Copy link
Author

While I didn't manage to upgrade the add-on, I did find the likely cause of the error I was trying to reproduce - maybe it can be helpful to someone:
kubernetes/ingress-nginx#12648

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

No branches or pull requests

1 participant