Originally published on kuryzhev.cloud
A team applies a default-deny policy to a staging namespace on Friday afternoon, and within seconds every pod starts logging "temporary failure in name resolution". Or the opposite happens: the policy applies cleanly, nothing breaks, and nothing is actually blocked either. A NetworkPolicy baseline sounds like a simple YAML exercise, but the documented behavior has enough sharp edges that the same few mistakes keep appearing. This retrospective walks through those mistakes as patterns, not as a report of any specific outage.
Context: what a NetworkPolicy baseline is supposed to do
By default, Kubernetes pods accept traffic from any other pod in the cluster and can reach any destination. Namespaces are an organizational boundary, not a network one.…