Scenario
Forbidden resources appear only during admission load spikes.
A Gatekeeper rule looks healthy and one forbidden object still lands because an earlier mutating webhook times out first
The constraint is correct, but one admission path exits before Gatekeeper validation runs.
What to check first
- Identify the primary failure signal in the Another Webhook Fell First and Closed the Hall Before Validation scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Trace webhook order and failure policy before weakening the constraint.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field