-
Notifications
You must be signed in to change notification settings - Fork 16.7k
[stable/nginx-ingress] Updating the chart without changing nginx image version break the ingress #16809
Comments
@ChiefAlexander @taharah could you please take a look? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Toc toc |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
@ChiefAlexander @taharah can I have a feedback? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
I was in vacation... :( @ChiefAlexander @taharah |
Describe the bug
If you update the chart without changing the nginx image the pods stop to working.
Version of Helm and Kubernetes:
K8s v1.12.7
Helm v2.14.3
Which chart:
v1.17.1
What happened:
I had nginx-ingress installed (nginx-ingress-1.15.0, v0.24.1).
I updated the chart (nginx-ingress-1.17.1, v0.24.1).
The nginx version was not updated by choice (due to this problem kubernetes/ingress-nginx#4305).
The nginx pods have begun to generate these errors:
And then I found this error in the pods:
Basically the chart update changed the name of the secret. The pods had the old and stopped working. By restarting them they took the secret correctly and restarted to work properly.
What you expected to happen:
If I update only the chart I would like the pods to continue to work
How to reproduce it (as minimally and precisely as possible):
Redo the same step that I did.
Anything else we need to know:
The text was updated successfully, but these errors were encountered: