Installation configuration parameters for vSphere¶

{
   "auths":{
      "cloud.openshift.com":{
         "auth":"b3Blb=",
         "email":"you@example.com"
      },
      "quay.io":{
         "auth":"b3Blb=",
         "email":"you@example.com"
      }
   }
}

Note

You cannot change parameters specified by the networking object after installation.

networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  - cidr: fd01::/48
    hostPrefix: 64

networking:
  serviceNetwork:
   - 172.30.0.0/16
networking:
  serviceNetwork:
   - 172.30.0.0/16
   - fd02::/112

networking:
  machineNetwork:
  - cidr: 10.0.0.0/16

Note

Set the networking.machineNetwork to match the CIDR of the preferred NIC.

If you are installing a cluster on AWS with dual-stack networking, consider the following distinction:

• If the installation program creates the VPC, do not specify an IPv6 entry in networking.machineNetwork. The installation program will assign an IPv6 address to the VPC.
• If you provide existing dual-stack subnets using the platform.aws.vpc.subnets parameter, you must specify IPv6 entries corresponding to either the VPC CIDR or the CIDR of the subnets.
• In both cases, you must provide an IPv4 CIDR entry.

Note

Not all CCO modes are supported for all cloud providers. For more information about CCO modes, see the "Managing cloud provider credentials" entry in the Authentication and authorization content.

Important

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 Switching RHEL to 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.

Important

If you are using Azure File storage, you cannot enable FIPS mode.

Important

When clusterUseOnly is false, its default setting, you must run the installation program from a bastion host that is within the same VPC where you want to deploy the cluster.

Note

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.

Note

This parameter applies only to installer-provisioned infrastructure without an external load balancer configured. You must not specify this parameter in user-provisioned infrastructure.

The apiVIP and ingressVIP parameters must come from the same network segment as the networking.machineNetwork parameter. If the networking.machineNetwork parameter is set to 10.0.0.0/16 then the API and Ingress VIPs must be in one of the 10.0.0.0/16 machine networks.

Important

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".

Note

This parameter applies only to installer-provisioned infrastructure without an external load balancer configured. You must not specify this parameter in user-provisioned infrastructure.

The apiVIP and ingressVIP parameters must come from the same network segment as the networking.machineNetwork parameter. If the networking.machineNetwork parameter is set to 10.0.0.0/16 then the API and Ingress VIPs must be in one of the 10.0.0.0/16 machine networks.

Note

In OpenShift Container Platform 4.12 and later, the apiVIP configuration setting is deprecated. Instead, use a List format to enter a value in the apiVIPs configuration setting.

Note

In OpenShift Container Platform 4.12 and later, the ingressVIP configuration setting is deprecated. Instead, use a List format to enter a value in the ingressVIPs configuration setting.

Important

Installing OpenShift Container Platform on VMware vSphere using multiple data disks is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.