Bug 2106944

Summary: Affinity rule created in console deployment for single-replica infrastructure
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.11   
Target Milestone: ---   
Target Release: 4.10.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-21 14:10:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2111037    
Bug Blocks:    

Description OpenShift BugZilla Robot 2022-07-13 22:55:48 UTC 
+++ 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
Comment 5 errata-xmlrpc 2022-09-21 14:10:53 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 (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