← Problem Library
K8s L6 K8S 1560 · 12 min

A service mesh revision switch succeeds and one workload still routes to the old control plane because its sidecar bootstrap retains the retired discovery host

Revision labels are correct, but one workload keeps using the previous discovery address embedded in its bootstrap config.

K8sPlatform ReliabilityLevel 6Pro12 min
Scenario

One workload remains on the old control plane after a mesh revision switch.

What to check first
  • Identify the primary failure signal in the The City Opened the New Control Tower and One Aircraft Took Off Using the Frequency Card That Was Taped Beside the Cockpit Window on the Old Fleet 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 sidecar bootstrap state before relabeling namespaces 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.