Multiple Service CIDRs

[aojea]

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 (x.y)
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-1880 Multiple Service CIDRs #3365
    • KEP-1880: updating KEP #3844
  • Code (k/k) update PR(s):
    • IPAddress allocator kubernetes#115075
    • KEP-1880 Multiple ServiceCIDR ( and IPAddress allocation) kubernetes#116516
  • Docs (k/website) update PR(s):
    • KEP-1880 alpha: IPAddresses website#37620
    • KEP-1880 Multiple ServiceCIDR  website#43469
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-1880: graduating to beta #4645
  • Code (k/k) update PR(s):
    • KEP-1880 Multiple Service CIDRs: Graduate to Beta (1/2) kubernetes#122047
    • KEP-1880 Multiple Service CIDRs: Graduate to Beta (2/2) kubernetes#125021
  • Docs (k/website) update(s):
    • KEP-1880 website#46947

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

[kikisdeliveryservice]

Hi @aojea

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[aojea]

seems this change requires more discussion, no plans yet

[kikisdeliveryservice]

Thanks! Please let us know if anything changes 😺

[fejta-bot]

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]

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]

/sig network

[aojea]

/remove-lifecycle rotten

[fejta-bot]

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

[fejta-bot]

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

[dcbw]

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

[k8s-triage-robot]

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]

@tjons can you please check the PR #4645 is ok? I can't find the missing sections of the template you are referring to

[sreeram-venkitesh]

/stage beta

[tjons]

@aojea this question, under scalability, is now required: https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template#can-enabling--using-this-feature-result-in-resource-exhaustion-of-some-node-resources-pids-sockets-inodes-etc: Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)? Otherwise, your KEP looks good, just needs to be merged and marked as implementable

[aojea]

@aojea this question, under scalability, is now required: https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template#can-enabling--using-this-feature-result-in-resource-exhaustion-of-some-node-resources-pids-sockets-inodes-etc: Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)

fixed, thanks for the quick response

[Princesso]

Hello @aojea 👋, 1.31 Docs Lead here.
Does this enhancement work planned for 1.31 require any new docs or modification to existing docs?
If so, please follow the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.
Thank you!

[dipesh-rawat]

Hi @aojea 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach the enhancements freeze in few hours, at 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment #1880 (comment) that are addressed as part of PR #4645 which still needs to be merged.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

Hi @aojea 👋, 1.31 Enhancements team here.

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

If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

[sreeram-venkitesh]

/milestone clear

[thockin]

I will file an exception on behalf of @aojea who is unavailable right now (Friday night local time). I think the only thing blocking is one corner-case that we want to address, but it is a small race and we don't want to go out with it.

[mbianchidev]

Hey @sreeram-venkitesh can you let me know if this enhancement makes it in this release?
Chaning the status on the board also works. Thanks a ton :)

[thockin]

The exception was approved. We are working on the revised kept language today and yesterday.

[sreeram-venkitesh]

@mbianchidev: +1 to what Tim said, exception was approved.

[thockin]

The revised KEP has been merged

[sreeram-venkitesh]

@thockin Is there anything else that needs to be merged? If no I can mark this KEP as tracked.

[thockin]

We haggled over some future milestones, but I think the language for this KEP for this release is done. Thanks for the extra few days!

[sreeram-venkitesh]

@aojea @thockin The KEP is marked as tracked for enhancements freeze! Thanks!

[Princesso]

Hello @aojea 👋, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you!

Hi @thockin @aojea, gentle reminder to raise a draft Doc PR before Thursday, June 27, 2024, 18:00 PDT, if this enhancement requires documentation for v1.31.

[mbianchidev]

Hello @aojea and @thockin

It's Matteo from the v1.31 Communications Team 😄

We'd love for you to opt in to write a feature blog about this enhancement on dynamic IPs availability for Services!
A reason why you might want to write a blog for this feature is that it is graduating to beta and it is interesting for our users.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

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.

Let me know if you need any support for the blog, thanks!

[tjons]

Hi @aojea @thockin - 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024 .

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, I am tracking the following PRs, both of which look good:

• KEP-1880 Multiple Service CIDRs: Graduate to Beta (1/2) kubernetes#122047
• KEP-1880 Multiple Service CIDRs: Graduate to Beta (2/2) kubernetes#125021

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

This enhancement is now marked as tracked for code freeze for the {current release} Code Freeze!
As always, we are here to help if any questions come up. Thanks!

[tjons]

this was inadvertently added to the 1.32 board
/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in