Scenario
Startup passes and long-lived gRPC calls later begin failing under the same FQDN-based policy.
A Cilium FQDN policy allows startup downloads and blocks steady-state gRPC
Bootstrap succeeds, yet runtime traffic uses a broader set of resolved addresses the policy never learned during startup.
What to check first
- Identify the primary failure signal in the The App Learned the Dependency's First Few Addresses and the Sidecar Introduced the Rest Too Late 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
Compare bootstrap and steady-state DNS paths before replacing FQDN rules with broader CIDRs.
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