Skip to content

Commit 71213d6

Browse files
lahinsonlahinson
committed
[OSDOCS-15316]: Creating a hosted cluster on bare metal
1 parent 112ba36 commit 71213d6

File tree

6 files changed

+412
-40
lines changed

6 files changed

+412
-40
lines changed

‎hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,16 +48,23 @@ include::modules/hcp-bm-infra-reqs.adoc[leveloffset=+2]
4848
include::modules/hcp-bm-dns.adoc[leveloffset=+1]
4949
include::modules/hcp-custom-dns.adoc[leveloffset=+2]
5050

51-
include::modules/hcp-bm-hc.adoc[leveloffset=+1]
51+
[id="hcp-bm-create-hc_{context}"]
52+
== Creating a hosted cluster on bare metal
53+
54+
When you create a hosted cluster with the Agent platform, the HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace. You can create a hosted cluster on bare metal or you can import one.
55+
56+
include::modules/hcp-bm-hc.adoc[leveloffset=+2]
5257

5358
[role="_additional-resources"]
5459
.Additional resources
5560
* xref:../../hosted_control_planes/hcp-import.adoc[Manually importing a hosted cluster]
61+
* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#configure-hosted-disconnected-digest-image[Extracting the {product-title} release image digest]
5662

5763
include::modules/hcp-bm-hc-console.adoc[leveloffset=+2]
5864

59-
.Next steps
60-
* To access the web console, see xref:../../web_console/web-console.adoc#web-console-overview[Accessing the web console].
65+
[role="_additional-resources"]
66+
.Additional resources
67+
* xref:../../web_console/web-console.adoc#web-console-overview[Accessing the web console]
6168

6269
include::modules/hcp-bm-hc-mirror.adoc[leveloffset=+2]
6370

@@ -67,4 +74,4 @@ include::modules/hcp-bm-hc-mirror.adoc[leveloffset=+2]
6774
* To add hosts to the host inventory by using the Discovery Image, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/clusters/cluster_mce_overview#add-host-host-inventory[Adding hosts to the host inventory by using the Discovery Image].
6875
* To extract the {product-title} release image digest, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/clusters/cluster_mce_overview#configure-hosted-disconnected-digest-image[Extracting the {product-title} release image digest].
6976

70-
include::modules/hcp-bm-verify.adoc[leveloffset=+1]
77+
include::modules/hcp-bm-verify.adoc[leveloffset=+1]

‎hosted_control_planes/hcp-deploy/hcp-deploy-ibm-power.adoc

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,17 @@ include::modules/hcp-ibm-power-infra-reqs.adoc[leveloffset=+1]
3737
include::modules/hcp-ibm-power-dns.adoc[leveloffset=+1]
3838
include::modules/hcp-custom-dns.adoc[leveloffset=+2]
3939

40-
include::modules/hcp-bm-hc.adoc[leveloffset=+1]
40+
[id="hcp-bm-create-hc-ibm-power"]
41+
== Creating a hosted cluster on bare metal
42+
43+
When you create a hosted cluster with the Agent platform, the HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace. You can create a hosted cluster on bare metal or you can import one.
44+
45+
include::modules/hcp-bm-hc.adoc[leveloffset=+2]
46+
47+
[role="_additional-resources"]
48+
.Additional resources
49+
* xref:../../hosted_control_planes/hcp-import.adoc[Manually importing a hosted cluster]
50+
* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#configure-hosted-disconnected-digest-image[Extracting the {product-title} release image digest]
4151

4252
[id="hcp-ibm-power-heterogeneous-nodepools_{context}"]
4353
== Creating heterogeneous node pools on agent hosted clusters

‎hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,11 +43,17 @@ include::modules/hcp-ibm-z-infra-reqs.adoc[leveloffset=+1]
4343
include::modules/hcp-ibm-z-dns.adoc[leveloffset=+1]
4444
include::modules/hcp-custom-dns.adoc[leveloffset=+2]
4545

46-
include::modules/hcp-bm-hc.adoc[leveloffset=+1]
46+
[id="hcp-bm-create-hc-ibm-z"]
47+
== Creating a hosted cluster on bare metal
48+
49+
When you create a hosted cluster with the Agent platform, the HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace. You can create a hosted cluster on bare metal or you can import one.
50+
51+
include::modules/hcp-bm-hc.adoc[leveloffset=+2]
4752

4853
[role="_additional-resources"]
4954
.Additional resources
50-
55+
* xref:../../hosted_control_planes/hcp-import.adoc[Manually importing a hosted cluster]
56+
* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#configure-hosted-disconnected-digest-image[Extracting the {product-title} release image digest]
5157
* xref:../../hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc#hcp-bm-hc-console_hcp-deploy-bm[Creating a hosted cluster on bare metal by using the console]
5258

5359
include::modules/hcp-ibm-z-infraenv.adoc[leveloffset=+1]

‎modules/hcp-bm-autoscale.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
//
33
// * hosted_control_planes/hcp-manage/hcp-manage-bm.adoc
44
// * hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc
5+
// * hosted_control_planes/hcp-manage/hcp-manage-virt.adoc
56

67
:_mod-docs-content-type: PROCEDURE
78
[id="hcp-bm-autoscale_{context}"]

‎modules/hcp-bm-dns.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88

99
The API Server for the hosted cluster is exposed as a `NodePort` service. A DNS entry must exist for `api.<hosted_cluster_name>.<base_domain>` that points to destination where the API Server can be reached.
1010

11-
The DNS entry can be as simple as a record that points to one of the nodes in the managed cluster that is running the hosted control plane. The entry can also point to a load balancer that is deployed to redirect incoming traffic to the ingress pods.
11+
The DNS entry can be as simple as a record that points to one of the nodes in the management cluster that is running the hosted control plane. The entry can also point to a load balancer that is deployed to redirect incoming traffic to the ingress pods.
1212

1313
.Example DNS configuration
1414
[source,terminal]
@@ -22,6 +22,11 @@ api-int.example.krnl.es. IN A 192.168.122.22
2222
`*`.apps.example.krnl.es. IN A 192.168.122.23
2323
----
2424

25+
[NOTE]
26+
====
27+
In the previous example, `*.apps.example.krnl.es. IN A 192.168.122.23` is either a node in the hosted cluster or a load balancer, if one has been configured.
28+
====
29+
2530
If you are configuring DNS for a disconnected environment on an IPv6 network, the configuration looks like the following example.
2631

2732
.Example DNS configuration for an IPv6 network

0 commit comments

Comments
 (0)