Slow boot time on our clusters #2170
Replies: 2 comments
-
The lowest hanging fruit that comes to mind since the considerations of KEP#8 is that we've released
A couple of questions just to understand better your situation:
|
Beta Was this translation helpful? Give feedback.
-
Hi @shaneutt thanks for the answer :) I'm not in the position for upgrading (I can take the new version as an argument pro-upgrading) and I can investigate about using |
Beta Was this translation helpful? Give feedback.
-
Hi,
We have a (what we consider) big cluster. The boot time for kong can be up to 35 seconds. We had probes to restart the pod at 30 secs which made us detect the issue due to the CrashLoopBackOffs.
I've seen some comments and work that could be related:
#1447
https://github.com/Kong/kubernetes-ingress-controller/pull/1742/files#
kubectl get service -A --no-headers | wc -l
4226
kubectl get secrets -A --no-headers | wc -l
11583
kubectl get endpoints -A --no-headers | wc -l
4068
We are running Kong 2.3.2 and Kong IC 1.2
We are still fine by increasing the startupProbe times, but... is there anything else we can do to help to confirm that the changes of the KEP could be beneficial?
Also, what about including a prometheus metric which keeps the boot time? if it grows over time, it's easier to get alerted and work on that.
Beta Was this translation helpful? Give feedback.
All reactions