Scenario
One Ingress path still returns 404 after annotation cleanup.
An Ingress change is correct and one path still returns 404 because the rewrite annotation key keeps the retired prefix
The controller is current, but one annotation still uses the earlier prefix format.
What to check first
- Identify the primary failure signal in the The New Route Board Was Fixed at the Platform and One conductor Still Read the Arrow Sticker From the Sign It Replaced 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
Check annotation keys before changing controller config.
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