-
Notifications
You must be signed in to change notification settings - Fork 2k
Open
Bug
0 / 10 of 1 issue completed
Copy link
Labels
bugAn issue reporting a potential bugAn issue reporting a potential bug
Description
Version
3.7.0
What Kubernetes platforms are you running on?
Other
Steps to reproduce
- Deploy a structure of mergeable ingress resources with 1 master and 500 minions.
- Change one of the minions.
- 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.
palmerabollo
Sub-issues
Metadata
Metadata
Assignees
Labels
bugAn issue reporting a potential bugAn issue reporting a potential bug
Type
Projects
Status
Prioritized backlog