Skip to content

Commit 575d82a

Browse files
committed
clarified single-az cluster minimum infra nodes
Author: Josephine Pfeiffer <[email protected]> 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
1 parent 4d54604 commit 575d82a

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

modules/rosa-policy-failure-points.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,9 @@ When accounting for possible node failures, it is also important to understand h
3535

3636
[id="rosa-policy-container-cluster-failure_{context}"]
3737
== Cluster failure
38-
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.
38+
Single-AZ ROSA clusters have at least three control plane and two infrastructure nodes in the same availability zone (AZ) in the private subnet.
39+
40+
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.
3941

4042
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.
4143

0 commit comments

Comments
 (0)