A library namespace applies a strict egress NetworkPolicy that blocks nearly all outbound traffic. Name resolution for Services immediately fails. What egress allowance is typically still required?
Select an answer to reveal the explanation.
Short Explanation
Lock the exits too hard and nobody can even look up phone numbers — leave a DNS path to CoreDNS on port 53.
Full Explanation
Pods resolve Service names via cluster DNS. An egress policy that omits CoreDNS/kube-dns (commonly UDP/TCP 53 toward the DNS Service or Pods) breaks resolution even when the intended application ports are later allowed. etcd and metrics-server access are not substitutes for DNS egress.