Scenario
One sidecar keeps using the old destination subset after a rollout.
An Istio subset update rolls out and one sidecar still uses the old destination because outlier detection keeps the retired subset name
The destination rule is current, but one sidecar still scores endpoints under the prior subset name cached by outlier detection.
What to check first
- Identify the primary failure signal in the The Team Bench Was Renamed on the Match Sheet and One Coach Kept Calling Plays for the Label Printed on Last Week's Clipboard 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
Inspect cached subset names before restarting the proxy.
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