Promote endPort field in netpolicies to beta

[rikatz]

Signed-off-by: Ricardo Pchevuzinske Katz ricardo.katz@gmail.com

What type of PR is this?

/kind feature
/kind api-change

What this PR does / why we need it:

Promote the endPort field in Network Policies to Beta

Which issue(s) this PR fixes:

Part of kubernetes/enhancements#2079

Special notes for your reviewer:

As per graduation criteria, we now have 2 CNIs supporting EndPort and one on its way to support:

• Calico, per PR Add support for Kubernetes EndPort field projectcalico/libcalico-go#1357
• Antrea, per PR Add K8sNP endPort support antrea-io/antrea#2190
• Kube-router (ongoing) per PR Add support for kubernetes endport field cloudnativelabs/kube-router#1080

About other CNIs:

• Cilium seems to need some change on its dataplane layer, which was already part of conversation with them and it's on roadmap.
• Openshift-sdn does not gets any new feature
• ovn-kubernetes just implements when a feature is GA

Does this PR introduce a user-facing change?

Network Policy EndPort is graduated to beta and is enabled by default

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/tree/d0b04580b6e3cd9287185cfc379efad151f966b2/keps/sig-network/2079-network-policy-port-range

[k8s-ci-robot]

@rikatz: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rikatz]

/sig network
/assign @thockin @caseydavenport

[fejta-bot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[thockin]

Test fails are saying to re-run generators.

[thockin]

/approve

[rikatz]

Test fails are saying to re-run generators.

Yeap, I'm leaving those as the final step because people used to ask me in other PRs to leave them in a separate commit! Thank you Tim! Will run right now and see if everything passes now! :)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz, thockin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• api/OWNERS [thockin]
• pkg/apis/networking/OWNERS [thockin]
• pkg/features/OWNERS [thockin]
• staging/src/k8s.io/api/OWNERS [thockin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rikatz]

/test pull-kubernetes-verify

This is strange, verify-openapi-spec does not fail here in my machine...

[rikatz]

/test pull-kubernetes-e2e-gci-gce-ingress

[rikatz]

/retest

[abhiraut]

nice lgtm! thanks @rikatz

[abhiraut]

/lgtm

[k8s-ci-robot]

@rikatz: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-gci-gce-ingress	bc86d12	link	/test pull-kubernetes-e2e-gci-gce-ingress

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[rikatz]

/retest