-
Notifications
You must be signed in to change notification settings - Fork 328
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
OCPBUGS-42338: Update KCM node monitor grace period #5166
OCPBUGS-42338: Update KCM node monitor grace period #5166
Conversation
Follow-up to openshift#4786 The Kubernetes controller manager default for node monitor grace period is not sufficient to avoid node readiness flaps during brief connectivity problems. Change is restricted to IBMCloud only.
@jonesbr17: This pull request references Jira Issue OCPBUGS-42338, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
/lgtm
/retest-required |
/retest-required |
2 similar comments
/retest-required |
/retest-required |
/test okd-scos-e2e-aws-ovn |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jonesbr17, rtheis, sjenning 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 |
/retest-required |
3 similar comments
/retest-required |
/retest-required |
/retest-required |
/retest-required |
/retest-required |
retest-required |
/retest-required |
1 similar comment
/retest-required |
1 similar comment
/test e2e-kubevirt-aws-ovn-reduced |
@jonesbr17 please ask Red Hat for assistance since I be that we need them to override this failure. |
1 similar comment
@jonesbr17: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@jonesbr17: Jira Issue OCPBUGS-42338: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-42338 has been moved to the MODIFIED state. 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 openshift-eng/jira-lifecycle-plugin repository. |
/cherry-pick release-4.18 |
@rtheis: new pull request created: #5250 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. |
What this PR does / why we need it:
Follow-up to #4786
The Kubernetes controller manager default for node monitor grace period is not sufficient to avoid node readiness flaps during brief connectivity problems. Change is restricted to IBMCloud only.
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #https://issues.redhat.com/browse/OCPBUGS-42338
Checklist