Merge pull request #7346 from stolostron/swope-install

https://issues.redhat.com/browse/ACM-15363--making 2.12 match the oth…

clusters/install_upgrade/install_connected.adoc

@@ -192,7 +192,7 @@ spec:
 ----
 
 +
-*Note:* To configure infrastructure nodes, see xref:./config_infra_nodes.adoc#config-infra-node-mce[Configuring infrastructure nodes for {mce-short}].
+*Note:* To configure infrastructure nodes, see xref:./config_infra_nodes_mce.adoc#config-infra-node-mce[Configuring infrastructure nodes for {mce-short}].
 
 = 
 +
@@ -249,4 +249,4 @@ If you are reinstalling the {mce-short} and the pods do not start, see xref:./un
 {mce-short} and to any user credentials with access to the namespace where you install 
 {mce-short}.
 
-You can now configure your {ocp-short} cluster to contain infrastructure nodes to run approved management components. Running components on infrastructure nodes avoids allocating {ocp-short} subscription quota for the nodes that are running those management components. See xref:./config_infra_nodes.adoc#config-infra-node-mce[Configuring infrastructure nodes for {mce-short}] for that procedure.
+You can now configure your {ocp-short} cluster to contain infrastructure nodes to run approved management components. Running components on infrastructure nodes avoids allocating {ocp-short} subscription quota for the nodes that are running those management components. See xref:./config_infra_nodes_mce.adoc#config-infra-node-mce[Configuring infrastructure nodes for {mce-short}] for that procedure.

clusters/install_upgrade/install_intro.adoc

@@ -16,7 +16,7 @@ For full support information, see the link:https://access.redhat.com/articles/70
 See the following documentation:
 
 * xref:./install_connected.adoc#installing-while-connected-online-mce[Installing while connected online]
-* xref:./config_infra_nodes.adoc#config-infra-node-mce[Configuring infrastructure nodes for {mce-short}]
+* xref:./config_infra_nodes_mce.adoc#config-infra-node-mce[Configuring infrastructure nodes for {mce-short}]
 * xref:./install_disconnected.adoc#install-on-disconnected-networks[Installing on disconnected networks]
 * xref:./uninstall.adoc#uninstalling-mce[Uninstalling]
 * xref:../about/mce_networking.adoc#mce-network-configuration[Network configuration]

clusters/main.adoc

@@ -13,7 +13,7 @@ include::release_notes/mce_known_issues.adoc[leveloffset=+3]
 include::release_notes/mce_deprecate_remove.adoc[leveloffset=+3]
 include::install_upgrade/install_intro.adoc[leveloffset=+2]
 include::install_upgrade/install_connected.adoc[leveloffset=+3]
-include::install_upgrade/config_infra_nodes.adoc[leveloffset=+3]
+include::install_upgrade/config_infra_nodes_mce.adoc[leveloffset=+3]
 include::install_upgrade/install_disconnected.adoc[leveloffset=+3]
 include::install_upgrade/adv_config_install.adoc[leveloffset=+3]
 include::install_upgrade/uninstall.adoc[leveloffset=+3]

install/install_connected.adoc

@@ -259,7 +259,7 @@ oc get mch -o yaml
 
 - *Important:* For security reasons, do not give access to the `local-cluster` namespace to any user that is not a `cluster-administrator`.
 
-You can now configure your {ocp-short} cluster to contain infrastructure nodes to run approved management components. Running components on infrastructure nodes avoids allocating {ocp-short} subscription quota for the nodes that are running those management components. See xref:../install/config_infra_nodes.adoc#config-infra-node-acm[Configuring infrastructure nodes for {acm-short}] for that procedure.
+You can now configure your {ocp-short} cluster to contain infrastructure nodes to run approved management components. Running components on infrastructure nodes avoids allocating {ocp-short} subscription quota for the nodes that are running those management components. See xref:../install/config_infra_nodes_acm.adoc#config-infra-node-acm[Configuring infrastructure nodes for {acm-short}] for that procedure.
 
 [#additional-resources-install]
 

install/install_overview.adoc

@@ -20,7 +20,7 @@ The documentation references the earliest supported {ocp-short} version, unless
 Installing {acm} sets up a multi-node cluster production environment. You can install {acm} in either standard or high-availability configurations. View the following documentation for more information about the installation and upgrade procedures, as well as information about advanced configuration, scalability, and sizing:
 
 * xref:../install/install_connected.adoc#installing-while-connected-online[Installing while connected online]
-* xref:../install/config_infra_nodes.adoc#config-infra-node-acm[Configuring infrastructure nodes for {acm-short}]
+* xref:../install/config_infra_nodes_acm.adoc#config-infra-node-acm[Configuring infrastructure nodes for {acm-short}]
 * xref:../install/install_disconnected.adoc#install-on-disconnected-networks[Install on disconnected networks]
 * xref:../install/cluster_size.adoc#sizing-your-cluster[Sizing your cluster]
 * xref:../install/perform_scale.adoc#performance-and-scalability[Performance and scalability]

install/main.adoc

@@ -6,7 +6,7 @@ include::install_overview.adoc[leveloffset=+1]
 include::perform_scale.adoc[leveloffset=+2]
 include::cluster_size.adoc[leveloffset=+3]
 include::install_connected.adoc[leveloffset=+2]
-include::config_infra_nodes.adoc[leveloffset=+2]
+include::config_infra_nodes_acm.adoc[leveloffset=+2]
 include::install_disconnected.adoc[leveloffset=+2]
 include::adv_config_install.adoc[leveloffset=+2]
 include::upgrade_hub.adoc[leveloffset=+2]