-
Notifications
You must be signed in to change notification settings - Fork 1.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
Updating topology KEPs to reflect updated 1.21 alpha target #2153
Conversation
@@ -183,6 +183,11 @@ between expected endpoints and actual endpoints in the zone). | |||
- Autoscaling will not behave well if only a single zone is receiving large | |||
amounts of traffic. This could potentially be mitigated by separating | |||
deployments and HPAs per zone. | |||
- Services with ExternalTrafficPolicy=local will need special treatment here. |
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.
- Services with ExternalTrafficPolicy=local will need special treatment here. | |
- Services with ExternalTrafficPolicy=Local will need special treatment here. |
@@ -535,8 +540,9 @@ EPEachZonePerSync = metrics.NewHistogramVec( | |||
### Graduation Criteria | |||
- Alpha should provide basic functionality covered with tests described above. | |||
- This KEP will largely depend on the EndpointSlice Subsetting. Once the | |||
EndpointSlice Subsetting feature has been updated, our change can kick-in | |||
without any new fields being added. | |||
EndpointSlice Subsetting feature has been updated, our change can kick-in |
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.
EndpointSlice Subsetting feature has been updated, our change can kick-in | |
EndpointSlice Subsetting feature has been updated, our change can kick in |
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: robscott, 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 |
This also adds some notes about node local traffic and DNS.
/assign @thockin