← Problem Library
K8s L4 K8S 1568 · 10 min

An admission webhook manifest is updated and one namespace still ignores it because the old failurePolicy survives in a shadow copy

The live manifest is strict, but one shadow object still carries the earlier failurePolicy and gets selected by the API server cache.

K8sPlatform ReliabilityLevel 4Pro10 min
Scenario

One namespace still ignores the webhook after the manifest was hardened.

What to check first
  • Identify the primary failure signal in the The Rulebook Was Tightened and One Inspector Pulled the Carbon Copy From the Drawer Marked Drafts 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 shadow admission objects before widening 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.