Description of problem:
When running in a topology that has an external control plane like ROKS or Hypershift, workloads should not include a master node selector because there are no master nodes. The service-ca-operator itself is not scheduled on masters because of its cluster profile. However, its operand includes a master node selector.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install 4.9 using Hypershift
The service-ca deployment in openshift-service-ca has a master node selector.
The service-ca deployment in openshift-service-ca does not select masters when Infrastructure.Status.ControlPlaneTopology is 'External'
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.9.4 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.