mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-21 12:13:55 +09:00
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 <yasar.rehman@gmail.com>
This commit is contained in:
1 parent
291b1fa3c0
commit
d1b472319a
1 file changed
+8
-6
@@ -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:
|
||||
|
||||
Reference in new issue
Block a user