Skip to content

Commit 5c294a5

Browse files
xenolinuxxenolinux
committed
Manage headings
1 parent b1caac8 commit 5c294a5

19 files changed

+72
-28
lines changed

‎_topic_maps/_topic_map.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2505,7 +2505,7 @@ Topics:
25052505
File: hcp-deploy-bm
25062506
- Name: Deploying hosted control planes on OpenShift Virtualization
25072507
File: hcp-deploy-virt
2508-
- Name: Deploying hosted control planes on non-bare metal agent machines
2508+
- Name: Deploying hosted control planes on non-bare-metal agent machines
25092509
File: hcp-deploy-non-bm
25102510
- Name: Deploying hosted control planes on IBM Z
25112511
File: hcp-deploy-ibmz
@@ -2520,7 +2520,7 @@ Topics:
25202520
File: hcp-manage-bm
25212521
- Name: Managing hosted control planes on OpenShift Virtualization
25222522
File: hcp-manage-virt
2523-
- Name: Managing hosted control planes on non-bare metal agent machines
2523+
- Name: Managing hosted control planes on non-bare-metal agent machines
25242524
File: hcp-manage-non-bm
25252525
- Name: Managing hosted control planes on IBM Power
25262526
File: hcp-manage-ibm-power
@@ -2579,7 +2579,7 @@ Topics:
25792579
File: hcp-destroy-ibmz
25802580
- Name: Destroying a hosted cluster on IBM Power
25812581
File: hcp-destroy-ibm-power
2582-
- Name: Destroying a hosted cluster on non-bare metal agent machines
2582+
- Name: Destroying a hosted cluster on non-bare-metal agent machines
25832583
File: hcp-destroy-non-bm
25842584
- Name: Manually importing a hosted cluster
25852585
File: hcp-import

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
:_mod-docs-content-type: ASSEMBLY
22
[id="hcp-deploy-non-bm"]
33
include::_attributes/common-attributes.adoc[]
4-
= Deploying {hcp} on non-bare metal agent machines
4+
= Deploying {hcp} on non-bare-metal agent machines
55
:context: hcp-deploy-non-bm
66

77
toc::[]

‎hosted_control_planes/hcp-destroy/hcp-destroy-non-bm.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
:_mod-docs-content-type: ASSEMBLY
22
[id="hcp-destroy-non-bm"]
33
include::_attributes/common-attributes.adoc[]
4-
= Destroying a hosted cluster on non-bare metal agent machines
4+
= Destroying a hosted cluster on non-bare-metal agent machines
55
:context: hcp-destroy-non-bm
66

77
toc::[]
88

9-
You can destroy hosted clusters on non-bare metal agent machines by using the command-line interface (CLI) or the {mce-short} web console.
9+
You can destroy hosted clusters on non-bare-metal agent machines by using the command-line interface (CLI) or the {mce-short} web console.
1010

1111
include::modules/destroy-hc-non-bm-cli.adoc[leveloffset=+1]
1212

‎hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
:_mod-docs-content-type: ASSEMBLY
22
[id="hcp-manage-non-bm"]
33
include::_attributes/common-attributes.adoc[]
4-
= Managing {hcp} on non-bare metal agent machines
4+
= Managing {hcp} on non-bare-metal agent machines
55
:context: hcp-manage-non-bm
66

77
toc::[]
88

9-
After you deploy {hcp} on non-bare metal agent machines, you can manage a hosted cluster by completing the following tasks.
9+
After you deploy {hcp} on non-bare-metal agent machines, you can manage a hosted cluster by completing the following tasks.
1010

1111
include::modules/hcp-bm-access.adoc[leveloffset=+1]
1212
include::modules/hcp-bm-scale-np.adoc[leveloffset=+1]

‎modules/destroy-hc-non-bm-cli.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44

55
:_mod-docs-content-type: PROCEDURE
66
[id="destroy-hc-non-bm-cli_{context}"]
7-
= Destroying a hosted cluster on non-bare metal agent machines
7+
= Destroying a hosted cluster on non-bare-metal agent machines
88

9-
You can use the `hcp` command-line interface (CLI) to destroy a hosted cluster on non-bare metal agent machines.
9+
You can use the `hcp` command-line interface (CLI) to destroy a hosted cluster on non-bare-metal agent machines.
1010

1111
.Procedure
1212

‎modules/destroy-hc-non-bm-console.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44

55
:_mod-docs-content-type: PROCEDURE
66
[id="destroy-hc-non-bm-console_{context}"]
7-
= Destroying a hosted cluster on non-bare metal agent machines by using the web console
7+
= Destroying a hosted cluster on non-bare-metal agent machines by using the web console
88

9-
You can use the {mce-short} web console to destroy a hosted cluster on non-bare metal agent machines.
9+
You can use the {mce-short} web console to destroy a hosted cluster on non-bare-metal agent machines.
1010

1111
.Procedure
1212

‎modules/hcp-bm-ingress.adoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,19 @@
33
// * hosted_control_planes/hcp-manage/hcp-manage-bm.adoc
44
// * hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc
55

6+
ifeval::["{context}" == "hcp-manage-non-bm"]
7+
:non-bm:
8+
endif::[]
9+
610
:_mod-docs-content-type: PROCEDURE
711
[id="hcp-bm-ingress_{context}"]
12+
ifndef::non-bm[]
813
= Handling ingress in a hosted cluster on bare metal
14+
endif::non-bm[]
15+
16+
ifdef::non-bm[]
17+
= Handling ingress in a hosted cluster on non-bare-metal agent machines
18+
endif::non-bm[]
919

1020
Every {product-title} cluster has a default application Ingress Controller that typically has an external DNS record associated with it. For example, if you create a hosted cluster named `example` with the base domain `krnl.es`, you can expect the wildcard domain `*.apps.example.krnl.es` to be routable.
1121

@@ -195,3 +205,8 @@ clusteroperator.config.openshift.io/ingress
195205
----
196206
+
197207
Replace `<4.x.y>` with the supported {product-title} version that you want to use, for example, `4.17.0-multi`.
208+
209+
210+
ifeval::["{context}" == "hcp-manage-non-bm"]
211+
:!non-bm:
212+
endif::[]

‎modules/hcp-bm-machine-health-disable.adoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,20 @@
33
// * hosted_control_planes/hcp-manage/hcp-manage-bm.adoc
44
// * hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc
55

6+
ifeval::["{context}" == "hcp-manage-non-bm"]
7+
:non-bm:
8+
endif::[]
9+
610
:_mod-docs-content-type: PROCEDURE
711
[id="hcp-bm-machine-health-disable_{context}"]
12+
ifndef::non-bm[]
813
= Disabling machine health checks on bare metal
14+
endif::non-bm[]
15+
16+
ifdef::non-bm[]
17+
= Disabling machine health checks on non-bare-metal agent machines
18+
endif::non-bm[]
19+
920

1021
To disable machine health checks for the managed cluster nodes, modify the `NodePool` resource.
1122

@@ -24,3 +35,7 @@ $ oc patch nodepool -n <hosted_cluster_namespace> <nodepool_name> -p '{"spec": {
2435
----
2536
$ oc get nodepool -n <hosted_cluster_namespace> <nodepool_name> -o yaml | grep autoRepair
2637
----
38+
39+
ifeval::["{context}" == "hcp-manage-non-bm"]
40+
:!non-bm:
41+
endif::[]

‎modules/hcp-bm-machine-health.adoc

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,19 @@
33
// * hosted_control_planes/hcp-manage/hcp-manage-bm.adoc
44
// * hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc
55

6+
ifeval::["{context}" == "hcp-manage-non-bm"]
7+
:non-bm:
8+
endif::[]
9+
610
:_mod-docs-content-type: PROCEDURE
711
[id="hcp-bm-machine-health_{context}"]
12+
ifndef::non-bm[]
813
= Enabling machine health checks on bare metal
14+
endif::non-bm[]
15+
16+
ifdef::non-bm[]
17+
= Enabling machine health checks on non-bare-metal agent machines
18+
endif::non-bm[]
919

1020
You can enable machine health checks on bare metal to repair and replace unhealthy managed cluster nodes automatically. You must have additional agent machines that are ready to install in the managed cluster.
1121

@@ -53,3 +63,7 @@ $ oc patch nodepool -n <hosted_cluster_namespace> <nodepool_name> -p '{"spec": {
5363
----
5464
$ oc get nodepool -n <hosted_cluster_namespace> <nodepool_name> -o yaml | grep autoRepair
5565
----
66+
67+
ifeval::["{context}" == "hcp-manage-non-bm"]
68+
:!non-bm:
69+
endif::[]

‎modules/hcp-non-bm-dns.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
:_mod-docs-content-type: CONCEPT
66
[id="hcp-non-bm-dns_{context}"]
7-
= Configuring DNS on non-bare metal agent machines
7+
= Configuring DNS on non-bare-metal agent machines
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>.<basedomain>` that points to destination where the API Server can be reached.
1010

0 commit comments

Comments
 (0)