← Problem Library
K8s L6 K8S 1513 · 11 min

A Gateway API route attaches and still serves the old backend because one controller worker reuses the stale parent generation cache

The route status is updated, but a cached parent generation on one worker keeps the old backend target active.

K8sPlatform ReliabilityLevel 6Pro11 min
Scenario

A backend switch never takes effect on one gateway worker after a Gateway API change.

What to check first
  • Identify the primary failure signal in the The Route Moved to the New Target and One Controller Worker Kept Reading the Previous Generation's Stage Directions 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 generation caching before forcing full rollouts.

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.