-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Truncate endpoints over a 1000 addresses #103520
Truncate endpoints over a 1000 addresses #103520
Conversation
/triage accepted |
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.
Thanks!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: swetharepakula, 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 |
0a37eb1
to
36c48f2
Compare
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.
Thanks for the work on this! Mostly LGTM.
/hold |
36c48f2
to
5d84dbc
Compare
5d84dbc
to
8522bdb
Compare
/hold cancel Updated the approach to truncate proportionally across the subsets |
/milestone v1.22 |
/retest |
8522bdb
to
9d4b2e1
Compare
Thanks! /lgtm |
* set `endpoints.kubernetes.io/over-capacity` to "truncated" when number of addresses has been truncated to a 1000 * ready addresses are prioritized over non-ready addresses * addresses are proportionally truncated across subsets
9d4b2e1
to
9bd857c
Compare
Thanks! /lgtm |
/retest |
/retest |
endpoints.kubernetes.io/over-capacity
to "truncated" whennumber of addresses has been truncated to a 1000
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR will enforce the recommended 1000 endpoint maxCapacity limit on Endpoints resources. If the number of endpoints exceeds 1000, they will be truncated now.
Special notes for your reviewer:
This is the final PR needed to close out KEP: EndpointSlice KEP.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
KEP: EndpointSlice KEP
Enhancement Issue: kubernetes/enhancements#752
/cc @aojea @andrewsykim @liggitt @robscott @wojtek-t
/assign @thockin
/sig network
/priority important-soon