-
Notifications
You must be signed in to change notification settings - Fork 185
indicate connected client about server ability to serve requests #3386
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
indicate connected client about server ability to serve requests #3386
Conversation
leelavg
commented
Jul 23, 2025
- explicitly sets a key on client-op configmap for client to take decisions on co-location with hub
- explicity send a failed precondition when server not able to serve the connected client
/cherrypick release-4.19 |
@leelavg: once the present PR merges, I will cherry-pick it on top of In response to this:
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. |
dc88eb7
to
93dd507
Compare
28ed486
to
f360a79
Compare
1. explicitly sets a key on client-op configmap for client to take decisions on co-location with hub 2. explicity send a failed precondition when server not able to serve the connected client Signed-off-by: Leela Venkaiah G <[email protected]>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leelavg, nb-ohad 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 |
bf410db
into
red-hat-storage:main
@leelavg: new pull request created: #3388 In response to this:
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. |