Hello everyone,
We're happy to announce the release of Network Policy API v0.2.0, introducing the v1alpha2 API version with a new unified resource:
ClusterNetworkPolicy (CNP).
Release:
https://github.com/kubernetes-sigs/network-policy-api/releases/tag/v0.2.0What's new in v0.2.0
ClusterNetworkPolicy combines the previously separate
AdminNetworkPolicy and
BaselineAdminNetworkPolicy resources into a single CRD with a tier field (Admin or Baseline) to control policy precedence. See
NPEP-285 for more details.
Other notable changes in v1alpha2:
- The Allow action has been renamed to Accept
- NPEP-187: Ports and Protocols -- The ports field has been replaced with a new protocols field that provides explicit per-protocol matching for TCP, UDP, and SCTP with clearer semantics and scope for future expansion and addition of more protocols
- Reduced MaxItems from 100 to 25 for rules and peers
Documentation
Please check out our docs on how to get started with this project OR for more details on how to use the new API
ImplementationsThe following projects have already implemented ClusterNetworkPolicy support:
- Kube-network-policies -- reference implementation
- Calico
- Kube-OVN
Road to Beta
We are now working towards Beta for the ClusterNetworkPolicy API (ETA: Around KubeCon NA 2026). Key areas of focus include:
- Ensuring the conformance test coverage is comprehensive
- Gathering feedback from implementers and users on the v1alpha2 API surface
We want your feedback!
If you're using or planning to use ClusterNetworkPolicy, we'd love to hear from you:
- Are there any gaps in the API for your use cases?
- How has your experience been with the v1alpha2 changes?
- Are there features you'd like to see prioritized for Beta?
Please share feedback on this thread, file issues, or join us at our community meetings (Tuesdays at 9am PT / 16:00 UTC every two weeks):
Slack: #sig-network-policy-api
Thanks to everyone who contributed to this release!
- Surya