-
Bug
-
Resolution: Done
-
Major
-
None
-
4.13, 4.12, 4.14
-
?
-
Important
-
No
-
SDN Sprint 233
-
1
-
Rejected
-
False
-
-
NA
This is a clone of issue OCPBUGS-8692. The following is the description of the original issue:
—
Description of problem:
In hypershift context: Operands managed by Operators running in the hosted control plane namespace in the management cluster do not honour affinity opinions https://hypershift-docs.netlify.app/how-to/distribute-hosted-cluster-workloads/ https://github.com/openshift/hypershift/blob/main/support/config/deployment.go#L263-L265 These operands running management side should honour the same affinity, tolerations, node selector and priority rules than the operator. This could be done by looking at the operator deployment itself or at the HCP resource. multus-admission-controller cloud-network-config-controller ovnkube-master
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a hypershift cluster. 2. Check affinity rules and node selector of the operands above. 3.
Actual results:
Operands missing affinity rules and node selecto
Expected results:
Operands have same affinity rules and node selector than the operator
Additional info:
- blocks
-
OCPBUGS-10319 Operands running management side missing affinity, tolerations, node selector and priority rules than the operator
- Closed
- clones
-
OCPBUGS-8692 Operands running management side missing affinity, tolerations, node selector and priority rules than the operator
- Closed
- is blocked by
-
OCPBUGS-8692 Operands running management side missing affinity, tolerations, node selector and priority rules than the operator
- Closed
- is cloned by
-
OCPBUGS-10319 Operands running management side missing affinity, tolerations, node selector and priority rules than the operator
- Closed
- links to