Installation configuration parameters for Alibaba Cloud

Before you deploy an OKD cluster on Alibaba Cloud, 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.

Available installation configuration parameters for Alibaba Cloud

The following tables specify the required, optional, and Alibaba Cloud-specific installation configuration parameters that you can set as part of the installation process.

After installation, you cannot modify these parameters in the install-config.yaml file.

Required configuration parameters

Required installation configuration parameters are described in the following table:

Table 1. Required parameters
ParameterDescriptionValues
  1. apiVersion:

The API version for the install-config.yaml content. The current version is v1. The installation program may also support older API versions.

String

  1. baseDomain:

The base domain of your cloud provider. The base domain is used to create routes to your OKD cluster components. The full DNS name for your cluster is a combination of the baseDomain and metadata.name parameter values that uses the <metadata.name>.<baseDomain> format.

A fully-qualified domain or subdomain name, such as example.com.

  1. metadata:

Kubernetes resource ObjectMeta, from which only the name parameter is consumed.

Object

  1. metadata:
  2.   name:

The name of the cluster. DNS records for the cluster are all subdomains of {{.metadata.name}}.{{.baseDomain}}.

String of lowercase letters, hyphens (-), and periods (.), such as dev.

  1. platform:

The configuration for the specific platform upon which to perform the installation: alibabacloud, aws, baremetal, azure, gcp, ibmcloud, nutanix, openstack, powervs, vsphere, or {}. For additional information about platform.<platform> parameters, consult the table for your specific platform that follows.

Object

Network configuration parameters

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.

Only IPv4 addresses are supported.

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.

Table 2. Network parameters
ParameterDescriptionValues
  1. networking:

The configuration for the cluster network.

Object

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

  1. networking:
  2.   networkType:

The Red Hat OpenShift Networking network plugin to install.

Either OpenShiftSDN or OVNKubernetes. The default value is OVNKubernetes.

  1. networking:
  2.   clusterNetwork:

The IP address blocks for pods.

The default value is 10.128.0.0/14 with a host prefix of /23.

If you specify multiple IP address blocks, the blocks must not overlap.

An array of objects. For example:

  1. networking:
  2.   clusterNetwork:
  3.   - cidr: 10.128.0.0/14
  4.     hostPrefix: 23
  1. networking:
  2.   clusterNetwork:
  3.     cidr:

Required if you use networking.clusterNetwork. An IP address block.

An IPv4 network.

An IP address block in Classless Inter-Domain Routing (CIDR) notation. The prefix length for an IPv4 block is between 0 and 32.

  1. networking:
  2.   clusterNetwork:
  3.     hostPrefix:

The subnet prefix length to assign to each individual node. For example, if hostPrefix is set to 23 then each node is assigned a /23 subnet out of the given cidr. A hostPrefix value of 23 provides 510 (2^(32 - 23) - 2) pod IP addresses.

A subnet prefix.

The default value is 23.

  1. networking:
  2.   serviceNetwork:

The IP address block for services. The default value is 172.30.0.0/16.

The OpenShift SDN and OVN-Kubernetes network plugins support only a single IP address block for the service network.

An array with an IP address block in CIDR format. For example:

  1. networking:
  2.   serviceNetwork:
  3.    - 172.30.0.0/16
  1. networking:
  2.   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:

  1. networking:
  2.   machineNetwork:
  3.   - cidr: 10.0.0.0/16
  1. networking:
  2.   machineNetwork:
  3.     cidr:

Required if you use networking.machineNetwork. An IP address block. The default value is 10.0.0.0/16 for all platforms other than libvirt and IBM Power® Virtual Server. For libvirt, the default value is 192.168.126.0/24. For IBM Power® Virtual Server, the default value is 192.168.0.0/24.

An IP network block in CIDR notation.

For example, 10.0.0.0/16.

Set the networking.machineNetwork to match the CIDR that the preferred NIC resides in.

Optional configuration parameters

Optional installation configuration parameters are described in the following table:

Table 3. Optional parameters
ParameterDescriptionValues
  1. 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

  1. capabilities:

Controls the installation of optional core cluster components. You can reduce the footprint of your OKD cluster by disabling optional components. For more information, see the “Cluster capabilities” page in Installing.

String array

  1. capabilities:
  2.   baselineCapabilitySet:

Selects an initial set of optional capabilities to enable. Valid values are None, v4.11, v4.12 and vCurrent. The default value is vCurrent.

String

  1. capabilities:
  2.   additionalEnabledCapabilities:

Extends the set of optional capabilities beyond what you specify in baselineCapabilitySet. You may specify multiple capabilities in this parameter.

String array

  1. cpuPartitioningMode:

Enables workload partitioning, which isolates OKD 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.

None or AllNodes. None is the default value.

  1. compute:

The configuration for the machines that comprise the compute nodes.

Array of MachinePool objects.

  1. compute:
  2.   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 amd64 (the default).

String

  1. compute:
  2.   hyperthreading:

Whether to enable or disable simultaneous multithreading, or hyperthreading, on compute machines. By default, simultaneous multithreading is enabled to increase the performance of your machines’ cores.

If you disable simultaneous multithreading, ensure that your capacity planning accounts for the dramatically decreased machine performance.

Enabled or Disabled

  1. compute:
  2.   name:

Required if you use compute. The name of the machine pool.

worker

  1. compute:
  2.   platform:

Required if you use compute. Use this parameter to specify the cloud provider to host the worker machines. This parameter value must match the controlPlane.platform parameter value.

alibabacloud, aws, azure, gcp, ibmcloud, nutanix, openstack, powervs, vsphere, or {}

  1. compute:
  2.   replicas:

The number of compute machines, which are also known as worker machines, to provision.

A positive integer greater than or equal to 2. The default value is 3.

  1. featureSet:

Enables the cluster for a feature set. A feature set is a collection of OKD 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 TechPreviewNoUpgrade.

  1. controlPlane:

The configuration for the machines that comprise the control plane.

Array of MachinePool objects.

  1. controlPlane:
  2.   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 amd64.

String

  1. controlPlane:
  2.   hyperthreading:

Whether to enable or disable simultaneous multithreading, or hyperthreading, on control plane machines. By default, simultaneous multithreading is enabled to increase the performance of your machines’ cores.

If you disable simultaneous multithreading, ensure that your capacity planning accounts for the dramatically decreased machine performance.

Enabled or Disabled

  1. controlPlane:
  2.   name:

Required if you use controlPlane. The name of the machine pool.

master

  1. controlPlane:
  2.   platform:

Required if you use controlPlane. Use this parameter to specify the cloud provider that hosts the control plane machines. This parameter value must match the compute.platform parameter value.

alibabacloud, aws, azure, gcp, ibmcloud, nutanix, openstack, powervs, vsphere, or {}

  1. controlPlane:
  2.   replicas:

The number of control plane machines to provision.

Supported values are 3, or 1 when deploying single-node OpenShift.

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

Mint, Passthrough, Manual or an empty string (“”). [1]

  1. imageContentSources:

Sources and repositories for the release-image content.

Array of objects. Includes a source and, optionally, mirrors, as described in the following rows of this table.

  1. imageContentSources:
  2.   source:

Required if you use imageContentSources. Specify the repository that users refer to, for example, in image pull specifications.

String

  1. imageContentSources:
  2.   mirrors:

Specify one or more repositories that may also contain the same images.

Array of strings

  1. publish:

How to publish or expose the user-facing endpoints of your cluster, such as the Kubernetes API, OpenShift routes.

Internal or External. The default value is External.

Setting this field to Internal is not supported on non-cloud platforms.

If the value of the field is set to Internal, the cluster will become non-functional. For more information, refer to BZ#1953035.

  1. sshKey:

The SSH key to authenticate access to your cluster machines.

For production OKD clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your ssh-agent process uses.

For example, sshKey: ssh-ed25519 AAAA...

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

Additional Alibaba Cloud configuration parameters

Additional Alibaba Cloud configuration parameters are described in the following table. The alibabacloud parameters are the configuration used when installing on Alibaba Cloud. The defaultMachinePlatform parameters are the default configuration used when installing on Alibaba Cloud for machine pools that do not define their own platform configuration.

These parameters apply to both compute machines and control plane machines where specified.

If defined, the parameters compute.platform.alibabacloud and controlPlane.platform.alibabacloud will overwrite platform.alibabacloud.defaultMachinePlatform settings for compute machines and control plane machines respectively.

Table 4. Optional Alibaba Cloud parameters
ParameterDescriptionValues
  1. compute:
  2.   platform:
  3.     alibabacloud:
  4.       imageID:

The imageID used to create the ECS instance. ImageID must belong to the same region as the cluster.

String.

  1. compute:
  2.   platform:
  3.     alibabacloud:
  4.       instanceType:

InstanceType defines the ECS instance type. Example: ecs.g6.large

String.

  1. compute:
  2.   platform:
  3.     alibabacloud:
  4.       systemDiskCategory:

Defines the category of the system disk. Examples: cloud_efficiency,cloud_essd

String.

  1. compute:
  2.   platform:
  3.     alibabacloud:
  4.       systemDisksize:

Defines the size of the system disk in gibibytes (GiB).

Integer.

  1. compute:
  2.   platform:
  3.     alibabacloud:
  4.       zones:

The list of availability zones that can be used. Examples: cn-hangzhou-h, cn-hangzhou-j

String list.

  1. controlPlane:
  2.   platform:
  3.     alibabacloud:
  4.       imageID:

The imageID used to create the ECS instance. ImageID must belong to the same region as the cluster.

String.

  1. controlPlane:
  2.   platform:
  3.     alibabacloud:
  4.       instanceType:

InstanceType defines the ECS instance type. Example: ecs.g6.xlarge

String.

  1. controlPlane:
  2.   platform:
  3.     alibabacloud:
  4.       systemDiskCategory:

Defines the category of the system disk. Examples: cloud_efficiency,cloud_essd

String.

  1. controlPlane:
  2.   platform:
  3.     alibabacloud:
  4.       systemDisksize:

Defines the size of the system disk in gibibytes (GiB).

Integer.

  1. controlPlane:
  2.   platform:
  3.     alibabacloud:
  4.       zones:

The list of availability zones that can be used. Examples: cn-hangzhou-h, cn-hangzhou-j

String list.

  1. platform:
  2.   alibabacloud:
  3.     region:

Required. The Alibaba Cloud region where the cluster will be created.

String.

  1. platform:
  2.   alibabacloud:
  3.     resourceGroupID:

The ID of an already existing resource group where the cluster will be installed. If empty, the installation program will create a new resource group for the cluster.

String.

  1. platform:
  2.   alibabacloud:
  3.     tags:

Additional keys and values to apply to all Alibaba Cloud resources created for the cluster.

Object.

  1. platform:
  2.   alibabacloud:
  3.     vpcID:

The ID of an already existing VPC where the cluster should be installed. If empty, the installation program will create a new VPC for the cluster.

String.

  1. platform:
  2.   alibabacloud:
  3.     vswitchIDs:

The ID list of already existing VSwitches where cluster resources will be created. The existing VSwitches can only be used when also using existing VPC. If empty, the installation program will create new VSwitches for the cluster.

String list.

  1. platform:
  2.   alibabacloud:
  3.     defaultMachinePlatform:
  4.       imageID:

For both compute machines and control plane machines, the image ID that should be used to create ECS instance. If set, the image ID should belong to the same region as the cluster.

String.

  1. platform:
  2.   alibabacloud:
  3.     defaultMachinePlatform:
  4.       instanceType:

For both compute machines and control plane machines, the ECS instance type used to create the ECS instance. Example: ecs.g6.xlarge

String.

  1. platform:
  2.   alibabacloud:
  3.     defaultMachinePlatform:
  4.       systemDiskCategory:

For both compute machines and control plane machines, the category of the system disk. Examples: cloud_efficiency, cloud_essd.

String, for example “”, cloud_efficiency, cloud_essd.

  1. platform:
  2.   alibabacloud:
  3.     defaultMachinePlatform:
  4.       systemDiskSize:

For both compute machines and control plane machines, the size of the system disk in gibibytes (GiB). The minimum is 120.

Integer.

  1. platform:
  2.   alibabacloud:
  3.     defaultMachinePlatform:
  4.       zones:

For both compute machines and control plane machines, the list of availability zones that can be used. Examples: cn-hangzhou-h, cn-hangzhou-j

String list.

  1. platform:
  2.   alibabacloud:
  3.     privateZoneID:

The ID of an existing private zone into which to add DNS records for the cluster’s internal API. An existing private zone can only be used when also using existing VPC. The private zone must be associated with the VPC containing the subnets. Leave the private zone unset to have the installation program create the private zone on your behalf.

String.