Skip to content
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

[Bug]: NIC generates AddedOrUpdated events for unchanged mergeable ingress resources #7223

Open
dareste opened this issue Jan 27, 2025 · 1 comment
Labels
bug An issue reporting a potential bug

Comments

@dareste
Copy link
Contributor

dareste commented Jan 27, 2025

Version

3.7.0

What Kubernetes platforms are you running on?

Other

Steps to reproduce

  1. Deploy a structure of mergeable ingress resources with 1 master and 500 minions.
  2. Change one of the minions.
  3. Watch the AddedOrUpdated events not only for the changed minion, but for all the minions and the master ingress resource.

The events can be observed both in the NIC logs, or in k8s via the kubectl get events -w command. In the logs, such events will appear immediately after the change. The events, however, will be slowly populated and the stream will last for ~3m (see attached file - this might change depending on the platform tested). During that time, nginx-ingress binary will show a slightly higher CPU usage when compared to the baseline.

Moreover, by comparing the resourceVersion values of the 501 objects, it can be confirmed that the only altered value belongs to the modified minion.

k8s-events-500-minions.txt

@dareste dareste added bug An issue reporting a potential bug needs triage An issue that needs to be triaged labels Jan 27, 2025
Copy link

Hi @dareste thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

@AlexFenlon AlexFenlon removed the needs triage An issue that needs to be triaged label Jan 27, 2025
@shaun-nx shaun-nx moved this from Todo ☑ to Prioritized backlog in NGINX Ingress Controller Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue reporting a potential bug
Projects
Status: Prioritized backlog
Development

No branches or pull requests

2 participants