-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Breaking Change with Ingress Controller 1.3.0 #11192
Comments
I see similar errors and get a 503 on some ingress routes.
Seems to be an DaemonSet issue, as it only pops up on DS deploys. Edit: Actually I'm wrong. The ingress seems to work as DP and DS, but the leader election still is not working. |
So I tried to add it manually but there seem to be no impact, even after a restart. Added to - apiGroups:
- coordination.k8s.io
resources:
- leases
verbs:
- list
- watch Edit: Okay seems to be a bit more effort than that => kubernetes/ingress-nginx@cf4dca8 |
Problem persists in chart version |
@aeimer - verbs:
- create
- update
- get
- list
- watch
apiGroups:
- coordination.k8s.io
resources:
- leases Restart is not required. |
Rollback to previous version :( |
fixed by #11454 |
@rpf3 unfortunately only partially |
Also seeing this in the latest chart 9.2.21:
|
oops, thank you, 9.3.4 is the latest |
Had the following error
Had to add the following in ClusterRole > nginx and everything worked. - verbs:
- list
- watch
apiGroups:
- coordination.k8s.io
resources:
- leases
- verbs:
- list
- watch
apiGroups:
- discovery.k8s.io
resources:
- endpointslices |
Name and Version
bitnami/nginx-ingress-controller 9.2.20
What steps will reproduce the bug?
Are you using any custom parameters or values?
N/A
What is the expected behavior?
The controller pod should log that the leader election occurred without issue.
What do you see instead?
The leader election is failing due to a change in the upstream app version 1.3.0
Additional information
https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.3.0
The text was updated successfully, but these errors were encountered: