-
Notifications
You must be signed in to change notification settings - Fork 303
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
Make L4 NetLB Controller Healthcheck return error #1683
Conversation
Hi @cezarygerard. 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/test-infra repository. |
/assign @freehan @swetharepakula @kl52752 |
@cezarygerard: GitHub didn't allow me to assign the following users: kl52752. Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
10f1b53
to
134e1c5
Compare
134e1c5
to
7f0f162
Compare
plus minor name fix
7f0f162
to
4238cc0
Compare
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cezarygerard, swetharepakula 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 |
klog.Error(msg) | ||
// TODO return error here | ||
return fmt.Errorf(msg) |
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.
Error not Errorf
klog.Error(msg) | ||
return fmt.Errorf(msg) |
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.
error, not Errorf
Are we sure we want to immediately turn this healthcheck on vs having a flag and seeing how the metric behaves? If this is too sensitive when it rolls out to production, the only thing we can do at that point is to rollback. |
…c instead After discussion offline we decide that restarting controller on single healthckeck failure may be too invasive and reduce the reliability. This PR undoes the kubernetes#1683 and replaces healthcheck failure error with metric to count the errors.
…c instead After discussion offline we decide that restarting controller on single healthckeck failure may be too invasive and reduce the reliability. This PR undoes the kubernetes#1683 and replaces healthcheck failure error with metric to count the errors.
…c instead After discussion offline we decide that restarting controller on single healthckeck failure may be too invasive and reduce the reliability. This PR undoes the kubernetes#1683 and replaces healthcheck failure error with metric to count the errors.
This is required to correctly track availability SLO when L4 NetLB Controller get's stuck