String
Before you deploy an OpenShift Container Platform cluster on vSphere, you provide parameters to customize your cluster and the platform that hosts it. When you create the install-config.yaml
file, you provide values for the required parameters through the command line. You can then modify the install-config.yaml
file to customize your cluster further.
The following tables specify the required, optional, and vSphere-specific installation configuration parameters that you can set as part of the installation process.
After installation, you cannot modify these parameters in the |
Required installation configuration parameters are described in the following table:
Parameter | Description | Values |
---|---|---|
apiVersion: |
The API version for the |
String |
baseDomain: |
The base domain of your cloud provider. The base domain is used to create routes to your OpenShift Container Platform cluster components. The full DNS name for your cluster is a combination of the |
A fully-qualified domain or subdomain name, such as |
metadata: |
Kubernetes resource |
Object |
metadata: name: |
The name of the cluster. DNS records for the cluster are all subdomains of |
String of lowercase letters and hyphens ( |
platform: |
The configuration for the specific platform upon which to perform the installation: |
Object |
pullSecret: |
Get a pull secret from Red Hat OpenShift Cluster Manager to authenticate downloading container images for OpenShift Container Platform components from services such as Quay.io. |
|
You can customize your installation configuration based on the requirements of your existing network infrastructure. For example, you can expand the IP address block for the cluster network or provide different IP address blocks than the defaults.
Consider the following information before you configure network parameters for your cluster:
If you use the Red Hat OpenShift Networking OVN-Kubernetes network plugin, both IPv4 and IPv6 address families are supported.
If you deployed nodes in an OpenShift Container Platform cluster with a network that supports both IPv4 and non-link-local IPv6 addresses, configure your cluster to use a dual-stack network.
For clusters configured for dual-stack networking, both IPv4 and IPv6 traffic must use the same network interface as the default gateway. This ensures that in a multiple network interface controller (NIC) environment, a cluster can detect what NIC to use based on the available network interface. For more information, see "OVN-Kubernetes IPv6 and dual-stack limitations" in About the OVN-Kubernetes network plugin.
To prevent network connectivity issues, do not install a single-stack IPv4 cluster on a host that supports dual-stack networking.
On VMware vSphere, dual-stack networking can specify either IPv4 or IPv6 as the primary address family. |
If you configure your cluster to use both IP address families, review the following requirements:
Both IP families must use the same network interface for the default gateway.
Both IP families must have the default gateway.
You must specify IPv4 and IPv6 addresses in the same order for all network configuration parameters. For example, in the following configuration IPv4 addresses are listed before IPv6 addresses.
networking:
clusterNetwork:
- cidr: 10.128.0.0/14
hostPrefix: 23
- cidr: fd00:10:128::/56
hostPrefix: 64
serviceNetwork:
- 172.30.0.0/16
- fd00:172:16::/112
Globalnet is not supported with Red Hat OpenShift Data Foundation disaster recovery solutions. For regional disaster recovery scenarios, ensure that you use a nonoverlapping range of private IP addresses for the cluster and service networks in each cluster. |
Parameter | Description | Values | ||
---|---|---|---|---|
networking: |
The configuration for the cluster network. |
Object
|
||
networking: networkType: |
The Red Hat OpenShift Networking network plugin to install. |
|
||
networking: clusterNetwork: |
The IP address blocks for pods. The default value is If you specify multiple IP address blocks, the blocks must not overlap. |
An array of objects. For example:
|
||
networking: clusterNetwork: cidr: |
Required if you use An IPv4 network. |
An IP address block in Classless Inter-Domain Routing (CIDR) notation.
The prefix length for an IPv4 block is between |
||
networking: clusterNetwork: hostPrefix: |
The subnet prefix length to assign to each individual node. For example, if |
A subnet prefix. The default value is |
||
networking: serviceNetwork: |
The IP address block for services. The default value is The OVN-Kubernetes network plugins supports only a single IP address block for the service network. |
An array with an IP address block in CIDR format. For example:
|
||
networking: machineNetwork: |
The IP address blocks for machines. If you specify multiple IP address blocks, the blocks must not overlap. |
An array of objects. For example:
|
||
networking: machineNetwork: cidr: |
Required if you use |
An IP network block in CIDR notation. For example,
|
Optional installation configuration parameters are described in the following table:
Parameter | Description | Values | ||||
---|---|---|---|---|---|---|
additionalTrustBundle: |
A PEM-encoded X.509 certificate bundle that is added to the nodes' trusted certificate store. This trust bundle may also be used when a proxy has been configured. |
String |
||||
capabilities: |
Controls the installation of optional core cluster components. You can reduce the footprint of your OpenShift Container Platform cluster by disabling optional components. For more information, see the "Cluster capabilities" page in Installing. |
String array |
||||
capabilities: baselineCapabilitySet: |
Selects an initial set of optional capabilities to enable. Valid values are |
String |
||||
capabilities: additionalEnabledCapabilities: |
Extends the set of optional capabilities beyond what you specify in |
String array |
||||
cpuPartitioningMode: |
Enables workload partitioning, which isolates OpenShift Container Platform services, cluster management workloads, and infrastructure pods to run on a reserved set of CPUs. Workload partitioning can only be enabled during installation and cannot be disabled after installation. While this field enables workload partitioning, it does not configure workloads to use specific CPUs. For more information, see the Workload partitioning page in the Scalability and Performance section. |
|
||||
compute: |
The configuration for the machines that comprise the compute nodes. |
Array of |
||||
compute: architecture: |
Determines the instruction set architecture of the machines in the pool. Currently, clusters with varied architectures are not supported. All pools must specify the same architecture. Valid values are |
String |
||||
compute: name: |
Required if you use |
|
||||
compute: platform: |
Required if you use |
|
||||
compute: replicas: |
The number of compute machines, which are also known as worker machines, to provision. |
A positive integer greater than or equal to |
||||
featureSet: |
Enables the cluster for a feature set. A feature set is a collection of OpenShift Container Platform features that are not enabled by default. For more information about enabling a feature set during installation, see "Enabling features using feature gates". |
String. The name of the feature set to enable, such as |
||||
controlPlane: |
The configuration for the machines that comprise the control plane. |
Array of |
||||
controlPlane: architecture: |
Determines the instruction set architecture of the machines in the pool. Currently, clusters with varied architectures are not supported. All pools must specify the same architecture. Valid values are |
String |
||||
controlPlane: name: |
Required if you use |
|
||||
controlPlane: platform: |
Required if you use |
|
||||
controlPlane: replicas: |
The number of control plane machines to provision. |
Supported values are |
||||
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.
|
|
||||
fips: |
Enable or disable FIPS mode. The default is
|
|
||||
imageContentSources: |
Sources and repositories for the release-image content. |
Array of objects. Includes a |
||||
imageContentSources: source: |
Required if you use |
String |
||||
imageContentSources: mirrors: |
Specify one or more repositories that may also contain the same images. |
Array of strings |
||||
publish: |
How to publish or expose the user-facing endpoints of your cluster, such as the Kubernetes API, OpenShift routes. |
Setting this field to
|
||||
sshKey: |
The SSH key to authenticate access to your cluster machines.
|
For example, |
Additional VMware vSphere configuration parameters are described in the following table:
Parameter | Description | Values | ||
---|---|---|---|---|
platform: vsphere: |
Describes your account on the cloud platform that hosts your cluster. You can use the parameter to customize the platform. If you provide additional configuration settings for compute and control plane machines in the machine pool, the parameter is not required. You can only specify one vCenter server for your OpenShift Container Platform cluster. |
A dictionary of vSphere configuration objects |
||
platform: vsphere: apiVIPs: |
Virtual IP (VIP) addresses that you configured for control plane API access.
|
Multiple IP addresses |
||
platform: vsphere: diskType: |
Optional: The disk provisioning method. This value defaults to the vSphere default storage policy if not set. |
Valid values are |
||
platform: vsphere: failureDomains: |
Establishes the relationships between a region and zone. You define a failure domain by using vCenter objects, such as a |
An array of failure domain configuration objects. |
||
platform: vsphere: failureDomains: name: |
The name of the failure domain. |
String |
||
platform: vsphere: failureDomains: region: |
If you define multiple failure domains for your cluster, you must attach the tag to each vCenter data center. To define a region, use a tag from the |
String |
||
platform: vsphere: failureDomains: server: |
Specifies the fully-qualified hostname or IP address of the VMware vCenter server, so that a client can access failure domain resources. You must apply the |
String |
||
platform: vsphere: failureDomains: zone: |
If you define multiple failure domains for your cluster, you must attach a tag to each vCenter cluster. To define a zone, use a tag from the |
String |
||
platform: vsphere: failureDomains: topology: computeCluster: |
The path to the vSphere compute cluster. |
String |
||
platform: vsphere: failureDomains: topology: datacenter: |
Lists and defines the data centers where OpenShift Container Platform virtual machines (VMs) operate.
The list of data centers must match the list of data centers specified in the |
String |
||
platform: vsphere: failureDomains: topology: datastore: |
Specifies the path to a vSphere datastore that stores virtual machines files for a failure domain. You must apply the |
String |
||
platform: vsphere: failureDomains: topology: folder: |
Optional: The absolute path of an existing folder where the user creates the virtual machines, for example, |
String |
||
platform: vsphere: failureDomains: topology: networks: |
Lists any network in the vCenter instance that contains the virtual IP addresses and DNS records that you configured. |
String |
||
platform: vsphere: failureDomains: topology: resourcePool: |
Optional: The absolute path of an existing resource pool where the installation program creates the virtual machines, for example, |
String |
||
platform: vsphere: failureDomains: topology template: |
Specifies the absolute path to a pre-existing Red Hat Enterprise Linux CoreOS (RHCOS) image template or virtual machine. The installation program can use the image template or virtual machine to quickly install RHCOS on vSphere hosts. Consider using this parameter as an alternative to uploading an RHCOS image on vSphere hosts. This parameter is available for use only on installer-provisioned infrastructure. |
String |
||
platform: vsphere: ingressVIPs: |
Virtual IP (VIP) addresses that you configured for cluster Ingress.
|
Multiple IP addresses |
||
platform: vsphere: vcenters: |
Configures the connection details so that services can communicate with a vCenter server. Currently, only a single vCenter server is supported. |
An array of vCenter configuration objects. |
||
platform: vsphere: vcenters: datacenters: |
Lists and defines the data centers where OpenShift Container Platform virtual machines (VMs) operate. The list of data centers must match the list of data centers specified in the |
String |
||
platform: vsphere: vcenters: password: |
The password associated with the vSphere user. |
String |
||
platform: vsphere: vcenters: port: |
The port number used to communicate with the vCenter server. |
Integer |
||
platform: vsphere: vcenters: server: |
The fully qualified host name (FQHN) or IP address of the vCenter server. |
String |
||
platform: vsphere: vcenters: user: |
The username associated with the vSphere user. |
String |
In OpenShift Container Platform 4.13, the following vSphere configuration parameters are deprecated. You can continue to use these parameters, but the installation program does not automatically specify these parameters in the install-config.yaml
file.
The following table lists each deprecated vSphere configuration parameter:
Parameter | Description | Values | ||
---|---|---|---|---|
platform: vsphere: apiVIP: |
The virtual IP (VIP) address that you configured for control plane API access.
|
An IP address, for example |
||
platform: vsphere: cluster: |
The vCenter cluster to install the OpenShift Container Platform cluster in. |
String |
||
platform: vsphere: datacenter: |
Defines the data center where OpenShift Container Platform virtual machines (VMs) operate. |
String |
||
platform: vsphere: defaultDatastore: |
The name of the default datastore to use for provisioning volumes. |
String |
||
platform: vsphere: folder: |
Optional: The absolute path of an existing folder where the installation program creates the virtual machines. If you do not provide this value, the installation program creates a folder that is named with the infrastructure ID in the data center virtual machine folder. |
String, for example, |
||
platform: vsphere: ingressVIP: |
Virtual IP (VIP) addresses that you configured for cluster Ingress.
|
An IP address, for example |
||
platform: vsphere: network: |
The network in the vCenter instance that contains the virtual IP addresses and DNS records that you configured. |
String |
||
platform: vsphere: password: |
The password for the vCenter user name. |
String |
||
platform: vsphere: resourcePool: |
Optional: The absolute path of an existing resource pool where the installation program creates the virtual machines. If you do not specify a value, the installation program installs the resources in the root of the cluster under |
String, for example, |
||
platform: vsphere: username: |
The user name to use to connect to the vCenter instance with. This user must have at least the roles and privileges that are required for static or dynamic persistent volume provisioning in vSphere. |
String |
||
platform: vsphere: vCenter: |
The fully-qualified hostname or IP address of a vCenter server. |
String |
Optional VMware vSphere machine pool configuration parameters are described in the following table:
Parameter | Description | Values |
---|---|---|
platform: vsphere: clusterOSImage: |
The location from which the installation program downloads the Red Hat Enterprise Linux CoreOS (RHCOS) image. Before setting a path value for this parameter, ensure that the default RHCOS boot image in the OpenShift Container Platform release matches the RHCOS image template or virtual machine version; otherwise, cluster installation might fail. |
An HTTP or HTTPS URL, optionally with a SHA-256 checksum. For example, |
platform: vsphere: osDisk: diskSizeGB: |
The size of the disk in gigabytes. |
Integer |
platform: vsphere: cpus: |
The total number of virtual processor cores to assign a virtual machine. The value of |
Integer |
platform: vsphere: coresPerSocket: |
The number of cores per socket in a virtual machine. The number of virtual sockets on the virtual machine is |
Integer |
platform: vsphere: memoryMB: |
The size of a virtual machine’s memory in megabytes. |
Integer |