-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18.z, 4.19
-
None
Description of problem:
CNO doesn't propagate HCP labels to 2nd level operands
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create hostedCluster with .spec.Labels
Actual results:
cloud-network-config-controller, multus-admission-controller, network-node-identity, ovnkube-control-plane-6dd8775f97-75f89 pods don't have the specified labels.
Expected results:
cloud-network-config-controller, multus-admission-controller, network-node-identity, ovnkube-control-plane-6dd8775f97-75f89 pods have the specified labels.
Additional info:
- blocks
-
OCPBUGS-45057 CNO doesn't propagate HCP labels to 2nd level operands
- ON_QA
-
OCPSTRAT-1657 Add a Mechanism to Label all Pods for a Hosted Cluster in the Control Plane Namespace
- In Progress
- is cloned by
-
OCPBUGS-45057 CNO doesn't propagate HCP labels to 2nd level operands
- ON_QA
- links to