Merge pull request #100781 from sr1kar99/tnf-tp-updates-main

OSDOCS#12987: Fixed issues in TNF docs

Author: mburke5678

installing/installing_two_node_cluster/installing_tnf/install-post-tnf.adoc

@@ -6,6 +6,11 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+The following sections help with recovering from issues in a two-node OpenShift cluster with fencing.
+
+:FeatureName: Two-node OpenShift cluster with fencing
+include::snippets/technology-preview.adoc[leveloffset=+1]
+
 // Manually recovering from a disruption event when automated recovery is unavailable
 include::modules/installation-manual-recovering-when-auto-recovery-is-unavail.adoc[leveloffset=+1]
 

installing/installing_two_node_cluster/installing_tnf/install-tnf.adoc

@@ -8,10 +8,8 @@ toc::[]
 
 You can deploy a two-node OpenShift cluster with fencing by using either the installer-provisioned infrastructure or the user-provisioned infrastructure installation method. The following examples provide sample `install-config.yaml` configurations for both methods.
 
-[NOTE]
-====
-Do an etcd backup before proceeding to ensure that you can restore the cluster if any issues occur.
-====
+:FeatureName: Two-node OpenShift cluster with fencing
+include::snippets/technology-preview.adoc[leveloffset=+1]
 
 // Sample install-config.yaml for a two-node installer-provisioned infrastructure cluster with fencing
 include::modules/installation-sample-install-config-two-node-fencing-ipi.adoc[leveloffset=+1]

installing/installing_two_node_cluster/installing_tnf/installing-two-node-fencing.adoc

@@ -37,6 +37,7 @@ The two-node OpenShift cluster with fencing requires the following hosts:
 |===
 
 The bootstrap and control plane machines must use Red Hat Enterprise Linux CoreOS (RHCOS) as the operating system. For instructions on installing RHCOS and starting the bootstrap process, see xref:../../../installing/installing_bare_metal/upi/installing-bare-metal#creating-machines-bare-metal_installing-bare-metal[Installing RHCOS and starting the {product-title} bootstrap process]
+
 [NOTE]
 ====
 The requirement to use RHCOS applies only to user-provisioned infrastructure deployments. For installer-provisioned infrastructure deployments, the bootstrap and control plane machines are provisioned automatically by the installation program, and you do not need to manually install RHCOS.

modules/installation-manual-recovering-when-auto-recovery-is-unavail.adoc

@@ -73,7 +73,7 @@ Review all Pacemaker activity on the node by running the following command:
 $ sudo journalctl -u pacemaker
 ----
 +
-Diagnose etcd resource startup issues byrunning the following command:
+Diagnose etcd resource startup issues by running the following command:
 +
 [source,terminal]
 ----

modules/installation-replacing-control-plane-nodes.adoc

@@ -92,7 +92,7 @@ $ sudo OCF_RESKEY_CRM_meta_notify_start_resource='etcd' pcs resource debug-start
 +
 After recovery, etcd must be running successfully on the survivor node.
 
-. Delete etcd secrets for the failed node by running the following command:
+. Delete etcd secrets for the failed node by running the following commands:
 +
 [source,terminal]
 ----
@@ -174,7 +174,7 @@ You must perform this step only if you are using installer-provisioned infrastru
 For information about replacing a failed bare-metal control plane node, see "Replacing an unhealthy etcd member on bare metal".
 ====
 
-.. Remove the BMH and `Machine` objects. The Machine controller automatically deletes the node object.
+.. Remove the BMH and `Machine` objects. The machine controller automatically deletes the node object.
 
 .. Provision a new machine by using the following sample configuration:
 +
@@ -295,7 +295,7 @@ $ oc annotate bmh <bmh_name> -n openshift-machine-api baremetalhost.metal3.io/de
 +
 [NOTE]
 ====
-Run the following command on the surviving control plane node, not the node being replaced.
+Run the following command on the survivor control plane node, not the node being replaced.
 ====
 +
 [source,terminal]

modules/installation-sample-install-config-two-node-fencing-ipi.adoc

@@ -4,6 +4,11 @@
 
 You can use the following `install-config.yaml` configuration as a template for deploying a two-node OpenShift cluster with fencing by using the installer-provisioned infrastructure method:
 
+[NOTE]
+====
+Do an etcd backup before proceeding to ensure that you can restore the cluster if any issues occur.
+====
+
 .Sample `install-config.yaml` configuration
 [source,yaml]
 ----
@@ -57,7 +62,7 @@ sshKey: '<ssh_public_key>'
 * `compute.replicas`: Set this field to `0` because a two-node fencing cluster does not include worker nodes.  
 * `controlPlane.replicas`: Set this field to `2` for a two-node fencing deployment.  
 * `fencing.credentials.hostname`: Provide the Baseboard Management Console (BMC) credentials for each control plane node. These credentials are required for node fencing and prevent split-brain scenarios. 
-* `fencing.credentials.certificateVerification`: Set this field to `Disabled` if your Redfish URL uses self-signed certificates, which is common for internally hosted endpoints. Set this field to `Enabled` for URLs with valid CA-signed certificates.
+* `fencing.credentials.certificateVerification`: Set this field to `Disabled` if your Redfish URL uses self-signed certificates, which is common for internally-hosted endpoints. Set this field to `Enabled` for URLs with valid CA-signed certificates.
 * `metadata.name`: The cluster name is used as a prefix for hostnames and DNS records.  
 * `featureSet`: Set this field to `TechPreviewNoUpgrade` to enable two-node OpenShift cluster deployments.  
 * `platform.baremetal.apiVIPs` and `platform.baremetal.ingressVIPs` : Virtual IPs for the API and Ingress endpoints. Ensure they are reachable by all nodes and external clients.  

modules/installation-sample-install-config-two-node-fencing-upi.adoc

@@ -4,6 +4,11 @@
 
 You can use the following `install-config.yaml` configuration as a template for deploying a two-node OpenShift cluster with fencing by using the user-provisioned infrastructure method:
 
+[NOTE]
+====
+Do an etcd backup before proceeding to ensure that you can restore the cluster if any issues occur.
+====
+
 .Sample `install-config.yaml` configuration
 [source,yaml]
 ----