-
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
Too many config reloads #2596
Comments
@Stono please add the flag |
@aledbf it appears to be because of the order of the vhosts:
It's the same number of hosts, just ordered differently. |
I suggest some sort of sort by id on the bit which renders these upstreams |
@Stono please use |
OK, give me a few mins |
It still reloads @aledbf - but nothing in the log output:
|
@Stono please use |
Same again!
|
Any ideas what it may be? I'm going live with a bunch of stuff on Monday so wondering if we're going to be able to fix it by then? |
Hey hey @aledbf
Our internet ingress controllers will be handling circa 200 ingress hosts. Most of these apps continuously deploy thus updating the ingress metadata labels with the current release version, even if the ingress
spec
hasn't actually changed.Unfortunately updates to ingress labels, still result in a backend reload in nginx:
We only have about 10 services on here at the moment, and a backend reload takes a fair bit of time to validate such a big config. I'm concerned and trying to pre-empt when it gets to 200 or so, and they're happening a lot, we're going to hit some issues.
In summary, it'd be great if ingress-nginx only performed a backend reload when the
spec
section of the ingress object has changed, because that's the bit that really matters!The text was updated successfully, but these errors were encountered: