← Problem Library
K8s L6 K8S 1509 · 11 min

A Gateway API canary route attaches and all traffic still lands on stable because the controller cached the old parent status

The route object is present, but one worker keeps reconciling against a stale parent attachment snapshot.

K8sPlatform ReliabilityLevel 6Pro11 min
Scenario

Canary weights never take effect on one controller revision after a Gateway API migration.

What to check first
  • Identify the primary failure signal in the The Canary Route Took Its Place 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
  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 parent status caching before changing weights again.

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.