Three Kubernetes NetworkPolicy Baseline Mistakes That Break Namespace Isolation
A default-deny NetworkPolicy changes how Kubernetes pods communicate by blocking traffic unless explicitly allowed. The article notes that policies are additive and allow-only, and that enforcement depends on the CNI plugin rather than the API object itself. A common failure occurs when a default-deny egress policy is applied without a DNS exception, causing pods to fail name resolution. Other pitfalls include DNS setups like NodeLocal DNSCache, which may need extra rules for hostNetwork pods or link-local addresses. The author also points to other platform dependencies that often break in the same way when they are not explicitly allowed.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in