Reserve Service IP Ranges For Dynamic and Static IP Allocation

[aojea]

Enhancement Description

• One-line enhancement description (can be used as a release note): Subdivide the ClusterIP range for dynamic and static IP allocation.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3070-reserved-service-ip-range
• Discussion Link: Reserved range within service CIDR wherein automatically assigned IPs will not be chosen kubernetes#95570
• Primary contact (assignee): @aojea
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.24
  • Beta release target (x.y): 1.25
  • Stable release target (x.y): 1.26

This feature went to GA in 1.26 kubernetes/kubernetes#112163 🥳

xref: kubernetes/kubernetes#106792

[pacoxu]

/sig network

[hosseinsalahi]

Hello @aojea

v1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. This enhancement is targeting alpha for v1.24,

Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release
• KEP has a 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 status of this enhancement is marked as tracked. Please keep the issue description up-to-date.
Thanks!

[nate-double-u]

Hi @aojea 👋 1.24 Docs lead here.

This enhancement is marked as Needs Docs for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, March 31st, 2022 @ 18:00 PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!

[valaparthvi]

Hi @aojea 👋 1.24 Release Comms team here.

We have an opt-in process for the feature blog delivery. If you would like to publish a feature blog for this issue in this cycle, then please opt in on this tracking sheet.

The deadline for submissions and the feature blog freeze is scheduled for 01:00 UTC Wednesday 23rd March 2022 / 18:00 PDT Tuesday 22nd March 2022. Other important dates for delivery and review are listed here: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.24#timeline.

For reference, here is the blog for 1.23.

Please feel free to reach out any time to me or on the #release-comms channel with questions or comments.

Thanks!

[hosseinsalahi]

Hello @aojea

I'm just checking in once more as we approach the 1.24 Code Freeze on 18:00 PDT, Tuesday, March 29th 2022

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are merged by the code freeze deadline.
• Have a documentation placeholder PR open by 18:00 PDT, Thursday, March 31, 2022.
  • Add documentation for (alpha) feature ServiceIPStaticSubrange website#32345

For note, the status of this enhancement is currently marked as tracked.

Could you please confirm if following PR is part of the implementation for this enhancement?

• KEP-3070: Reserve Service IP Ranges For Dynamic and Static IP Allocation kubernetes#106792

Kindly please let me know if I'm missing any related PRs other than the ones I linked above.
Thank you so much!

[aojea]

Could you please confirm if following PR is part of the implementation for this enhancement?

• KEP-3070: Reserve Service IP Ranges For Dynamic and Static IP Allocation kubernetes#106792
• ServiceIPStaticSubrange alpha feature in 1.24 website#32345

Kindly please let me know if I'm missing any related PRs other than the ones I linked above. Thank you so much

@encodeflush those 2 PRs are the implementation and the docs,

[valaparthvi]

Hi @aojea wave 1.24 Release Comms team here.

We have an opt-in process for the feature blog delivery. If you would like to publish a feature blog for this issue in this cycle, then please opt in on this tracking sheet.

The deadline for submissions and the feature blog freeze is scheduled for 01:00 UTC Wednesday 23rd March 2022 / 18:00 PDT Tuesday 22nd March 2022. Other important dates for delivery and review are listed here: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.24#timeline.

For reference, here is the blog for 1.23.

Please feel free to reach out any time to me or on the #release-comms channel with questions or comments.

Thanks!

Hi @aojea, can you please add a placeholder PR for this feature in https://github.com/kubernetes/website by March 30, that is our extended deadline for feature blog freeze?

Example of a feature blog PR: kubernetes/website#30538
Example of a feature blog: https://github.com/kubernetes/website/blob/main/content/en/blog/_posts/2021-12-08-dual-stack-networking-ga.md

[aojea]

@valaparthvi https://github.com/kubernetes/website/pull/32606/files

[Priyankasaggu11929]

/milestone clear

[Priyankasaggu11929]

/milestone v1.25

[ruheenaansari34]

Hello @aojea 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting stage stable for 1.26 (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.26
• 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:

• update the merged kep.yaml to reflect latest stage & milestone information.
• add a PRR approval for stage stable that has been completed and have it merged into k/enhancements.

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!

[aojea]

Thanks @ruheenaansari34 for the heads up, sent PR to fix it
#3578

[rhockenbury]

With #3583 merged, we have this marked as tracked for v1.26. Thanks.

[mickeyboxell]

@aojea Are docs required for this KEP? If so, who will be opening the docs PR for k/website?

[aojea]

@aojea Are docs required for this KEP? If so, who will be opening the docs PR for k/website?

Thanks for the remindes, submitted
kubernetes/website#37432 @mickeyboxell

[Atharva-Shinde]

Hey @aojea 👋,

Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to this enhancement are linked in the issue description above(for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

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

[Atharva-Shinde]

Hey @aojea 👋, just a quick check-in again before 1.26 code freeze at 17:00 PDT Tuesday 8th November 2022 i.e tomorrow.
Looks like we would at least need to get the code PRs merged before the code-freeze. Could you also please update the Issue Description with related code PRs :)

[aojea]

Done, thanks for the heads up

[rhockenbury]

We have this marked as tracked for code freeze.

[marosset]

Hi @aojea - since this enhancement has graduated to stable can you please update https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/3070-reserved-service-ip-range/kep.yaml setting the status to implemented and then close this issue.
Thanks!

[aojea]

sent #3707 for setting status to implemented

[thockin]

NEXT: Remove gate in 1.28

[thockin]

DONE