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
Bug 1867608: ds/machine-config-daemon: Set maxUnavailable 10% #1992
Bug 1867608: ds/machine-config-daemon: Set maxUnavailable 10% #1992
Conversation
This is similar to others I'm updating as well, but for some reason this one feels riskier than those just given the criticality of MCO but I don't think it really is. Feedback welcome though. openshift/cluster-monitoring-operator#902 |
/retest |
/retitle Bug 1867608: ds/machine-config-daemon: Set maxUnavailable 10% |
/retest |
@sdodson: This pull request references Bugzilla bug 1867608, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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. |
/test e2e-aws |
@sdodson given how critical the MCO is, what do you think if we defer this to the next release to give it more and more time to soak? the issue is known (around timing) but it'll make us more comfortable and find us ready to debug if anything goes south. Would that work? |
/approve |
Yeah, I'm fine with deferring this as long as we're open to backporting to 4.6.z before it transitions to maintenance phase. This is just an optimization. |
/bugzilla refresh |
@sdodson: This pull request references Bugzilla bug 1867608, which is invalid:
Comment 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. |
@sdodson: The following tests failed, say
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/test-infra repository. I understand the commands that are listed here. |
/bugzilla refresh |
@sdodson: This pull request references Bugzilla bug 1867608, which is valid. 3 validation(s) were run on this bug
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. |
This daemonset is not critical to availability like SDN or DNS pods therefore allow maxUnavailable to scale with cluster size. This roughly increases rollout speed by 10x on a 250 node cluster.
ef0f01a
to
cff9a69
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, sdodson 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 Please review the full test history for this PR and help us cut down flakes. |
12 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@sdodson: All pull requests linked via external trackers have merged: Bugzilla bug 1867608 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 kubernetes/test-infra repository. |
This has sat in master for a month now and as far as I know there's been no ill effect. |
@sdodson: new pull request created: #2240 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. |
This daemonset is not critical to availability like SDN or DNS pods therefore
allow maxUnavailable to scale with cluster size. This roughly increases rollout
speed by 10x on a 250 node cluster.
How to verify this, provision a cluster with 20 or more hosts. Confirm that updates
to the machine-config-daemonset allows for up to 10% to update at once but otherwise
operates normally.