-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.12.z
-
Important
-
No
-
SDN Sprint 233
-
1
-
Rejected
-
False
-
Description of problem:
When running on hypershift, pods managed by the CNO do not get the same tolerations as other pods in the control plane namespace: - effect: NoSchedule key: hypershift.openshift.io/control-plane operator: Equal value: "true" - effect: NoSchedule key: hypershift.openshift.io/cluster operator: Equal value: CLUSTER-NS-NAME
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a HyperShift cluster with release 4.12.4 2. Look at the taints for CNO-managed pods in the hosted control plane namespace.
Actual results:
Pods do not have `hypershift.openshift.io/control-plane` or `hypershift.openshift.io/cluster` taints.
Expected results:
Pods have `hypershift.openshift.io/control-plane` and `hypershift.openshift.io/cluster` taints.
Additional info:
- blocks
-
HOSTEDCP-546 Provide a mechanism for operands to get control plane affinity and priority rules
- Closed