-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The documentation [1] shows a note where it is saying: """ Exactly three control plane nodes must be used for all production deployments. However, on bare metal platforms, clusters can be scaled up to five control plane nodes. """ This statement is incomplete as it doesn't include the Two Nodes Clusters. Additionally, it should be not advertised that cluster should be running as 5-node cluster. Better would be this. """ Exactly three control plane nodes must be used for all production deployments. However, on bare metal platforms, in certain cases the clusters can be scaled up to five control plane nodes (always confirm with Red Hat Support). There is an exception in Two Nodes Cluster with Arbiter or with Fencing, where the Control Plane services run on 2-node only <link-to-two-node-openshift>. """ [1] https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/architecture/control-plane#defining-masters_control-plane
Version-Release number of selected component (if applicable):
Openshift Container Platform 4.19
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: