NetworkPolicy port range

[rikatz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow a Network Policy to contemplate a set of ports in a single rule.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2079-network-policy-port-range
• Discussion Link: https://www.youtube.com/watch?v=yX1nFb3DS3A&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb Minute 29:00
• Primary contact (assignee): @rikatz
• Responsible SIGs: Network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y) - v1.21
  • Beta release target (x.y) - v1.22
  • Stable release target (x.y) - v1,25

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/sig network

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[rikatz]

/remove-lifecycle stale

[rikatz]

/lifecycle active

[annajung]

This enhancement has met all the requirements for the enhancement freeze 👍

[JamesLaverack]

Hi @rikatz,

Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

• Tuesday, March 9th: Week 9 — Code Freeze
• Tuesday, March 16th: Week 10 — Docs Placeholder PR deadline
  • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!

[JamesLaverack]

Hi @rikatz

Enhancements team is currently tracking the following PRs

• Add EndPort to Network Policy - Alpha kubernetes#97058

As this PR is merged, can we mark this enhancement complete for code freeze or do you have other PR(s) that are being worked on as part of the release?

[rikatz]

@JamesLaverack 👋

Yes,this can be marked as done. I'm just working on the docs here: kubernetes/website#26714

[JamesLaverack]

/milestone v1.22
/stage beta

[Priyankasaggu11929]

/reopen

[k8s-ci-robot]

@Priyankasaggu11929: Reopened this issue.

In response to this:

/reopen

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.

[rhockenbury]

👋 Hey @rikatz,

Enhancements team checking in as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed by code freeze:
[ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
[x] All PRs are fully merged by the code freeze deadline.

Looks like there is one merged PR in k/k. Let me know if I missed any other PRs that need to be tracked.

As always, we are here to help should questions come up. Thanks!!

[rikatz]

hey @rhockenbury

yeah, there's no new PR. We just need to make sure this is also announced in the blog with the features of v1.25, letting users know this feature depends on which CNI/NPP they use :)

Thanks for the heads up

[reylejano]

HI @rikatz , since this enhancement will graduate to stable, the Targeting a Range of Ports section on the Network Policies page on kubernetes.io should be updated accordingly
Please make a PR to the dev-1.25 branch on k/website to update that section -- at least the feature state if the rest of the documentation requires no changes

[thockin]

Remove gate in 1.27

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale