Scenario
One ingress class begins rejecting previously valid snippets after a controller class rename.
An ingress snippet policy blocks only one class
The annotation is unchanged, but policy evaluation keys off the controller class name and only one class now fails admission.
What to check first
- Identify the primary failure signal in the The Snippet Stayed the Same and the Controller Changed Its Last Name 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
Compare validating policy selectors before removing the snippet or disabling admission.
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