mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
TELCODOCS-843: Remediation, Fencing, and Maintentance concept details added
[enterprise-4.12] TELCODOCS-843: Remediation, Fencing, and Maintentance concept details added
This commit is contained in:
committed by
Michael Burke
parent
3fd8331146
commit
6ab9dc4033
@@ -72,7 +72,7 @@ You can configure one of the following high-availability (HA) options for your c
|
||||
In {product-title} clusters installed using installer-provisioned infrastructure and with MachineHealthCheck properly configured, if a node fails the MachineHealthCheck and becomes unavailable to the cluster, it is recycled. What happens next with VMs that ran on the failed node depends on a series of conditions. See xref:../../virt/virtual_machines/virt-create-vms.adoc#virt-about-runstrategies-vms_virt-create-vms[About RunStrategies for virtual machines] for more detailed information about the potential outcomes and how RunStrategies affect those outcomes.
|
||||
====
|
||||
|
||||
* Automatic high availability for both IPI and non-IPI is available by using the xref:../../nodes/nodes/eco-node-health-check-operator.adoc#node-health-check-operator[Node Health Check Operator] on the {product-title} cluster to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses the Self Node Remediation Operator to remediate the unhealthy nodes.
|
||||
* Automatic high availability for both IPI and non-IPI is available by using the xref:../../nodes/nodes/ecosystems/eco-node-health-check-operator.adoc#node-health-check-operator[Node Health Check Operator] on the {product-title} cluster to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses the Self Node Remediation Operator to remediate the unhealthy nodes.
|
||||
+
|
||||
--
|
||||
ifdef::openshift-enterprise[]
|
||||
|
||||
Reference in New Issue
Block a user