-
Bug
-
Resolution: Unresolved
-
Normal
-
4.18.z, 4.19.z, 4.20.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Bug Fix
-
Previously, control plane nodes created prior to OCP 4.12 would not have had the node-role.kubernetes.io/control-plane label. Now the MCO will add that label whenever it uncordons a control plane node if it was missing.
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-62321. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-58820. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-58180. The following is the description of the original issue:
—
Since 4.12 newly created masters have been labeled with `node-role.kubernetes.io/control-plane` but we never did anything to ensure the label is added to masters created in previous releases. Today we have more than 3,000 clusters where control plane hosts are not labeled with the newer label, we should add a one shot process that checks for the label on start up and applies it if not present.
For reference this is when the new label was added at node registration time https://github.com/openshift/machine-config-operator/pull/3273
- blocks
-
-
- Verified
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
-
- Verified
-
- is depended on by
-
-
- Closed
-
- links to
