Answers are grounded in this paper and cite their sources.
Kubernetes NetworkPolicy resources are the native mechanism for restricting traffic to and from pods, but a NetworkPolicy is a declaration of intent, not a guarantee of enforcement. Enforcement depends on the CNI plugin, and in a GitOps pipeline, where policies are stored in Git and reconciled automatically, a manifest that passes review can still produce no isolation at runtime. This literature-based study reviews what is known about two validation families (static, which inspects manifests before they reach the cluster, and dynamic, which tests connectivity inside a running cluster) and identifies four gaps: the divide between static and dynamic validation, the handoff gap between pre-apply and post-sync phases, the missing link between known misconfiguration patterns and the gates that might catch them, and the absence of a reproducible test oracle for dynamic testing. From this review we derive a four-layer conceptual framework (manifest-level static validation, offline semantic validation, runtime dynamic validation, and continuous verification inside the reconciliation loop) as an organising model for practitioners and an agenda for empirical work. The framework synthesises existing approaches and has not been implemented or tested.
No takes yet. Share an insight, caveat, or question.
Aayan et al. (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: