-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Checksum changing without config changing #3489
Comments
Some of our Ingress objects are having their I would not have expected those changes to result in an nginx reload (and the corresponding drop of tcp connections) |
@mikebryant please add the flag |
(After some conversation with @aledbf - many thanks!) - looks like this is because the |
Hi, can I ask what is the status of this? I see the merged PR, but the issue remains opened. We actually suffer from ingress nginx being reloaded too often and killing connections even if there are no changes in config. Fixing this would resolve our problems, right? |
Closing. Please update to 0.22.0. Reopen if the issue persist after the upgrade |
It seems I have like this issue, mentioned above.
ingress-nginx/controller:v1.7.0 |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): checksum
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version: 0.21.0
Kubernetes version (use
kubectl version
):Environment:
uname -a
):What happened: nginx.conf is being changed, and nginx reloaded, but there appears to be no actual change
What you expected to happen: For the config not to reload if there's no change
How to reproduce it (as minimally and precisely as possible):
Unsure
Anything else we need to know:
Debug, from a controller pod, at different times:
The text was updated successfully, but these errors were encountered: