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

Multiple Service CIDRs #1880

Open
aojea opened this issue Jun 30, 2020 · 30 comments
Open

Multiple Service CIDRs #1880

aojea opened this issue Jun 30, 2020 · 30 comments
Assignees
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. 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

Comments

@aojea
Copy link
Member

aojea commented Jun 30, 2020

Enhancement Description

  • One-line enhancement description (can be used as a release note): Implement an API to manage Kubernetes Services IP Ranges
  • Kubernetes Enhancement Proposal: KEP-1880 Multiple Service CIDRs #3365
  • Primary contact (assignee): @aojea
  • Responsible SIGs: sig-network
  • Enhancement target (which target equals to which milestone):
    • Alpha release target 1.25
    • Beta release target (x.y)
    • Stable release target (x.y)

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 30, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 13, 2020

Hi @aojea

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

@aojea
Copy link
Member Author

aojea commented Sep 14, 2020

seems this change requires more discussion, no plans yet

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 14, 2020

Thanks! Please let us know if anything changes 😺

@kikisdeliveryservice kikisdeliveryservice added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Sep 14, 2020
@fejta-bot
Copy link

fejta-bot commented Dec 13, 2020

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 Dec 13, 2020
@fejta-bot
Copy link

fejta-bot commented Jan 12, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 12, 2021
@ehashman
Copy link
Member

ehashman commented Jan 13, 2021

/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 13, 2021
@aojea
Copy link
Member Author

aojea commented Jan 14, 2021

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 14, 2021
@aojea aojea changed the title Supported Service Subnet Sizes Services API for ClusterIP and NodePort Allocations Jan 24, 2021
@aojea aojea changed the title Services API for ClusterIP and NodePort Allocations Services ClusterIP and NodePort Allocations API Jan 24, 2021
@fejta-bot
Copy link

fejta-bot commented Apr 24, 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-contributor-experience at kubernetes/community.
/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 Apr 24, 2021
@thockin thockin added this to New (not evaluated) in SIG-Network KEPs via automation May 22, 2021
@fejta-bot
Copy link

fejta-bot commented May 24, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 24, 2021
@thockin thockin removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 1, 2021
@thockin thockin moved this from New (not evaluated) to Pre-Alpha (code not merged) in SIG-Network KEPs Jun 1, 2021
@aojea aojea moved this from Pre-Alpha (code not merged) to New, not evaluated in SIG-Network KEPs Jun 1, 2021
@aojea aojea moved this from New, not evaluated to Evaluated, not committed in SIG-Network KEPs Jun 1, 2021
@aojea aojea moved this from Evaluated, not committed to Pre-Alpha (code not merged) in SIG-Network KEPs Jun 1, 2021
@dcbw
Copy link
Member

dcbw commented Jun 10, 2021

[sig-network 2021-06-10] Waiting on Tim/others to review Antonio's PoC repo...

@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 8, 2021

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

@jasonbraganza
Copy link
Member

jasonbraganza commented Jun 13, 2022

Hello @aojea 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

For note, This enhancement is targeting for stage alpha 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.

Looks like for this one, we would need to update the open PR #3365 with the following and get it merged by the enhancement freeze:

  • Update the kep.yaml file to change status from provisional to implementable

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!

@jasonbraganza
Copy link
Member

jasonbraganza commented Jun 20, 2022

Hello @aojea . Just checking in, as we are four days away from the enhancements freeze.

Please plan to get the PR #3365 merged with the suggestions mentioned above, by the new enhancements freeze date: Thursday, June 23, 2022 at 18:00 PM PT.

Please note: the current status of the enhancement is at-risk.
Thank you.

@aojea aojea changed the title Services IP Ranges Multiple Service CIDRs Jun 20, 2022
@thockin thockin moved this from Evaluated, not committed (undecided whether we want to do this or not) to Pre-Alpha (we want to do this but the KEP or code is not merged yet) in SIG-Network KEPs Jun 20, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 23, 2022

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

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

@kcmartin
Copy link

kcmartin commented Jul 12, 2022

Hello @aojea 👋, 1.25 Release Docs Lead here.
This enhancement is marked as ‘Needs Docs’ for 1.25 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by August 4.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

@rhockenbury
Copy link

rhockenbury commented Jul 21, 2022

👋 Hey @aojea,

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!!

@kcmartin
Copy link

kcmartin commented Jul 27, 2022

Hi @aojea !

Here is your reminder that are approaching the August 4 deadline for opening a docs PR placeholder for your enhancement.

Please reach out here if you have any questions. Thanks!

@aojea
Copy link
Member Author

aojea commented Jul 29, 2022

@kcmartin @rhockenbury sorry for the silence, been busy, I'm going to postpone this for 1.26

@rhockenbury
Copy link

rhockenbury commented Jul 29, 2022

Thanks for the update. I have this marked in the tracking sheet as Removed from Milestone

@rhockenbury rhockenbury removed this from the v1.25 milestone Jul 29, 2022
@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 Jul 29, 2022
@thockin thockin added this to the v1.26 milestone Sep 29, 2022
@thockin
Copy link
Member

thockin commented Sep 29, 2022

Candidate for Alpha in 1.26

@thockin thockin added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 29, 2022
@rhockenbury
Copy link

rhockenbury commented Sep 30, 2022

/label tracked/yes
/remove-label tracked/no
/stage alpha

@k8s-ci-robot k8s-ci-robot added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha 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
@rhockenbury
Copy link

rhockenbury commented Oct 1, 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 for stage alpha 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, please plan to open a PR to update the KEP yaml, KEP README and PRR file.

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!

@rhockenbury
Copy link

rhockenbury commented Oct 7, 2022

Hello 👋, 1.26 Enhancements Lead here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot 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 Oct 7, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Oct 7, 2022
@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Oct 7, 2022
@aojea
Copy link
Member Author

aojea commented Nov 7, 2022

@rhockenbury can you please drop this from 1.26, I'm not going to make it for sure, I will target 1.27

Thanks

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/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
Projects
Status: Net New
SIG-Network KEPs
Pre-Alpha (we want to do this but the...
Development

No branches or pull requests