← Problem Library
K8s L5 K8S 1432 · 14 min

A Gatekeeper rollout looks healthy and one forbidden object still slips

The constraint is correct, yet one API path exits admission early after another webhook times out under load.

K8sPlatform ReliabilityLevel 5Pro14 min
Scenario

A small subset of forbidden objects appears only during admission load spikes after the webhook stack grows.

What to check first
  • Identify the primary failure signal in the The Policy Was Ready and Another Webhook Fell Over First and Sent the Request Down a Shorter Hallway 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 full admission order and failure policy before weakening constraints or restarting Gatekeeper.

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.