Bug 1987029

Summary: ROKS/hypershift: service-ca-operator produces an operand that selects master nodes
Product: OpenShift Container Platform Reporter: Cesar Wong <cewong>
Component: ibm-roks-toolkitAssignee: Cesar Wong <cewong>
Status: CLOSED ERRATA QA Contact: Jie Zhao <jiezhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.10CC: yli2
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-26 17:22:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Cesar Wong 2021-07-28 18:31:38 UTC
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):

How reproducible:

Steps to Reproduce:
1. Install 4.9 using Hypershift

Actual results:
The service-ca deployment in openshift-service-ca has a master node selector.

Expected results:
The service-ca deployment in openshift-service-ca does not select masters when Infrastructure.Status.ControlPlaneTopology is 'External'

Additional info:

Comment 7 errata-xmlrpc 2021-10-26 17:22:37 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.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.