Scenario
One node still sends requests to an old backend after kube-proxy replacement rollout.
A Cilium kube-proxy replacement rollout finishes and one node still sends traffic to the old backend because the revnat slot was never repinned
Service state is updated, but one node keeps using a revnat entry created before the backend move.
What to check first
- Identify the primary failure signal in the The New Route Table Was Issued and One Driver Kept Following the Detour Number Painted on the Barrier From Last Week 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 revnat maps before restarting the whole fleet.
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