From a security perspective, network policies are important because, by default, Kubernetes allows all-to-all communication in the cluster. Namespaces only provide a simple isolation that still allows pods to communicate with each other by IP address. In larger clusters or in multitenant scenarios, you have to provide better network isolation. Even though Windows nodes do not yet support network policies (but eventually they will be supported), we feel that it is important to make you aware of how you can approach network segmentation using native Kubernetes constructs.
If you have an AKS Engine Linux cluster with a Calico network on an Azure CNI plugin, you can follow along and configure the network policies for ...
