Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NetworkPolicy port range #2079

Open
rikatz opened this issue Oct 6, 2020 · 39 comments · Fixed by kubernetes/kubernetes#110868
Open

NetworkPolicy port range #2079

rikatz opened this issue Oct 6, 2020 · 39 comments · Fixed by kubernetes/kubernetes#110868
Assignees
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Milestone

Comments

@rikatz
Copy link
Contributor

rikatz commented Oct 6, 2020

Enhancement Description

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

/sig network

@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Oct 6, 2020
@kikisdeliveryservice kikisdeliveryservice added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Oct 6, 2020
@fejta-bot
Copy link

fejta-bot commented Jan 4, 2021

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2021
@rikatz
Copy link
Contributor Author

rikatz commented Jan 4, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2021
@rikatz
Copy link
Contributor Author

rikatz commented Jan 26, 2021

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Jan 26, 2021
@annajung annajung added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jan 27, 2021
@annajung annajung added this to the v1.21 milestone Jan 27, 2021
@annajung
Copy link
Member

annajung commented Feb 9, 2021

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

@JamesLaverack
Copy link
Member

JamesLaverack commented Feb 19, 2021

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
Copy link
Member

JamesLaverack commented Mar 2, 2021

Hi @rikatz

Enhancements team is currently tracking the following PRs

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
Copy link
Contributor Author

rikatz commented Mar 2, 2021

@JamesLaverack 👋

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

@JamesLaverack JamesLaverack added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Apr 25, 2021
@thockin thockin changed the title Allow a Network Policy to contemplate a set of ports in a single rule. NetworkPolicy port range Apr 30, 2021
@JamesLaverack JamesLaverack added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 1, 2021
@JamesLaverack
Copy link
Member

JamesLaverack commented May 1, 2021

/milestone v1.22
/stage beta

@k8s-ci-robot k8s-ci-robot added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels May 1, 2021
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.21, v1.22 May 1, 2021
@thockin thockin modified the milestones: v1.23, v1.25 Feb 2, 2022
@gracenng gracenng removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Mar 6, 2022
@thockin
Copy link
Member

thockin commented Jun 20, 2022

Added to spreadsheet for 1.25

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 21, 2022

Hello @rikatz 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PT on Thursday June 23, 2022, which is just over 3 days from now.

For note, This enhancement is targeting for stage stable for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has a updated detailed test plan section filled out
  • KEP has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

The open PR #2883 is addressing all the unchecked items above. Please plan to get it merged by the Enhancements Freeze.

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@Priyankasaggu11929 Priyankasaggu11929 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 21, 2022
@rikatz
Copy link
Contributor Author

rikatz commented Jun 21, 2022

@Priyankasaggu11929 thanks!

KEP has been merged with all the checkbox filled. I will start implementing in k/k :)

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 22, 2022

Thanks so much @rikatz. The KEP is now marked as tracked in the 1.25 enhancements tracking sheet. 🚀

@thockin thockin moved this from Beta gated (merged) to GA (merged, gate not removed) in SIG-Network KEPs Jul 5, 2022
@thockin
Copy link
Member

thockin commented Jul 5, 2022

TODO: Remove gate in v1.27

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jul 13, 2022

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Jul 13, 2022
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 13, 2022

@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.

SIG-Network KEPs automation moved this from GA (merged, gate not removed) to New, not evaluated Jul 13, 2022
@rhockenbury
Copy link

rhockenbury commented Jul 21, 2022

👋 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
Copy link
Contributor Author

rikatz commented Jul 21, 2022

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

@thockin thockin moved this from New, not evaluated to Alpha gated (code is merged) in SIG-Network KEPs Aug 4, 2022
@reylejano
Copy link
Member

reylejano commented Aug 8, 2022

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

@rhockenbury rhockenbury added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 11, 2022
@thockin thockin moved this from Alpha gated (code is merged) to GA (merged, gate not removed) in SIG-Network KEPs Sep 29, 2022
@thockin thockin modified the milestones: v1.25, v1.27 Sep 29, 2022
@thockin
Copy link
Member

thockin commented Sep 29, 2022

Remove gate in 1.27

@thockin thockin removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
SIG-Network KEPs
GA (merged, gate not removed)
Development

Successfully merging a pull request may close this issue.