One node still routes wrong after Cilium restore and CIDR recycling.
A Cilium node restore completes and one service still routes wrong because the ipcache keeps the retired pod CIDR owner
Endpoints are healthy, but one node still decorates traffic using the old owner mapping for a reclaimed pod CIDR.
Scenario
What to check first
- Identify the primary failure signal in the The New Street Register Reached City Hall and One clerk still assigned houses using the neighborhood map printed before the annex swap 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 ipcache ownership before draining the node.
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