Skip to content

Graduating networks peer to standard channel from experimentalΒ #259

@tssurya

Description

@tssurya

Describe the issue:

We added support for networks peer which is a list of inline CIDRs #185

There are currently two implementations definitely who have implemented this:

  1. OVN-Kubernetes
  2. Calico
  3. Kube-network-policies

Other CNI implementations like Kube-OVN are waiting for this API to be in standard channel rather than experimental: kubeovn/kube-ovn#3247 (comment)

are there any concerns from the maintainers of the repo if I move this peer to standard channel?

@danwinship / @Dyanngg / @aojea / @astoycos ?

As per our docs: https://network-policy-api.sigs.k8s.io/versioning/?h=beta#experimental-standard (I can open another issue to track what we spoke about whether we want standard/experimental to mean stability OR optional but for all intents and purposes of this field there was no controversies on the optional/mandatory bits so we should try to focus on stability aspects here); it seems I need to fullfill alpha->beta chain of events: https://network-policy-api.sigs.k8s.io/versioning/?h=beta#alpha-beta

so we seems to satisfy most of the requirements here. Only missing bit is validation which I was waiting for 1.31 kube to have isCIDR validation: https://github.com/kubernetes-sigs/network-policy-api/pull/256/files#diff-e14a317f3c12a983e1037dec16d99833bd1398ab66a65a8b6476adad81d05b1cR150 so once we fix the bump to 1.31 we should be able to move networks peer.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions