+++ This bug was initially created as a clone of Bug #1783007 +++ Description of problem: The ingress operator computes a hash value for the deployment for an ingress controller and uses this hash value in the pod template spec's labels and affinity policy. This hash value includes the deployment's spec.replicas field, which is copied from the same field on the ingresscontroller, which means that scaling the ingresscontroller causes a rolling update of the deployment. This rolling update is unnecessary and should not happen. Version-Release number of selected component (if applicable): The deployment hashing is added in 4.3. How reproducible: The behavior is deterministic. Steps to Reproduce: 1. Scale an ingresscontroller: `oc -n openshift-ingress-operator scale ingresscontroller/default --replicas=3` Actual results: The ingresscontroller's deployment performs a rolling update (i.e., it scales up a new replicaset and scales down the old one). Expected results: Scaling the ingresscontroller should not trigger a rolling update (i.e., the existing replicaset should scale up or down, and the deployment should not create a new replicaset). Additional info: https://github.com/openshift/cluster-ingress-operator/pull/280/commits/0f6fd1c67dd719508c33e475ebda3f6e47052501 added the deployment hashing logic.
verified with 4.3.0-0.nightly-2019-12-13-180405 and issue has been fixed. $ oc get rs -n openshift-ingress NAME DESIRED CURRENT READY AGE router-default-85dc747cd8 2 2 2 46m $ oc scale ingresscontrollers.operator.openshift.io/default --replicas=1 -n openshift-ingress-operator ingresscontroller.operator.openshift.io/default scaled $ oc get rs -n openshift-ingress NAME DESIRED CURRENT READY AGE router-default-85dc747cd8 1 1 1 47m
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062