Bug 1938920 - ovnkube-master/ovs-node DaemonSets should use maxUnavailable: 10%
Summary: ovnkube-master/ovs-node DaemonSets should use maxUnavailable: 10%
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Vadim Rutkovsky
QA Contact: Dan Brahaney
Depends On:
TreeView+ depends on / blocked
Reported: 2021-03-15 08:26 UTC by Vadim Rutkovsky
Modified: 2021-07-27 22:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: ovs-node has maxUnavailable set to 25% Consequence: updates on large clusters update one quarter of the cluster nodes causing potential disruption Fix: maxUnavalable for this DS is set to 10% Result: user workloads are less likely to be disrupted
Clone Of:
Last Closed: 2021-07-27 22:53:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1020 0 None open Bug 1938920: Set maxUnavailable for ovnkube-master and ovs-node daemonsets 2021-03-15 08:32:02 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:53:42 UTC

Description Vadim Rutkovsky 2021-03-15 08:26:30 UTC
This bug was initially created as a copy of Bug #1933173

I am copying this bug because it also applies to OVN

It's currently maxUnavailable: 1, but we want maxUnavailable: 10%, so we scale better on clusters with large node-counts.  Checking a recent 4.8 CI release:

$ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-4.8/1364411741282242560/artifacts/e2e-gcp/daemonsets.json | jq -r '.items[] | select(.spec.template.spec.nodeSelector["node-role.kubernetes.io/master"] != "" and .spec.updateStrategy.rollingUpdate.maxUnavailable != "10%") | .metadata.namespace + " " + .metadata.name + " " + (.spec.template.spec.nodeSelector | tostring) + " " + (.spec.updateStrategy | tostring)'
openshift-sdn sdn {"kubernetes.io/os":"linux"} {"rollingUpdate":{"maxUnavailable":1},"type":"RollingUpdate"}

Like bug 1933159, but different DaemonSet.

Comment 3 Dan Brahaney 2021-04-08 14:09:44 UTC
❯ oc get -o yaml -n openshift-ovn-kubernetes ds ovs-node
apiVersion: apps/v1
kind: DaemonSet
      maxSurge: 0
      maxUnavailable: 10%
    type: RollingUpdate

Verified on build registry.ci.openshift.org/ocp/release:4.8.0-0.nightly-2021-04-08-005413

Comment 6 errata-xmlrpc 2021-07-27 22:53:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.