From d1b472319a24e95ad9b844151a5d41aa29222ff7 Mon Sep 17 00:00:00 2001 From: Yasar Rahman Date: Tue, 13 Oct 2026 19:45:30 +0500 Subject: [PATCH] fix(vpa): explain that the webhook waits add up within one request failurePolicy Ignore applies only after the timeout; the Pod CREATE webhooks are called sequentially within one request, so their waits accumulate and can pass the request deadline. Assisted-by: LLM Signed-off-by: Yasar Rahman --- .../system/vertical-pod-autoscaler/values.yaml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/packages/system/vertical-pod-autoscaler/values.yaml b/packages/system/vertical-pod-autoscaler/values.yaml index b870049be..a828ee95b 100644 --- a/packages/system/vertical-pod-autoscaler/values.yaml +++ b/packages/system/vertical-pod-autoscaler/values.yaml @@ -39,12 +39,14 @@ vertical-pod-autoscaler: 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. + # namespace with failurePolicy Ignore and, by default, a 30s timeout. Ignore only + # applies after the 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), the API server + # still waits the full 30s. The Pod CREATE webhooks are called one after another within + # one request, so their waits add up; past the request's deadline the creation fails + # with "context deadline exceeded", including for the CNI's own DaemonSet pods (#3125). + # A mutation takes milliseconds; 5s keeps slow responses working and keeps the total + # wait well inside the deadline. webhook-timeout-seconds: 5 resources: limits: