By Manjot Pahwa, Networking Product Manager, Google, and Andy Randall, Co-founder and VP of Product, Tigera
We’re pleased to announce the GA of network policies for Kubernetes, which we originally announced into beta last September. Network policies are fully tested and supported for production workloads on Google Kubernetes Engine, and, as a community, we recommend users enable them.
Network policies are sets of constraints that allow Kubernetes admins to designate how groups of Pods can communicate with each other, allowing the creation of a hierarchy of network controls. For example, if you have a multi-tier application, you can create a network policy that ensures a compromised front-end service doesn’t communicate with a back-end service such as billing.
With GA, the community has added the following additional features:
What’s next for Kubernetes network policies?
The pace of Kubernetes development comes fast and furious, particularly in the area of network security. To learn how to get started with and make the most of network policies in Kubernetes, check out this recent blog post by Google developer experience engineer Ahmet Alp Balkan, then try out network policies for yourself.
If you haven’t tried GCP and Kubernetes Engine before, you can quickly get started with our $300 free credits.