[OSDOCS-15316]: Creating a hosted cluster on bare metal #96275
Conversation
openshift-ci
bot
added
the
size/M
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
from
a51c7f8 to
0c0d363
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
from
0c0d363 to
17bbb24
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
2 times, most recently
from
09a5173 to
4b08e25
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
3 times, most recently
from
73ffe57 to
daa7c37
Compare
openshift-ci
bot
added
size/L
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
from
daa7c37 to
e5561df
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
6 times, most recently
from
aba8843 to
30573c3
Compare
modules/hcp-bm-hc.adoc
Outdated
| @@ -20,6 +20,8 @@ As you create a hosted cluster, keep the following guidelines in mind: | |||
|
|
|||
| - The most common service publishing strategy is to expose services through a load balancer. That strategy is the preferred method for exposing the Kubernetes API server. If you create a hosted cluster by using the web console or by using {rh-rhacm-title}, to set a publishing strategy for a service besides the Kubernetes API server, you must manually specify the `servicePublishingStrategy` information in the `HostedCluster` custom resource. | |||
There was a problem hiding this comment.
We suggest to use a load balancer but by default with the hcp create agent command the bare metal hosted clusters are created with node port: we should indicate this here. We also should explain how to change the servicePublishingStrategy in the section to create bare metal hosted clusters as otherwise we leave this for the user to research with not even references to where. @jparrill ptal
There was a problem hiding this comment.
I updated the wording here, but I still need help to describe what users should do to change the servicePublishingStrategy.
| <9> Specify the availability policy for the hosted control plane components. Supported options are `SingleReplica` and `HighlyAvailable`. The default value is `HighlyAvailable`. | ||
| <10> Specify the supported {product-title} version that you want to use, for example, `4.19.0-multi`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_. | ||
| <10> Specify the supported {product-title} version that you want to use, for example, `4.19.0-multi`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see "Extracting the {product-title} release image digest". | ||
| <11> Specify the node pool replica count, for example, `3`. You must specify the replica count as `0` or greater to create the same number of replicas. Otherwise, no node pools are created. |
There was a problem hiding this comment.
We don't explain that in order to be able to add nodes to this cluster we must have previously added nodes to an InfraEnv (via web ui for example) and we don't explain how to do this. This leaves the user with a workflow that will always fail to complete as at this point the user hasn't been told how to add nodes to the inventory first.
There was a problem hiding this comment.
I added a new procedure before this procedure about adding bare-metal nodes to a hardware inventory.
modules/hcp-bm-hc.adoc
Outdated
| @@ -20,6 +20,8 @@ As you create a hosted cluster, keep the following guidelines in mind: | |||
|
|
|||
| - The most common service publishing strategy is to expose services through a load balancer. That strategy is the preferred method for exposing the Kubernetes API server. If you create a hosted cluster by using the web console or by using {rh-rhacm-title}, to set a publishing strategy for a service besides the Kubernetes API server, you must manually specify the `servicePublishingStrategy` information in the `HostedCluster` custom resource. | |||
|
|
|||
| - Ensure that you meet the requirements described in "Preparing to deploy {hcp} on bare metal", which includes requirements related to infrastructure, firewalls, ports, and services. | |||
There was a problem hiding this comment.
In the "Preparing to deploy hosted control planes on bare metal" in "Prerequisites to configure a management cluster" it's mentioned "You must add the topology.kubernetes.io/zone label to your bare-metal hosts on your management cluster. Ensure that each host has a unique value for topology.kubernetes.io/zone. Otherwise, all of the hosted control plane pods are scheduled on a single node, causing a single point of failure."
In my experience if you don't the hosted cluster creation command never completes. We should give an example of how to do that, e.g. on your management cluster run:
oc label node [worker-node-1] topology.kubernetes.io/zone=zone1
oc label node [worker-node-2] topology.kubernetes.io/zone=zone2
oc label node [worker-node-3] topology.kubernetes.io/zone=zone3
There was a problem hiding this comment.
Added to the prerequisites ✅
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
from
30573c3 to
cc2d20e
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
from
cc2d20e to
549af30
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
from
549af30 to
e15611b
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
4 times, most recently
from
531204b to
1104fb6
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
3 times, most recently
from
5dbf4ce to
007db9a
Compare
lahinson
force-pushed
the
osdocs-15316-hcp-bm-improvements
branch
from
007db9a to
d7dd5ba
Compare
|
@lahinson: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/OSDOCS-15316
Link to docs preview:
QE review:
Additional information: