-
Notifications
You must be signed in to change notification settings - Fork 40.9k
Don't log irrelevant zone hints message on no endpoints #132680
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
Don't log irrelevant zone hints message on no endpoints #132680
Conversation
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-sigs/prow repository. |
Hi @milesbxf. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/sig network |
cc. @danwinship as it looks like you last touched this code |
This is called from kubernetes/pkg/proxy/topology.go Line 44 in 95bff1b
/assign @danwinship |
Yeah, it would probably be good to just bail out of CategorizeEndpoints early if there aren't any endpoints. But we should still fix |
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.
Also, this needs an addition to the unit test in topology_test.go
Unit test added (thanks also for the clarification suggestion on the comment)
Happy to add this too - what are the expected return values if there are no endpoints? Would |
/ok-to-test please squash the commits , and you can add a separate commit with the
those are named variables so you can just |
Update pkg/proxy/topology.go Co-authored-by: Dan Winship <danwinship@redhat.com> Add unit test case
8a1761c
to
060f4ce
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.
looks good, just nitpicks
060f4ce
to
fbd2bd4
Compare
Thanks - I think I've addressed everything here + squashed |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, milesbxf 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 |
fbd2bd4
to
071b9f3
Compare
071b9f3
to
1cec0ac
Compare
/lgtm /test pull-kubernetes-e2e-gce Does not look related |
LGTM label has been added. Git tree hash: d291a683add2902945e3869817432bf34b191fbc
|
What type of PR is this?
/kind bug
What this PR does / why we need it:
See #132678 - kube-proxy is currently logging erroneous messages about ignoring topology hints when an endpointslice is empty. This short circuits the function and returns the default traffic distribution if there are no endpoints.
Which issue(s) this PR is related to:
Fixes #132678
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: