Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions modules/hcp-bm-hc.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -65,16 +65,15 @@ $ hcp create cluster agent \
--pull-secret=<path_to_pull_secret> \
--agent-namespace=<hosted_control_plane_namespace> \
--base-domain=<base_domain> \
--api-server-address=api.<hosted_cluster_name>.<base_domain>
--api-server-address=api.<hosted_cluster_name>.<base_domain> \
--etcd-storage-class=<etcd_storage_class> \
--ssh-key=<path_to_ssh_key> \
--namespace=<hosted_cluster_namespace> \
--control-plane-availability-policy=HighlyAvailable \
--release-image=quay.io/openshift-release-dev/ocp-release:<ocp_release_image>-multi \
--node-pool-replicas=<node_pool_replica_count> \
--render \
--render-sensitive \
--ssh-key <home_directory>/<path_to_ssh_key>/<ssh_key> > hosted-cluster-config.yaml
--render-sensitive > hosted-cluster-config.yaml
----
+
where:
Expand All @@ -90,7 +89,6 @@ where:
`control-plane-availability-policy`:: Specifies the availability policy for the hosted control plane components. Supported options are `SingleReplica` and `HighlyAvailable`. The default value is `HighlyAvailable`.
`<ocp_release_image>`:: Specifies the supported {product-title} version that you want to use, such as `4.22.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".
`<node_pool_replica_count>`:: Specifies the node pool replica count, such as `3`. You must specify the replica count as `0` or greater to create the same number of replicas. Otherwise, you do not create node pools.
`<home_directory>/<path_to_ssh_key>/<ssh_key>`:: Specifies the path to the SSH key, such as `user/.ssh/id_rsa`.

. Configure the service publishing strategy. By default, hosted clusters use the `NodePort` service publishing strategy because node ports are always available without additional infrastructure. However, you can configure the service publishing strategy to use a load balancer.

Expand Down