+++ This bug was initially created as a clone of Bug #2093852 +++ Description of problem: Console operator erroneously creates console deployment with an affinity rule when running in a cluster with HA control plane (ControlPlaneTopology=="HighlyAvailable"/"External") and non-HA infrastructure plane (InfrastructureTopology=="SingleReplica"). Version-Release number of selected component (if applicable): How reproducible: To reproduce the issue, create an OCP cluster with 3 control plane nodes and 1 worker node. Console deployment will have non-empty affinity clause, even though the number of console replicas is 1: ``` kind: Deployment apiVersion: apps/v1 ... name: console ... spec: replicas: 1 ... template: ... spec: ... affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchExpressions: - key: component operator: In values: - ui topologyKey: kubernetes.io/hostname ... ```` Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This issue causes console deployment updates to stall because new console replica will not start on the same single worker node due to the anti-affinity rule. --- Additional comment from jhadvig on 2022-06-06 08:34:42 UTC --- Created from https://github.com/openshift/console-operator/issues/656
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 (OpenShift Container Platform 4.10.33 bug fix 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. https://access.redhat.com/errata/RHBA-2022:6532