-
Bug
-
Resolution: Done
-
Minor
-
4.17, 4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
2
-
Low
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 267
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Further clarification would be useful on the label required for HCP bare metal hosts.
Version-Release number of selected component (if applicable):
How reproducible:
N/A - Documentation issue.
Steps to Reproduce:
1.N/A documentation issue.
Actual results:
N/A Documentation issue.
Expected results:
N/A Documentation issue.
Additional info:
From this page: https://docs.openshift.com/container-platform/4.17/hosted_control_planes/hcp-deploy/hcp-deploy-bm.html#hcp-bm-prereqs_hcp-deploy-bm The current text is: ``` You must add the topology.kubernetes.io/zone label to your bare metal hosts on your management cluster. Otherwise, all of the hosted control plane pods are scheduled on a single node, causing single point of failure. ``` Suggestion to change to something like: ``` You must add the topology.kubernetes.io/zone label to your bare metal hosts on your management cluster, as well as using a different value for this label on each host. Otherwise, all of the hosted control plane pods are scheduled on a single node, causing single point of failure. ``` It is necessary to use a different value for this label or else you get the failure described in the text.