ingress-nginx
ingress-nginx copied to clipboard
kubernetes
Multiple ingress update cause reloaded N times of nginx instead of just one time for all
There are 5 ingress which always been upgraded via using Helm.
Just wondering even If I upgrade 5 ingress's annotations, can it be just reloaded 1 time only?
@Taymindis: This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/remove-kind bug /kind support
Please provide information that was requested in the new issue template.
5 ingress upgraded means 5 instances of ingress-nginx controller or 5 ingress objects. Looks more like ingress objects but just want to confirm.
If it is ingress objects, did you apply 5 yaml files at once or one by one.
What is the problem you want to solve ?
Hi @longwuyuan ,
We have our own helm which iterates to create/upgrade ingress objects.
when we modify something on values that apply to relevant ingress object, the N ingress object affected for change will trigger N time of relaod.
I understand that if one ingress object changed, it will RELOAD, but what if I have 30 ingress objects which actually need to reload 30 times from ingress controller?
Solution:
Can it be done by just 1 reload in specific amount of time detection of change?
Someone attempted a hack for a custom behaviour related to disabling admission webhook temporarily, if I am not wrong. They were guided by an expert. While the admission webhook was disabled, the user changed objects and after completing all changes, they re-enabled admission.
I mentioned above incident because there may be ways to achieve it, but there is no feature as per your description. Let us see if other people have comments.
I'm observing the same issue in our multiple ingress controller setup. To make things a bit more complicated the memory usage increases (and it is not flushed) on every backend reload (just like described in #8166).
@longwuyuan @pdefreitas
The nginx-ingress-controller seemed consuming memory without releasing it, there are just 2 ingress objects only so far.
A complete event history and a complete k8s state is needed to make any comments about memory consumption. Please open a new issue to report a new problem. You originally asked for one single reload of nginx in response to multiple config changes. That is a different issue compare from this high-memory consumption issue.
A complete event history and a complete k8s state is needed to make any comments about memory consumption. Please open a new issue to report a new problem. You originally asked for one single reload of nginx in response to multiple config changes. That is a different issue compare from this high-memory consumption issue.
Thanks for reminding, I have reported new issue
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue or PR with
/reopen - Mark this issue or PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue or PR with
/reopen- Mark this issue or PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.