Scenario
One cross-namespace route fails after ReferenceGrant rollout.
A ReferenceGrant is applied and one cross-namespace route still fails because the parent namespace cache keeps the retired label key
The grant exists, but one gateway worker still filters namespaces using a label key from before policy normalization.
What to check first
- Identify the primary failure signal in the The Permission Slip Was Filed Correctly and One Gate Agent Kept Looking for the Stamp Used on the Old Uniform 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 namespace selection cache before widening the grant.
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