Scenario
One proxy still allows the old SAN after mesh egress fixes.
A mesh egress restriction is correct and one proxy still allows the old SAN because the warmup cache restores the retired list
The policy is updated, but one proxy still rebuilds an earlier SAN allowlist during warmup.
What to check first
- Identify the primary failure signal in the The New border rulebook arrived at the checkpoint and One guard still reopened the notebook containing the host list from the rehearsal 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 warmup state before rolling the mesh.
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