From ddace4ddfc25247b6d8ecc7bc9cd7bd92ff11083 Mon Sep 17 00:00:00 2001 From: Sebastian Kopacz Date: Thu, 5 Dec 2024 16:26:39 -0500 Subject: [PATCH] OSDOCS-12786: 4/5 node support for ABI --- modules/etcd-node-scaling.adoc | 4 +++- modules/installation-configuration-parameters.adoc | 5 +++++ modules/understanding-agent-install.adoc | 3 +-- 3 files changed, 9 insertions(+), 3 deletions(-) diff --git a/modules/etcd-node-scaling.adoc b/modules/etcd-node-scaling.adoc index 6be33192b8..13148b700c 100644 --- a/modules/etcd-node-scaling.adoc +++ b/modules/etcd-node-scaling.adoc @@ -6,7 +6,9 @@ [id="etcd-node-scaling_{context}"] = Node scaling for etcd -In general, clusters must have 3 control plane nodes. However, if your cluster is installed on a bare metal platform, you can scale a cluster up to 5 control plane nodes as a postinstallation task. For example, to scale from 3 to 4 control plane nodes after installation, you can add a host and install it as a control plane node. Then, the etcd Operator scales accordingly to account for the additional control plane node. +In general, clusters must have 3 control plane nodes. However, if your cluster is installed on a bare metal platform, it can have up to 5 control plane nodes. If an existing bare-metal cluster has fewer than 5 control plane nodes, you can scale the cluster up as a postinstallation task. + +For example, to scale from 3 to 4 control plane nodes after installation, you can add a host and install it as a control plane node. Then, the etcd Operator scales accordingly to account for the additional control plane node. Scaling a cluster to 4 or 5 control plane nodes is available only on bare metal platforms. diff --git a/modules/installation-configuration-parameters.adoc b/modules/installation-configuration-parameters.adoc index 1045343ad4..0324253227 100644 --- a/modules/installation-configuration-parameters.adoc +++ b/modules/installation-configuration-parameters.adoc @@ -629,7 +629,12 @@ endif::agent[] |controlPlane: replicas: |The number of control plane machines to provision. +ifndef::agent[] |Supported values are `3`, or `1` when deploying {sno}. +endif::agent[] +ifdef::agent[] +|Supported values are `3`, `4`, `5`, or `1` when deploying {sno}. +endif::agent[] |credentialsMode: |The Cloud Credential Operator (CCO) mode. If no mode is specified, the CCO dynamically tries to determine the capabilities of the provided credentials, with a preference for mint mode on the platforms where multiple modes are supported. diff --git a/modules/understanding-agent-install.adoc b/modules/understanding-agent-install.adoc index 93e68a15be..fe39119524 100644 --- a/modules/understanding-agent-install.adoc +++ b/modules/understanding-agent-install.adoc @@ -58,10 +58,9 @@ Recommended cluster resources for the following topologies: |Topology|Number of control plane nodes|Number of compute nodes|vCPU|Memory|Storage |Single-node cluster|1|0|8 vCPUs|16 GB of RAM| 120 GB |Compact cluster|3|0 or 1|8 vCPUs|16 GB of RAM|120 GB -|HA cluster|3|2 and above |8 vCPUs|16 GB of RAM|120 GB +|HA cluster|3 to 5|2 and above |8 vCPUs|16 GB of RAM|120 GB |==== - In the `install-config.yaml`, specify the platform on which to perform the installation. The following platforms are supported: * `baremetal`