-
Notifications
You must be signed in to change notification settings - Fork 198
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
chore: improve apiserver loadbalancer healthcheck #885
chore: improve apiserver loadbalancer healthcheck #885
Conversation
|
Welcome @esierra-stratio! |
Hi @esierra-stratio. Thanks for your PR. I'm waiting for a kubernetes-sigs 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/test-infra repository. |
/ok-to-test |
fix lint issue
d860582
to
aa63a56
Compare
/test ? |
@richardcase: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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/test-infra repository. |
any estimation of when this PR could be merged? |
/test pull-cluster-api-provider-gcp-capi-e2e |
/approve thanks |
/assign @richardcase |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, esierra-stratio 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 |
hi team! any estimation of when it can be merged? |
i am fine, any comments @richardcase otherwise we can merge this |
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
In some cases when kubelet running on a node accidentally stops working, it can lead to errors since the node appears as healthy backend in the apiserver load balancer even though etcd probe is returning
etcd failed reason withheld
In that scenario, the different calls made to the apiserver load balancer by the pieces on k8s may try to reach an unresponsive backend generating massive cluster issues.
Fixes #
Special notes for your reviewer:
TODOs:
Release note: