Picture a Friday evening: a container in your staging namespace starts querying the prod database, for the plain reason that nothing stops it. In Kubernetes that is the default behaviour. A Kubernetes NetworkPolicy is how you put walls where the cluster has none, and this post follows the routine I would suggest: lock a namespace down, reopen only the doors you need, then prove each wall holds.
Well-placed walls pay off a second time: when a call fails, the responsible rule is in a file you can read instead of a puzzle you have to guess at. To watch flows afterwards, see Cilium and Hubble ; here we stay on the standard API.
Full disclosure: span.observer did not deploy these policies on a cluster. Manifests and commands are those of the Kubernetes documentation, read on 8 November 2026, and the screenshots reproduce those extracts, test output included, which is what the docs announce rather than something we measured.
What « isolated » means for a pod
Everything hinges on one switch.…