-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
KEP-1880 alpha: IPAddresses #37620
KEP-1880 alpha: IPAddresses #37620
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
@aojea could you write a description for this PR? I'm not sure what you intend it to be, other than that it's related to the KEP that you mentioned. |
This will go for 1.27, it is not possible to me to deliver it this cycle |
Hi @aojea 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review as soon as possible. 01:00 UTC Wednesday 22nd March 2023 / 17:00 PDT Tuesday 21st March 2023 is the official deadline. This PR will need a doc review by Tuesday 4th April 2023 to get this into the release. Please reach out to required SIGs to get their review. Thank you! |
Signed-off-by: Antonio Ojea <aojea@google.com>
If you enable the `MultiCIDRServiceAllocator` | ||
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/), | ||
the control plane replaces the existing etcd allocator with a new one, using IPAddress | ||
objects instead of an internal global allocation map. The ClusterIP address | ||
associated to each `Service` will have a referenced IPAddress object. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you also need to enable an alpha API group for this to actually work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, good catch, it needs to enable networking.k8s.io/v1alpha1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is interesting, so if you only enable the feature gate it will fail to create any service
Co-authored-by: Qiming Teng <tengqm@outlook.com>
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: b0d97455e245d55224d09a2f792de9455eb7ae55
|
/approve |
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
/lgtm |
LGTM label has been added. Git tree hash: 9589bc6a212b8c8c25b5d8c5b6d660161a38dfbf
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LukeMwila, Rishit-dagli, sftim, thockin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The KEP-1880 introduces two new types: IPAddress and ServiceCIDR.
KEP-1880 is meant to address the main problems with the IP allocation on Services.
During the implementation. phase, we realized the need to align the use of ServiceCIDR with the other KEP that is introducing multiple ClusterCIDR as a new type https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2593-multiple-cluster-cidrs.
This is required because otherwise users can cause networking problems due to misconfigurations in their cluster.
Because of that, in this first iteration of the KEP-1880, only the new IPAddress object and its ClusterIP allocator is introduced.
kubernetes/enhancements#1880