Repository navigation
Multiple Service CIDRs #1880
Description
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: https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/1880-multiple-service-cidrs/README.md
- Primary contact (assignee): @aojea
- Responsible SIGs: sig-network
- Enhancement target (which target equals to which milestone):
- Alpha release target 1.29
- Beta release target 1.31
- Stable release target 1.33
- Alpha
- KEP (
k/enhancements) update PR(s): - Code (
k/k) update PR(s): - Docs (
k/website) update PR(s):
- KEP (
- Beta
- KEP (
k/enhancements) update PR(s): - Code (
k/k) update PR(s): - Docs (
k/website) update(s):
- KEP (
- Stable
- KEP (
k/enhancements) update PR(s): KEP 1880: graduation to GA #4983 - Code (
k/k) update PR(s): KEP-1880 Multiple Service CIDRs: Graduate to GA kubernetes#128971 - Docs (
k/website) update(s): Multiple Service CIDRs - KEP 1880 website#49746
- KEP (
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
kikisdeliveryservice commentedon Sep 13, 2020
Hi @aojea
Enhancements Lead here. Any plans for this in 1.20?
Thanks!
Kirsten
aojea commentedon Sep 14, 2020
seems this change requires more discussion, no plans yet
kikisdeliveryservice commentedon Sep 14, 2020
Thanks! Please let us know if anything changes 😺
fejta-bot commentedon 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
fejta-bot commentedon 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
ehashman commentedon Jan 13, 2021
/sig network
aojea commentedon Jan 14, 2021
/remove-lifecycle rotten
176 remaining items
rayandas commentedon Feb 12, 2025
Hello @aojea 👋, v1.33 Docs Lead here.
Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?
If so, please follow the steps here to open a PR against
dev-1.33branch in thek/websiterepo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT.Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
fykaa commentedon Feb 28, 2025
Hello @aojea 👋, v1.33 Enhancements team here.
With all the implementation (code-related) PRs merged per the issue description:
This enhancement is now marked as
Tracked for code freezefor the v1.33 Code Freeze!Additionally, please let me know if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.
Please note that KEPs targeting
stableneed to have thestatusfield marked asimplementedin the kep.yaml file after code PRs are merged and the feature gates are removed.aojea commentedon Feb 28, 2025
despite is GA, we are still leaving the feature not locked by default, so I think is better to wait for GA and locked by default,
rytswd commentedon Mar 1, 2025
Hi @aojea 👋 -- this is Ryota (@rytswd) from the 1.33 Communications Team!
For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!
As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:
To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚
Tip
Some timeline to keep in mind:
Note
In your placeholder PR, use
XXcharacters for the blogdatein the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.sn3hay commentedon Mar 3, 2025
Hi @aojea 👋, 1.33 Communications Team here again!
This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 5th March, 2025. To opt in, please let us know and open a Feature Blog placeholder PR against
[k/website](https://github.com/kubernetes/website)by the deadline. If you have any questions, please feel free to reach out to us!Tip
Some timeline to keep in mind:
Note
In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.
jenshu commentedon May 16, 2025
Hi @aojea 👋, 1.34 Enhancements Lead here,
Given that this KEP has graduated to
stable, once all the work is completed (including removing feature gates), could you please update the KEP status inkep.yamltoimplemented, and then close this issue?Thanks!
/remove-label lead-opted-in
/remove-label tracked/yes