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

clarified single-az cluster minimum infra nodes

Browse Source 
Author:    Josephine Pfeiffer <hi@josie.lol>
 Date:      Wed Feb 22 13:37:03 2023 +0100
 On branch rosa-az-nodes
 Changes to be committed:
	modified:   modules/rosa-policy-failure-points.adoc
This commit is contained in:
Josephine Pfeiffer
2023-02-22 13:37:03 +01:00
committed by openshift-cherrypick-robot
parent 6da38cacc5
commit a1b4df92fe
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
modules/rosa-policy-failure-points.adoc
View File

@@ -35,7 +35,9 @@ When accounting for possible node failures, it is also important to understand h
[id="rosa-policy-container-cluster-failure_{context}"]
== Cluster failure
ROSA clusters have at least three control plane nodes and three infrastructure nodes that are preconfigured for high availability, either in a single zone or across multiple zones, depending on the type of cluster you have selected. Control plane and infrastructure nodes have the same resiliency as worker nodes, with the added benefit of being managed completely by Red Hat.
Single-AZ ROSA clusters have at least three control plane and two infrastructure nodes in the same availability zone (AZ) in the private subnet.
Multi-AZ ROSA clusters have at least three control plane nodes and three infrastructure nodes that are preconfigured for high availability, either in a single zone or across multiple zones, depending on the type of cluster you have selected. Control plane and infrastructure nodes have the same resiliency as worker nodes, with the added benefit of being managed completely by Red Hat.
In the event of a complete control plane outage, the OpenShift APIs will not function, and existing worker node pods are unaffected. However, if there is also a pod or node outage at the same time, the control planes must recover before new pods or nodes can be added or scheduled.