Frequent kong ingress controller leader re-election happening

[chowmean]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

Hi in our kong setup, we have seen multiple leader re-election happening and thus pushing our memory for few min. We have also seen instances when someone the kong proxy which has KIC running starts giving 503.

Need some assistance here as to what to look. Is there anything on the lease side that we should check? Memory and CPU spikes but are in controller range.

We have around 1000 routes configuration.

Seeing this a lot in our logs and nothing major apart from this:

leaderelection.go:258] successfully acquired lease kong-public/kong-ingress-controller-leader-kong-public

We are running with DB mode and KIC in each kong pods.

Expected Behavior

There should not be so many re-elections.

Steps To Reproduce

NA

Kong Ingress Controller version

2.7

Kubernetes version

1.25

Anything else?

Kong Proxy version is 3.0

[tao12345666333]

Please run kubectl get events -n <your KIC's namespace>, and show the events.

[rainest]

We use the standard upstream controller-runtime and client-go leader election utilities. KIC won't behave any differently than any other standard Kubernetes leader election controller would.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.