← Problem Library
K8s L6 K8S 1461 · 13 min

A Cilium policy allows the namespace and still blocks node-local DNS because the host firewall evaluates before pod identity is restored

DNS breaks only on one hardened node pool even though namespace policy looks correct.

K8sPlatform ReliabilityLevel 6Pro13 min
Scenario

Pods on one node pool lose DNS right after node-local DNS and host firewall hardening are enabled together.

What to check first
  • Identify the primary failure signal in the The DNS Packet Left the Pod and the Host Firewall Judged It Too Early scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Trace host-path identity restoration before widening namespace policy exceptions.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.