fix(vpa): shorten the admission webhook timeout to 5s

The VPA admission controller registers its Pod CREATE webhook in every
namespace with failurePolicy Ignore and a 30s timeout. When its pod is
down and the Service IP blackholes (a cold start after a full cluster
shutdown, before the CNI is back), each Pod creation waits the full 30s
here on top of the other webhooks and fails with "context deadline
exceeded". That includes the CNI's own DaemonSet pods, so the cluster
cannot recover without deleting the webhook configuration by hand.

A mutation takes milliseconds; 5s keeps slow responses working and lets
Ignore actually ignore. Uses the admission controller's documented
--webhook-timeout-seconds flag through the chart's extraArgs.

Refs #3125

Assisted-by: LLM
Signed-off-by: Yasar Rahman <yasar.rehman@gmail.com>
This commit is contained in:
Yasar Rahman committed 2026-11-06 20:06:38 +05:00
1 parent 970191dc8a
commit 291b1fa3c0
1 file changed
+9
@@ -37,6 +37,15 @@ vertical-pod-autoscaler:
prometheus-cadvisor-job-name: cadvisor
admissionController:
extraArgs:
# The admission controller registers its mutating webhook for Pod CREATE in every
# namespace with failurePolicy Ignore and, by default, a 30s timeout. When its pod is
# down and the Service IP blackholes (e.g. a cold start after a full cluster shutdown,
# before the CNI is back), every Pod creation waits the full 30s here on top of the
# other webhooks and fails with "context deadline exceeded" - including the CNI's own
# DaemonSet pods, so the cluster cannot recover by itself (#3125). A mutation takes
# milliseconds; 5s keeps a slow response working and lets Ignore actually ignore.
webhook-timeout-seconds: 5
resources:
limits:
memory: 256Mi