Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 13. Installing a three-node cluster on Azure
In OpenShift Container Platform version 4.14, you can install a three-node cluster on Microsoft Azure. A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production.
You can install a three-node cluster using either installer-provisioned or user-provisioned infrastructure.
Deploying a three-node cluster using an Azure Marketplace image is not supported.
13.1. Configuring a three-node cluster Link kopierenLink in die Zwischenablage kopiert!
You configure a three-node cluster by setting the number of worker nodes to
0
install-config.yaml
0
Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes.
Prerequisites
-
You have an existing file.
install-config.yaml
Procedure
Set the number of compute replicas to
in your0file, as shown in the followinginstall-config.yamlstanza:computeExample
install-config.yamlfile for a three-node clusterapiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ...If you are deploying a cluster with user-provisioned infrastructure:
-
After you create the Kubernetes manifest files, make sure that the parameter is set to
spec.mastersSchedulableintruefile. You can locate this file incluster-scheduler-02-config.yml. For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on Azure using ARM templates".<installation_directory>/manifests - Do not create additional worker nodes.
-
After you create the Kubernetes manifest files, make sure that the
Example cluster-scheduler-02-config.yml file for a three-node cluster
apiVersion: config.openshift.io/v1
kind: Scheduler
metadata:
creationTimestamp: null
name: cluster
spec:
mastersSchedulable: true
policy:
name: ""
status: {}