Skip to content

Network Policy API Subgroup Blog

ClusterNetworkPolicy or what happened to the AdminNetworkPolicy and BaselineAdminNetworkPolicy?

AdminNetworkPolicy (ANP) and BaselineAdminNetworkPolicy (BANP) were the first APIs created by the Network Policy API working group. They are v1alpha1 resources, which means that they are not stable and are mostly used to get early feedback on the API design from the community.

If you have seen these APIs, you probably have noticed that they are quite similar. If you have written controllers to reconcile these resources, you probably also found some code duplication. The original reason for having two separate resources was just a lack of use cases for multiple instances of BANP, which made it a singleton. However, with more feedback from the community, we have realized that those use cases do exist and that having two separate resources adds more burden than value.

Getting started with the AdminNetworkPolicy API

AdminNetworkPolicy API has been an exciting new addition towards the Kubernetes networking space and is currently on its way towards beta. If you want to learn how to use the API and how it interoperates with the existing NetworkPolicy API, you've landed at the right place :) This blog post will take you through the ins-and-outs of the AdminNetworkPolicy objects, as well as providing some basic sample specs for typical use-cases that the API solves.