-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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 TopologyAwareHints feature gate to be on by default #108747
Updating TopologyAwareHints feature gate to be on by default #108747
Conversation
Change-Id: Ib93157b2dc5f8c2cc19cb9b400e6e64563450de1
@robscott: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/lgtm I defer to Tim for approval
hmm, having a cluster in 1.23.4 that does not have a feature enabled by default and it does in 1.23.5 sounds a bit complex, in this case the the functionality does not seem a problem because of the annotation that you mention, but it runs additional code paths in the endpointslice controller (and IIRC we had a bug related to the nodename thing) kubernetes/pkg/controller/endpointslice/endpointslice_controller.go Lines 157 to 165 in e6c093d
What Jordan and Tim say? cc @liggitt |
I'd also be surprised to see this feature change default enablement in a patch release... is there a concrete problem if default enablement happens in 1.24? |
I can't support the cherry-pick either. :( /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 |
What type of PR is this?
/kind bug
/kind cleanup
What this PR does / why we need it:
This was the intention with #106433 and matches the docs we currently have for Topology Aware Hints. The net effect of this is just allowing a separate Service annotation opt-in to actually be effective. This will have no effect on users that are not explicitly trying to use this feature.
Special notes for your reviewer:
Would like to cherry pick this to 1.23 if possible.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig network
/priority important-soon
/cc @aojea @danwinship
/assign @thockin