Skip to content

Commit 616df72

Browse files
committed
[OSDOCS-13296]: Adding network options to hosted cluster creation task
1 parent 21225e1 commit 616df72

File tree

1 file changed

+15
-9
lines changed

1 file changed

+15
-9
lines changed

modules/hcp-virt-create-hc-console.adoc

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,27 +12,33 @@ To create a hosted cluster with the KubeVirt platform by using the console, comp
1212

1313
. Open the {product-title} web console and log in by entering your administrator credentials.
1414

15-
. In the console header, ensure that **All Clusters** is selected.
15+
. In the console header, ensure that *All Clusters* is selected.
1616

17-
. Click **Infrastructure > Clusters**.
17+
. Click *Infrastructure > Clusters*.
1818

19-
. Click **Create cluster > Red Hat OpenShift Virtualization > Hosted**.
19+
. Click *Create cluster > Red Hat OpenShift Virtualization > Hosted*.
2020

21-
. On the **Create cluster** page, follow the prompts to enter details about the cluster and node pools.
21+
. On the *Create cluster* page, follow the prompts to enter details about the cluster and node pools.
2222
+
2323
[NOTE]
2424
====
25-
* If you want to use predefined values to automatically populate fields in the console, you can create a {VirtProductName} credential. For more information, see _Creating a credential for an on-premises environment_.
25+
* If you want to use predefined values to automatically populate fields in the console, you can create a {VirtProductName} credential. For more information, see "Creating a credential for an on-premises environment".
2626
2727
* On the *Cluster details* page, the pull secret is your {product-title} pull secret that you use to access {product-title} resources. If you selected a {VirtProductName} credential, the pull secret is automatically populated.
2828
====
2929
30-
. Review your entries and click **Create**.
30+
. On the *Node pools* page, expand the *Networking options* section and configure the networking options for your node pool:
3131
+
32-
The **Hosted cluster** view is displayed.
32+
.. In the *Additional networks* field, enter a network name in the format of `<namespace>/<name>`; for example, `my-namespace/network1`. The namespace and the name must be valid DNS labels. Multiple networks are supported.
33+
+
34+
.. By default, the *Attach default pod network* checkbox is selected. You can clear this checkbox only if additional networks exist.
35+
36+
. Review your entries and click *Create*.
37+
+
38+
The *Hosted cluster* view is displayed.
3339

34-
. Monitor the deployment of the hosted cluster in the **Hosted cluster** view. If you do not see information about the hosted cluster, ensure that **All Clusters** is selected, and click the cluster name.
40+
. Monitor the deployment of the hosted cluster in the *Hosted cluster* view. If you do not see information about the hosted cluster, ensure that *All Clusters* is selected, and click the cluster name.
3541

3642
. Wait until the control plane components are ready. This process can take a few minutes.
3743

38-
. To view the node pool status, scroll to the **NodePool** section. The process to install the nodes takes about 10 minutes. You can also click **Nodes** to confirm whether the nodes joined the hosted cluster.
44+
. To view the node pool status, scroll to the *NodePool* section. The process to install the nodes takes about 10 minutes. You can also click *Nodes* to confirm whether the nodes joined the hosted cluster.

0 commit comments

Comments
 (0)