The firewall was down, the pods were exposed, and one wrong packet could take the cluster offline. Kubernetes Network Policies are the last line of defense. Pair them with Zscaler, and you get a hardened perimeter for workloads that move fast and scale without warning.
Network Policies in Kubernetes define how pods talk to each other and to the outside world. They use labels to match pods and namespaces, then apply rules for ingress and egress traffic. By default, if no NetworkPolicy applies to a pod, all traffic is allowed. That default should change the moment you deploy Zscaler for security at the network edge.
Zscaler acts as a cloud-native secure gateway. It inspects traffic, enforces zero trust, and blocks threats before they reach your cluster. But if traffic inside Kubernetes is unrestricted, a breach can spread laterally. Combining Zscaler with locked-down Network Policies stops this. Create rules that permit ingress only from trusted services. Restrict egress to known domains and IP ranges allowed in Zscaler.