Scenario
Startup succeeds and long-lived service calls fail later under the same FQDN-based egress policy.
A Cilium FQDN policy allows bootstrap package downloads and blocks long-lived...
The domain is allowed initially, yet the later resolver path yields a wider address set the policy never learned.
What to check first
- Identify the primary failure signal in the The Dependency Had More Addresses Than the Bootstrap Resolver Bothered to Mention 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 runtime DNS paths before replacing FQDN policy 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