Installation configuration parameters for Azure
Before you deploy an OKD cluster on Microsoft Azure, 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 Azure
The following tables specify the required, optional, and Azure-specific installation configuration parameters that you can set as part of the installation process.
After installation, you cannot modify these parameters in the |
Required configuration parameters
Required installation configuration parameters are described in the following table:
Parameter | Description | Values |
---|---|---|
| The API version for the | String |
| 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 | A fully-qualified domain or subdomain name, such as |
| Kubernetes resource | Object |
| The name of the cluster. DNS records for the cluster are all subdomains of | String of lowercase letters, hyphens ( |
| The configuration for the specific platform upon which to perform the installation: | 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. |
Parameter | Description | Values | ||
---|---|---|---|---|
| The configuration for the cluster network. | Object
| ||
| The Red Hat OpenShift Networking network plugin to install. | Either | ||
| 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:
| ||
| 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 | ||
| The subnet prefix length to assign to each individual node. For example, if | A subnet prefix. The default value is | ||
| The IP address block for services. The default value is 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:
| ||
| The IP address blocks for machines. If you specify multiple IP address blocks, the blocks must not overlap. | An array of objects. For example:
| ||
| Required if you use | An IP network block in CIDR notation. For example,
|
Optional configuration parameters
Optional installation configuration parameters are described in the following table:
Parameter | Description | Values | ||
---|---|---|---|---|
| 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 | ||
| 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 | ||
| Selects an initial set of optional capabilities to enable. Valid values are | String | ||
| Extends the set of optional capabilities beyond what you specify in | String array | ||
| 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. |
| ||
| The configuration for the machines that comprise the compute nodes. | Array of | ||
| 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 | ||
| Whether to enable or disable simultaneous multithreading, or
|
| ||
| Required if you use |
| ||
| Required if you use |
| ||
| The number of compute machines, which are also known as worker machines, to provision. | A positive integer greater than or equal to | ||
| 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 | ||
| The configuration for the machines that comprise the control plane. | Array of | ||
| 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 | ||
| Whether to enable or disable simultaneous multithreading, or
|
| ||
| Required if you use |
| ||
| Required if you use |
| ||
| The number of control plane machines to provision. | Supported values are | ||
| 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. |
| ||
| Sources and repositories for the release-image content. | Array of objects. Includes a | ||
| Required if you use | String | ||
| Specify one or more repositories that may also contain the same images. | Array of strings | ||
| How to publish or expose the user-facing endpoints of your cluster, such as the Kubernetes API, OpenShift routes. |
| ||
| The SSH key to authenticate access to your cluster machines.
| For example, |
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.
Setting this parameter to
Manual
enables alternatives to storing administrator-level secrets in thekube-system
project, which require additional configuration steps. For more information, see “Alternatives to storing administrator-level secrets in the kube-system project”.
Additional Azure configuration parameters
Additional Azure configuration parameters are described in the following table.
By default, if you specify availability zones in the |
Parameter | Description | Values | ||
---|---|---|---|---|
| Enables host-level encryption for compute machines. You can enable this encryption alongside user-managed server-side encryption. This feature encrypts temporary, ephemeral, cached and un-managed disks on the VM host. This is not a prerequisite for user-managed server-side encryption. |
| ||
| The Azure disk size for the VM. | Integer that represents the size of the disk in GB. The default is | ||
| Defines the type of disk. |
| ||
| Enables the use of Azure ultra disks for persistent storage on compute nodes. This requires that your Azure region and zone have ultra disks available. |
| ||
| The name of the Azure resource group that contains the disk encryption set from the installation prerequisites. This resource group should be different from the resource group where you install the cluster to avoid deleting your Azure encryption key when the cluster is destroyed. This value is only necessary if you intend to install the cluster with user-managed disk encryption. | String, for example | ||
| The name of the disk encryption set that contains the encryption key from the installation prerequisites. | String, for example | ||
| Defines the Azure subscription of the disk encryption set where the disk encryption set resides. This secondary disk encryption set is used to encrypt compute machines. | String, in the format | ||
| Optional. By default, the installation program downloads and installs the Fedora CoreOS (FCOS) image that is used to boot compute machines. You can override the default behavior by using a custom FCOS image that is available from the Azure Marketplace. The installation program uses this image for compute machines only. | String. The name of the image publisher. | ||
| The name of Azure Marketplace offer that is associated with the custom FCOS image. If you use | String. The name of the image offer. | ||
| An instance of the Azure Marketplace offer. If you use | String. The SKU of the image offer. | ||
| The version number of the image SKU. If you use | String. The version of the image to use. | ||
| Enables accelerated networking. Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, improving its networking performance. If instance type of compute machines support |
| ||
| Defines the Azure instance type for compute machines. | String | ||
| The availability zones where the installation program creates compute machines. | String list | ||
| Enables confidential VMs or trusted launch for compute nodes. This option is not enabled by default. |
| ||
| Enables secure boot on compute nodes if you are using confidential VMs. |
| ||
| Enables the virtualized Trusted Platform Module (vTPM) feature on compute nodes if you are using confidential VMs. |
| ||
| Enables secure boot on compute nodes if you are using trusted launch. |
| ||
| Enables the vTPM feature on compute nodes if you are using trusted launch. |
| ||
| Enables the encryption of the virtual machine guest state for compute nodes. This parameter can only be used if you use Confidential VMs. |
| ||
| Enables confidential VMs or trusted launch for control plane nodes. This option is not enabled by default. |
| ||
| Enables secure boot on control plane nodes if you are using confidential VMs. |
| ||
| Enables the vTPM feature on control plane nodes if you are using confidential VMs. |
| ||
| Enables secure boot on control plane nodes if you are using trusted launch. |
| ||
| Enables the vTPM feature on control plane nodes if you are using trusted launch. |
| ||
| Enables the encryption of the virtual machine guest state for control plane nodes. This parameter can only be used if you use Confidential VMs. |
| ||
| Defines the Azure instance type for control plane machines. | String | ||
| The availability zones where the installation program creates control plane machines. | String list | ||
| Enables confidential VMs or trusted launch for all nodes. This option is not enabled by default. |
| ||
| Enables secure boot on all nodes if you are using confidential VMs. |
| ||
| Enables the virtualized Trusted Platform Module (vTPM) feature on all nodes if you are using confidential VMs. |
| ||
| Enables secure boot on all nodes if you are using trusted launch. |
| ||
| Enables the vTPM feature on all nodes if you are using trusted launch. |
| ||
| Enables the encryption of the virtual machine guest state for all nodes. This parameter can only be used if you use Confidential VMs. |
| ||
| Enables host-level encryption for compute machines. You can enable this encryption alongside user-managed server-side encryption. This feature encrypts temporary, ephemeral, cached, and un-managed disks on the VM host. This parameter is not a prerequisite for user-managed server-side encryption. |
| ||
| The name of the disk encryption set that contains the encryption key from the installation prerequisites. | String, for example, | ||
| The name of the Azure resource group that contains the disk encryption set from the installation prerequisites. To avoid deleting your Azure encryption key when the cluster is destroyed, this resource group must be different from the resource group where you install the cluster. This value is necessary only if you intend to install the cluster with user-managed disk encryption. | String, for example, | ||
| Defines the Azure subscription of the disk encryption set where the disk encryption set resides. This secondary disk encryption set is used to encrypt compute machines. | String, in the format | ||
| The Azure disk size for the VM. | Integer that represents the size of the disk in GB. The default is | ||
| Defines the type of disk. |
| ||
| Optional. By default, the installation program downloads and installs the Fedora CoreOS (FCOS) image that is used to boot control plane and compute machines. You can override the default behavior by using a custom FCOS image that is available from the Azure Marketplace. The installation program uses this image for both types of machines. | String. The name of the image publisher. | ||
| The name of Azure Marketplace offer that is associated with the custom FCOS image. If you use | String. The name of the image offer. | ||
| An instance of the Azure Marketplace offer. If you use | String. The SKU of the image offer. | ||
| The version number of the image SKU. If you use | String. The version of the image to use. | ||
| The Azure instance type for control plane and compute machines. | The Azure instance type. | ||
| The availability zones where the installation program creates compute and control plane machines. | String list. | ||
| Enables host-level encryption for control plane machines. You can enable this encryption alongside user-managed server-side encryption. This feature encrypts temporary, ephemeral, cached and un-managed disks on the VM host. This is not a prerequisite for user-managed server-side encryption. |
| ||
| The name of the Azure resource group that contains the disk encryption set from the installation prerequisites. This resource group should be different from the resource group where you install the cluster to avoid deleting your Azure encryption key when the cluster is destroyed. This value is only necessary if you intend to install the cluster with user-managed disk encryption. | String, for example | ||
| The name of the disk encryption set that contains the encryption key from the installation prerequisites. | String, for example | ||
| Defines the Azure subscription of the disk encryption set where the disk encryption set resides. This secondary disk encryption set is used to encrypt control plane machines. | String, in the format | ||
| The Azure disk size for the VM. | Integer that represents the size of the disk in GB. The default is | ||
| Defines the type of disk. |
| ||
| Optional. By default, the installation program downloads and installs the Fedora CoreOS (FCOS) image that is used to boot control plane machines. You can override the default behavior by using a custom FCOS image that is available from the Azure Marketplace. The installation program uses this image for control plane machines only. | String. The name of the image publisher. | ||
| The name of Azure Marketplace offer that is associated with the custom FCOS image. If you use | String. The name of the image offer. | ||
| An instance of the Azure Marketplace offer. If you use | String. The SKU of the image offer. | ||
| The version number of the image SKU. If you use | String. The version of the image to use. | ||
| Enables the use of Azure ultra disks for persistent storage on control plane machines. This requires that your Azure region and zone have ultra disks available. |
| ||
| Enables accelerated networking. Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, improving its networking performance. If instance type of control plane machines support |
| ||
| The name of the resource group that contains the DNS zone for your base domain. | String, for example | ||
| The name of an already existing resource group to install your cluster to. This resource group must be empty and only used for this specific cluster; the cluster components assume ownership of all resources in the resource group. If you limit the service principal scope of the installation program to this resource group, you must ensure all other resources used by the installation program in your environment have the necessary permissions, such as the public DNS zone and virtual network. Destroying the cluster by using the installation program deletes this resource group. | String, for example | ||
| The outbound routing strategy used to connect your cluster to the internet. If you are using user-defined routing, you must have pre-existing networking available where the outbound routing has already been configured prior to installing a cluster. The installation program is not responsible for configuring user-defined routing. If you specify the
|
| ||
| The name of the Azure region that hosts your cluster. | Any valid region name, such as | ||
| List of availability zones to place machines in. For high availability, specify at least two zones. | List of zones, for example | ||
| Enables the use of Azure ultra disks for persistent storage on control plane and compute machines. This requires that your Azure region and zone have ultra disks available. |
| ||
| The name of the resource group that contains the existing VNet that you want to deploy your cluster to. This name cannot be the same as the | String. | ||
| The name of the existing VNet that you want to deploy your cluster to. | String. | ||
| The name of the existing subnet in your VNet that you want to deploy your control plane machines to. | Valid CIDR, for example | ||
| The name of the existing subnet in your VNet that you want to deploy your compute machines to. | Valid CIDR, for example | ||
| The name of the Azure cloud environment that is used to configure the Azure SDK with the appropriate Azure API endpoints. If empty, the default value | Any valid cloud environment, such as | ||
| Enables accelerated networking. Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, improving its networking performance. |
|
You cannot customize Azure Availability Zones or Use tags to organize your Azure resources with an Azure cluster. |