Reserve nodeport ranges for dynamic and static allocation

[xuzhenglun]

Enhancement Description

• One-line enhancement description (can be used as a release note): reserve nodeport ranges for dynamic and static allocation
• Kubernetes Enhancement Proposal: Reserve Nodeport Ranges For Dynamic And Static Port Allocation #3682
• Discussion Link: Reserved an statically port range for nodeport  kubernetes#114129
• Primary contact (assignee): @xuzhenglun
• Responsible SIGs: network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.27
  • Beta release target (x.y): 1.28
  • Stable release target (x.y): 1.30
• Alpha
  • KEP (k/enhancements) update PR(s):
    • Reserve Nodeport Ranges For Dynamic And Static Port Allocation #3682
  • Code (k/k) update PR(s):
    • Reserve Nodeport Ranges For Dynamic And Static Port Allocation kubernetes#114418
  • Docs (k/website) update PR(s):
    • add doc for ServiceNodePortStaticSubrange website#39850
    • add blog for feature ServiceNodePortStaticSubrange website#40204

[aojea]

/sig network

[wojtek-t]

@thockin @aojea - I think we want to opt-in this for 1.27, right?

[aojea]

yes, @xuzhenglun that is the plan , right?

[xuzhenglun]

yes, @xuzhenglun that is the plan , right?

yes, it is. now PR is ready and waiting for next step review kubernetes/kubernetes#114418

[wojtek-t]

/label lead-opted-in

[Atharva-Shinde]

Hello @xuzhenglun 👋, Enhancements team here.

Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

For this KEP, we would just need to update the following:

• Add response for this question in the Scalability questionnaire of the KEP readme
• Change the status of the KEP from provisional to implementable
• Update this enhancement's test plan section to be in compliance with the current detailed test plan of the KEP readme template
• Change the kep-number from 3070 to the actual number of the KEP i.e 3668

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!

[xuzhenglun]

Hello @xuzhenglun 👋, Enhancements team here.

Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

For this KEP, we would just need to update the following:

• Add response for this question in the Scalability questionnaire of the KEP readme
• Change the status of the KEP from provisional to implementable
• Update this enhancement's test plan section to be in compliance with the current detailed test plan of the KEP readme template
• Change the kep-number from 3070 to the actual number of the KEP i.e 3668

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!

@Atharva-Shinde KEP has fixed in #3809, should I do anything else to remove at risk label?

[Atharva-Shinde]

@xuzhenglun
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[mickeyboxell]

Hi @xuzhenglun 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

[xuzhenglun]

I think a blog is enough for this KEP, WDYT? @aojea

Placeholder doc PR link: kubernetes/website#39850 @mickeyboxell

[Atharva-Shinde]

Hey again @xuzhenglun 👋 Enhancements team here,
Just checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are fully merged by the code freeze deadline.
  • Reserve Nodeport Ranges For Dynamic And Static Port Allocation kubernetes#114418

Also please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!