Scenario
Canary weight changes never take effect after moving from Ingress to Gateway API on one controller revision.
A Gateway API canary route looks correct and 100 percent of traffic still lands on stable because the controller cached the previous HTTPRoute parent status
The canary route is attached, but one controller worker keeps honoring an old parent status snapshot during reconciliation.
What to check first
- Identify the primary failure signal in the The Canary Route Stood in the Config and the Controller Kept Reading the Last Status Report It Filed Before the Change 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 route parent status and controller cache freshness before editing weights again.
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