-
Bug
-
Resolution: Done
-
Major
-
MCE 2.4.0, MCE 2.3.0, MCE 2.5.0
-
1
-
False
-
None
-
False
-
-
-
Moderate
-
No
Description of problem:
Console checks for node labels that have been deprecated since Kubernetes 1.17 to determine Region and Zone.
failure-domain.beta.kubernetes.io/region
failure-domain.beta.kubernetes.io/zone
https://kubernetes.io/docs/reference/labels-annotations-taints/#failure-domainbetakubernetesioregion
The preferred labels to use are:
topology.kubernetes.io/region
topology.kubernetes.io/zone
Similarly, beta.kubernetes.io/instance-type was deprecated in favour of node.kubernetes.io/instance-type.
https://kubernetes.io/docs/reference/labels-annotations-taints/#beta-kubernetes-io-instance-type-deprecated
Version-Release number of selected component (if applicable):
All
How reproducible:
Most clusters still have the deprecated labels, but some platforms may have switched to using the newer labels exclusively (for example, a Bare Metal cluster installed with Assisted Installer might omit the deprecated labels).
Steps to Reproduce:
- Obtain a cluster without theĀ failure-domain.beta.kubernetes.io labels on the nodes, or simply remove the labels from the nodes.
- Bring the cluster under ACM management by importing it or installing ACM on it.
- View the cluster details, then click on the nodes tab.
Actual results:
Region and Zone are missing.
Expected results:
Region and Zone should be populated according to the topology.kubernetes.io labels.
Additional info:
- clones
-
ACM-9003 Console does not show Region and Zone for nodes [MCE 2.3.5]
- Closed
- links to
-
RHSA-2023:125650 Multicluster Engine for Kubernetes 2.2.11 security updates and bug fixes