mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
109 lines
5.1 KiB
Plaintext
109 lines
5.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_aws/installing-aws-user-infra.adoc [Eventually]
|
|
// * installing/installing_azure/installing-azure-user-infra.adoc [Eventually]
|
|
// * installing/installing_gcp/installing-gcp-user-infra.adoc [Eventually]
|
|
// * installing/installing_gcp/installing-restricted-networks-gcp.adoc [Eventually]
|
|
// * installing/installing_bare_metal/upi/installing-bare-metal.adoc
|
|
// * installing/installing_aws/installing-restricted-networks-aws.adoc [Eventually]
|
|
// * installing/installing_bare_metal/upi/installing-restricted-networks-bare-metal.adoc
|
|
// * installing/installing_platform_agnostic/installing-platform-agnostic.adoc
|
|
// * installing/installing_vsphere/installing-restricted-networks-vsphere.adoc [Eventually]
|
|
// * installing/installing_vsphere/installing-vsphere.adoc [Eventually]
|
|
// * installing/installing_ibm_z/installing-ibm-z.adoc
|
|
// * installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc
|
|
// * installing/installing_ibm_z/installing-ibm-z-kvm.adoc
|
|
// * installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc
|
|
// * installing/installing_ibm_z/installing-ibm-z-lpar.adoc
|
|
// * installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.adoc
|
|
|
|
ifeval::["{context}" == "installing-ibm-z"]
|
|
:ibm-z:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-ibm-z-kvm"]
|
|
:ibm-z-kvm:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-ibm-z-lpar"]
|
|
:ibm-z:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-restricted-networks-ibm-z"]
|
|
:ibm-z:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-restricted-networks-ibm-z-kvm"]
|
|
:ibm-z-kvm:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-restricted-networks-ibm-z"]
|
|
:ibm-z:
|
|
endif::[]
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="installation-three-node-cluster_{context}"]
|
|
= Configuring a three-node cluster
|
|
|
|
[role="_abstract"]
|
|
ifndef::ibm-z,ibm-z-kvm[]
|
|
To create smaller, resource-efficient clusters for testing and production, deploy a bare-metal cluster with zero compute machines. This optional configuration uses only three control plane machines, optimizing infrastructure resources for administrators and developers.
|
|
endif::ibm-z,ibm-z-kvm[]
|
|
ifdef::ibm-z,ibm-z-kvm[]
|
|
To create smaller, resource-efficient clusters for testing and production, deploy a bare-metal cluster with zero compute machines in a minimal three-node cluster. This optional configuration uses only three control plane machines, optimizing infrastructure resources for testing, development, and production purposes.
|
|
endif::ibm-z,ibm-z-kvm[]
|
|
|
|
In three-node {product-title} environments, the three control plane machines are schedulable, which means that your application workloads are scheduled to run on them.
|
|
|
|
.Prerequisites
|
|
|
|
* You have an existing `install-config.yaml` file.
|
|
|
|
.Procedure
|
|
|
|
* Ensure that the number of compute replicas is set to `0` in your `install-config.yaml` file, as shown in the following `compute` stanza:
|
|
+
|
|
[source,yaml]
|
|
----
|
|
compute:
|
|
- name: worker
|
|
platform: {}
|
|
replicas: 0
|
|
# ...
|
|
----
|
|
+
|
|
[NOTE]
|
|
====
|
|
You must set the value of the `replicas` parameter for the compute machines to `0` when you install {product-title} on user-provisioned infrastructure, regardless of the number of compute machines you are deploying. In installer-provisioned installations, the parameter controls the number of compute machines that the cluster creates and manages for you. This does not apply to user-provisioned installations, where the compute machines are deployed manually.
|
|
====
|
|
ifdef::ibm-z,ibm-z-kvm[]
|
|
+
|
|
[NOTE]
|
|
====
|
|
The preferred resource for control plane nodes is six vCPUs and 21 GB. For three control plane nodes this is the memory + vCPU equivalent of a minimum five-node cluster. You should back the three nodes, each installed on a 120 GB disk, with three IFLs that are SMT2 enabled. The minimum tested setup is three vCPUs and 10 GB on a 120 GB disk for each control plane node.
|
|
====
|
|
endif::ibm-z,ibm-z-kvm[]
|
|
.Next steps
|
|
|
|
For three-node cluster installations, follow these next steps:
|
|
|
|
* If you are deploying a three-node cluster with zero compute nodes, the Ingress Controller pods run on the control plane nodes. In three-node cluster deployments, you must configure your application ingress load balancer to route HTTP and HTTPS traffic to the control plane nodes. See the _Load balancing requirements for user-provisioned infrastructure_ section for more information.
|
|
|
|
* When you create the Kubernetes manifest files in the following procedure, ensure that the `mastersSchedulable` parameter in the `<installation_directory>/manifests/cluster-scheduler-02-config.yml` file is set to `true`. This enables your application workloads to run on the control plane nodes.
|
|
|
|
* Do not deploy any compute nodes when you create the {op-system-first} machines.
|
|
|
|
ifeval::["{context}" == "installing-ibm-z"]
|
|
:!ibm-z:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-ibm-z-kvm"]
|
|
:!ibm-z-kvm:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-ibm-z-lpar"]
|
|
:!ibm-z:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-restricted-networks-ibm-z"]
|
|
:!ibm-z:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-restricted-networks-ibm-z-kvm"]
|
|
:!ibm-z-kvm:
|
|
endif::[]
|
|
ifeval::["{context}" == "installing-restricted-networks-ibm-z-lpar"]
|
|
:!ibm-z:
|
|
endif::[]
|