So, you’ve deployed a bright shinny new k8s cluster, pushed your code and services, have the replication controllers auto-scaling and recovering like mad — life is good. Unfortunately, maybe a bit too good. You’ve got attention, and now the security folks are knocking at the door, asking how you intend to run this bright new shinny cluster through the firewalls to instill corporate policy. Let’s see, seconds to spin up a pod, days to get a firewall change ticket through — this isn’t going to work. What you need is some Kubernetes network policy. We’ll discuss this capability and show you how you can use it to meet (and exceed) organizational security requirements within the cluster, and even between the cluster and the rest of the organization.