← Problem Library
K8s L4 K8S 1608 · 8 min

A webhook timeout update lands and one API server still waits because the admission cache keeps the previous timeout object

The live config is updated, but one API server still caches the old timeoutSeconds object.

K8sPlatform ReliabilityLevel 4Pro8 min
Scenario

One API server still waits too long after a webhook timeout update.

What to check first
  • Identify the primary failure signal in the The New closing time was posted on the door and One attendant still followed the laminated sign left from the previous shift scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Inspect cached webhook objects before editing selectors.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.