||The base domain of the cluster. All DNS records must be sub-domains of this
base and include the cluster name.
controlPlane section is a single mapping, but the compute section is a
sequence of mappings. To meet the requirements of the different data structures,
the first line of the
compute section must begin with a hyphen,
-, and the
first line of the
controlPlane section must not. Both sections define a single machine pool, so only one control plane is used. OpenShift Container Platform does not support defining multiple compute pools.
||You must set the value of the
replicas parameter to
0. This parameter
controls the number of workers that the cluster creates and manages for you,
which are functions that the cluster does not perform when you
use user-provisioned infrastructure. You must manually deploy worker
machines for the cluster to use before you finish installing OpenShift Container Platform.
||The number of control plane machines that you add to the cluster. Because
the cluster uses this values as the number of etcd endpoints in the cluster, the
value must match the number of control plane machines that you deploy.
||The cluster name that you specified in your DNS records.
||Establishes the relationships between a region and zone. You define a failure domain by using vCenter objects, such as a
datastore object. A failure domain defines the vCenter location for OpenShift Container Platform cluster nodes.
||The vSphere datacenter.
||The path to the vSphere datastore that holds virtual machine files, templates, and ISO images.
You can specify the path of any datastore that exists in a datastore cluster. By default, Storage vMotion is automatically enabled for a datastore cluster. Red Hat does not support Storage vMotion, so you must disable Storage vMotion to avoid data loss issues for your OpenShift Container Platform cluster.
If you must specify VMs across multiple datastores, use a
datastore object to specify a failure domain in your cluster’s
install-config.yaml configuration file. For more information, see "VMware vSphere region and zone enablement".
||Optional: For installer-provisioned infrastructure, the absolute path of an existing resource pool where the installation program creates the virtual machines, for example,
/<datacenter_name>/host/<cluster_name>/Resources/<resource_pool_name>/<optional_nested_resource_pool_name>. If you do not specify a value, resources are installed in the root of the cluster
||Optional: For installer-provisioned infrastructure, the absolute path of an existing folder where the installation program creates the virtual machines, for example,
/<datacenter_name>/vm/<folder_name>/<subfolder_name>. If you do not provide this value, the installation program creates a top-level folder in the datacenter virtual machine folder that is named with the infrastructure ID. If you are providing the infrastructure for the cluster and you do not want to use the default
StorageClass object, named
thin, you can omit the
folder parameter from the
||The password associated with the vSphere user.
||The fully-qualified hostname or IP address of the vCenter server.
The Cluster Cloud Controller Manager Operator performs a connectivity check on a provided hostname or IP address. Ensure that you specify a hostname or an IP address to a reachable vCenter server. If you provide metadata to a non-existent vCenter server, installation of the cluster fails at the bootstrap stage.
||The vSphere disk provisioning method.
||Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the Red Hat Enterprise Linux CoreOS (RHCOS) machines that OpenShift Container Platform runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with RHCOS instead.
To enable FIPS mode for your cluster, you must run the installation program from a Red Hat Enterprise Linux (RHEL) computer configured to operate in FIPS mode. For more information about configuring FIPS mode on RHEL, see Installing the system in FIPS mode. When running Red Hat Enterprise Linux (RHEL) or Red Hat Enterprise Linux CoreOS (RHCOS) booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64, ppc64le, and s390x architectures.
<local_registry>, specify the registry domain name, and optionally the
port, that your mirror registry uses to serve content. For example
specify the base64-encoded user name and password for your mirror registry.
||The public portion of the default SSH key for the
core user in
Red Hat Enterprise Linux CoreOS (RHCOS).
For production OpenShift Container Platform clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your
ssh-agent process uses.
||Provide the contents of the certificate file that you used for your mirror
imageContentSources section from the output of the command to
mirror the repository.