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

Reserve Service IP Ranges For Dynamic and Static IP Allocation #3070

Open
aojea opened this issue Dec 2, 2021 · 33 comments
Open

Reserve Service IP Ranges For Dynamic and Static IP Allocation #3070

aojea opened this issue Dec 2, 2021 · 33 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@aojea
Copy link
Member

aojea commented Dec 2, 2021

Enhancement Description

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

xref: kubernetes/kubernetes#106792

@pacoxu
Copy link
Member

pacoxu commented Jan 6, 2022

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 6, 2022
@thockin thockin added this to the v1.24 milestone Jan 6, 2022
@thockin thockin added this to New, not evaluated in SIG-Network KEPs via automation Jan 6, 2022
@thockin thockin moved this from New, not evaluated to Pre-Alpha (we want to do this but the KEP or code is not merged yet) in SIG-Network KEPs Jan 6, 2022
@aojea aojea changed the title Reserved range within service CIDR wherein automatically assigned IPs will not be chosen Reserve Service IP Range For Dynamic and Static IP Allocation Jan 7, 2022
@aojea aojea changed the title Reserve Service IP Range For Dynamic and Static IP Allocation Reserve Service IP Ranges For Dynamic and Static IP Allocation Jan 7, 2022
@hosseinsalahi
Copy link

hosseinsalahi commented Jan 28, 2022

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

nate-double-u commented Feb 14, 2022

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!

@gracenng gracenng added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Mar 6, 2022
@valaparthvi
Copy link

valaparthvi commented Mar 21, 2022

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

hosseinsalahi commented Mar 21, 2022

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:

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?

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

@aojea
Copy link
Member Author

aojea commented Mar 21, 2022

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

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

valaparthvi commented Mar 29, 2022

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

aojea commented Mar 29, 2022

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

@thockin thockin moved this from Pre-Alpha (we want to do this but the KEP or code is not merged yet) to Alpha gated (code is merged) in SIG-Network KEPs Mar 29, 2022
@Priyankasaggu11929 Priyankasaggu11929 removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 10, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented May 10, 2022

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.24 milestone May 10, 2022
@Priyankasaggu11929 Priyankasaggu11929 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 9, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 9, 2022

/milestone v1.25

@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Jun 9, 2022
@jasonbraganza
Copy link
Member

jasonbraganza commented Jun 20, 2022

Thank you @aojea 🙂
Will be able to mark this as tracked as soon as PR #3413 gets merged

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 23, 2022

With KEP PR #3413 merged, the enhancement is ready for the 1.25 Enhancements Freeze.

For note, the status is now marked as tracked. Thank you so much! 🙂

@thockin thockin moved this from Alpha gated (code is merged) to Beta gated (merged) in SIG-Network KEPs Jul 6, 2022
@parul5sahoo
Copy link
Member

parul5sahoo commented Jul 22, 2022

Hi @aojea 👋

Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed:

Please verify, if there are any additional k/k PRs besides the ones listed above.

Since, all listed above k/k PRs are merged, the status of the enhancement is currently marked as tracked.

Please also update the issue description with the relevant links for tracking purpose. Thank you so much!

@aojea
Copy link
Member Author

aojea commented Jul 29, 2022

we are good here @parul5sahoo , nothing else is required

@reylejano
Copy link
Member

reylejano commented Aug 8, 2022

For 1.25, with this enhancement's graduation to beta, the service-ip-static-sub-range section on the services page on kubernetes.io needs to be updated. @aojea , can you open a PR to the dev-1.25 branch in k/website to update the page accordingly (at least update the feature state if there are no other changes required)
Thank you

@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 added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 29, 2022
@thockin
Copy link
Member

thockin commented Sep 29, 2022

Candidate for GA in 1.26 ? @aojea

@aojea
Copy link
Member Author

aojea commented Sep 29, 2022

Yes

@rhockenbury
Copy link

rhockenbury commented Sep 30, 2022

/milestone v1.26
/label tracked/yes
/remove-label tracked/no
/stage stable

@k8s-ci-robot k8s-ci-robot added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status 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 Sep 30, 2022
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.25, v1.26 Sep 30, 2022
@ruheenaansari34
Copy link

ruheenaansari34 commented Oct 4, 2022

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

aojea commented Oct 4, 2022

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

@rhockenbury
Copy link

rhockenbury commented Oct 6, 2022

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

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

mickeyboxell commented Oct 20, 2022

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

@aojea
Copy link
Member Author

aojea commented Oct 21, 2022

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

Atharva-Shinde commented Oct 31, 2022

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

Atharva-Shinde commented Nov 7, 2022

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

aojea commented Nov 7, 2022

Done, thanks for the heads up

@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

We have this marked as tracked for code freeze.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Graduating
SIG-Network KEPs
GA (merged, gate not removed)
Development

No branches or pull requests