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
1 of 4 tasks
aojea opened this issue Jun 30, 2020 · 59 comments
Open
1 of 4 tasks

Multiple Service CIDRs #1880

aojea opened this issue Jun 30, 2020 · 59 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

Comments

@aojea
Copy link
Member

aojea commented Jun 30, 2020

Enhancement Description

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

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

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

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

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

/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

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

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 Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Jun 1, 2021
@aojea aojea moved this from Pre-Alpha (code not merged) to New, not evaluated in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Jun 1, 2021
@aojea aojea moved this from New, not evaluated to Evaluated, not committed in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Jun 1, 2021
@aojea aojea moved this from Evaluated, not committed to Pre-Alpha (code not merged) in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) 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

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

@aojea
Copy link
Member Author

aojea commented Mar 14, 2023

Please let me know what other PRs in k/k I should be tracking for this KEP.

Only this PR for this KEP will be targeting this release kubernetes/kubernetes#115075

@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 Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Mar 16, 2023
@thockin thockin modified the milestones: v1.27, v1.28 Apr 27, 2023
@thockin
Copy link
Member

thockin commented Apr 27, 2023

Milestoning for 1.28, but @aojea is driving a discussion about overlap with #2593

@Atharva-Shinde Atharva-Shinde removed lead-opted-in Denotes that an issue has been opted in to a release tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 14, 2023
@thockin thockin modified the milestones: v1.28, v1.29 Jun 7, 2023
@thockin
Copy link
Member

thockin commented Jun 7, 2023

Moved to 1.29

@npolshakova
Copy link

Hi @aojea, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancements and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

@thockin thockin added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 27, 2023
@sanchita-07
Copy link
Member

Hello @aojea 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage beta for 1.29 (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.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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

  • KEP readme using the latest template has been merged into the k/enhancements repo
  • The kep.yaml file based on the recent changes
  • Update the issue description.

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

@aojea
Copy link
Member Author

aojea commented Sep 27, 2023

still targeting alpha @sanchita-07 😄

@sanchita-07
Copy link
Member

Okay! Can you update the issue and the milestone in kep.yaml for the same, please?

@Priyankasaggu11929
Copy link
Member

#4175 updates the latest_milestone in kep.yaml and KEP Readme and is merged.

@npolshakova
Copy link

With KEP PR #4175 approved, the enhancement is ready for the enhancements freeze. The status is now marked as tracked for enhancement freeze for 1.29. 🚀 Thank you!

@harshitasao
Copy link

Hi @aojea 👋, v1.29 Docs Shadow here
Does this enhancement work planned for v1.29 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

@harshitasao
Copy link

Hi @aojea! The deadline to open a placeholder PR against k/website for required documentation is Thursday, 19 October. Could you please update me on the status of docs for this enhancement?
Thank you!

@sanchita-07
Copy link
Member

Hey again @aojea 👋, 1.29 Enhancements team here.

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 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 ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PR was merged before code freeze:

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

With the merged and linked in the issue description, this KEP is tracked for code freeze for v1.29. 🚀
As always, we are here to help if any questions come up ✌. Thanks :)

@aojea
Copy link
Member Author

aojea commented Oct 24, 2023

@sanchita-07 update the description, this one is missing for this release kubernetes/kubernetes#116516

@kcmartin
Copy link

Hi @aojea ! 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here's the 1.29 Calendar

@salehsedghpour
Copy link
Contributor

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Jan 6, 2024
@salehsedghpour
Copy link
Contributor

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now,
If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

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
Projects
Status: Net New
Status: Tracked
Status: Tracked for Code Freeze
Obsolete: SIG-Network KEPs (see https...
Alpha gated (code is merged)
Development

No branches or pull requests