openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS#12987: Two-node OpenShift cluster with fencing Follow Up

Browse Source
This commit is contained in:
Michael Burke
2025-10-17 15:48:05 -04:00
committed by openshift-cherrypick-robot
parent 653782dfdb
commit 8ef3d29b53
4 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
installing/installing_two_node_cluster/installing_tnf/install-post-tnf.adoc
View File

@@ -6,11 +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]
Use the following sections help you with recovering from issues in a two-node OpenShift cluster with fencing.
// Manually recovering from a disruption event when automated recovery is unavailable
include::modules/installation-manual-recovering-when-auto-recovery-is-unavail.adoc[leveloffset=+1]
@@ -30,4 +30,4 @@ include::modules/installation-replacing-control-plane-nodes.adoc[leveloffset=+1]
* xref:../../../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backup-etcd-restoring_backing-up-etcd[Restoring etcd from a backup].
// Verifying etcd health in a two-node OpenShift cluster with fencing
include::modules/installation-verifying-etcd-health.adoc[leveloffset=+1]
include::modules/installation-verifying-etcd-health.adoc[leveloffset=+1]

4
installing/installing_two_node_cluster/installing_tnf/install-tnf.adoc
View File

@@ -6,11 +6,11 @@ include::_attributes/common-attributes.adoc[]
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.
:FeatureName: Two-node OpenShift cluster with fencing
include::snippets/technology-preview.adoc[leveloffset=+1]
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.
// 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]

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

@@ -158,4 +158,4 @@ If manual recovery is still required and it fails, collect a must-gather and SOS
.Verification
For information about verifying that both control plane nodes and etcd are operating correctly, see "Verifying etcd health in a two-node OpenShift cluster with fencing".
For information about verifying that both control plane nodes and etcd are operating correctly, see "Verifying etcd health in a two-node OpenShift cluster with fencing".

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

@@ -67,4 +67,4 @@ sshKey: '<ssh_public_key>'
* `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.
* `pullSecret`: Contains credentials required to pull container images for the cluster components.
* `sshKey`: The SSH public key for accessing cluster nodes after installation.
* `sshKey`: The SSH public key for accessing cluster nodes after installation.