Installing a cluster on Azure in a restricted network with user-provisioned infrastructure

In OKD, you can install a cluster on Microsoft Azure by using infrastructure that you provide.

Several Azure Resource Manager (ARM) templates are provided to assist in completing these steps or to help model your own.

The steps for performing a user-provisioned infrastructure installation are provided as an example only. Installing a cluster with infrastructure you provide requires knowledge of the cloud provider and the installation process of OKD. Several ARM templates are provided to assist in completing these steps or to help model your own. You are also free to create the required resources through other methods.

Prerequisites

About installations in restricted networks

In OKD 4.14, you can perform an installation that does not require an active connection to the internet to obtain software components. Restricted network installations can be completed using installer-provisioned infrastructure or user-provisioned infrastructure, depending on the cloud platform to which you are installing the cluster.

If you choose to perform a restricted network installation on a cloud platform, you still require access to its cloud APIs. Some cloud functions, like Amazon Web Service’s Route 53 DNS and IAM services, require internet access. Depending on your network, you might require less internet access for an installation on bare metal hardware, Nutanix, or on VMware vSphere.

To complete a restricted network installation, you must create a registry that mirrors the contents of the OpenShift image registry and contains the installation media. You can create this registry on a mirror host, which can access both the internet and your closed network, or by using other methods that meet your restrictions.

Because of the complexity of the configuration for user-provisioned installations, consider completing a standard user-provisioned infrastructure installation before you attempt a restricted network installation using user-provisioned infrastructure. Completing this test installation might make it easier to isolate and troubleshoot any issues that might arise during your installation in a restricted network.

Additional limits

Clusters in restricted networks have the following additional limitations and restrictions:

  • The ClusterVersion status includes an Unable to retrieve available updates error.

  • By default, you cannot use the contents of the Developer Catalog because you cannot access the required image stream tags.

Configuring your Azure project

Before you can install OKD, you must configure an Azure project to host it.

All Azure resources that are available through public endpoints are subject to resource name restrictions, and you cannot create resources that use certain terms. For a list of terms that Azure restricts, see Resolve reserved resource name errors in the Azure documentation.

Azure account limits

The OKD cluster uses a number of Microsoft Azure components, and the default Azure subscription and service limits, quotas, and constraints affect your ability to install OKD clusters.

Default limits vary by offer category types, such as Free Trial and Pay-As-You-Go, and by series, such as Dv2, F, and G. For example, the default for Enterprise Agreement subscriptions is 350 cores.

Check the limits for your subscription type and if necessary, increase quota limits for your account before you install a default cluster on Azure.

The following table summarizes the Azure components whose limits can impact your ability to install and run OKD clusters.

ComponentNumber of components required by defaultDefault Azure limitDescription

vCPU

44

20 per region

A default cluster requires 44 vCPUs, so you must increase the account limit.

By default, each cluster creates the following instances:

  • One bootstrap machine, which is removed after installation

  • Three control plane machines

  • Three compute machines

Because the bootstrap and control plane machines use Standard_D8s_v3 virtual machines, which use 8 vCPUs, and the compute machines use Standard_D4s_v3 virtual machines, which use 4 vCPUs, a default cluster requires 44 vCPUs. The bootstrap node VM, which uses 8 vCPUs, is used only during installation.

To deploy more worker nodes, enable autoscaling, deploy large workloads, or use a different instance type, you must further increase the vCPU limit for your account to ensure that your cluster can deploy the machines that you require.

OS Disk

7

Each cluster machine must have a minimum of 100 GB of storage and 300 IOPS. While these are the minimum supported values, faster storage is recommended for production clusters and clusters with intensive workloads. For more information about optimizing storage for performance, see the page titled “Optimizing storage” in the “Scalability and performance” section.

VNet

1

1000 per region

Each default cluster requires one Virtual Network (VNet), which contains two subnets.

Network interfaces

7

65,536 per region

Each default cluster requires seven network interfaces. If you create more machines or your deployed workloads create load balancers, your cluster uses more network interfaces.

Network security groups

2

5000

Each cluster creates network security groups for each subnet in the VNet. The default cluster creates network security groups for the control plane and for the compute node subnets:

controlplane

Allows the control plane machines to be reached on port 6443 from anywhere

node

Allows worker nodes to be reached from the internet on ports 80 and 443

Network load balancers

3

1000 per region

Each cluster creates the following load balancers:

default

Public IP address that load balances requests to ports 80 and 443 across worker machines

internal

Private IP address that load balances requests to ports 6443 and 22623 across control plane machines

external

Public IP address that load balances requests to port 6443 across control plane machines

If your applications create more Kubernetes LoadBalancer service objects, your cluster uses more load balancers.

Public IP addresses

3

Each of the two public load balancers uses a public IP address. The bootstrap machine also uses a public IP address so that you can SSH into the machine to troubleshoot issues during installation. The IP address for the bootstrap node is used only during installation.

Private IP addresses

7

The internal load balancer, each of the three control plane machines, and each of the three worker machines each use a private IP address.

Spot VM vCPUs (optional)

0

If you configure spot VMs, your cluster must have two spot VM vCPUs for every compute node.

20 per region

This is an optional component. To use spot VMs, you must increase the Azure default limit to at least twice the number of compute nodes in your cluster.

Using spot VMs for control plane nodes is not recommended.

Additional resources

Configuring a public DNS zone in Azure

To install OKD, the Microsoft Azure account you use must have a dedicated public hosted DNS zone in your account. This zone must be authoritative for the domain. This service provides cluster DNS resolution and name lookup for external connections to the cluster.

Procedure

  1. Identify your domain, or subdomain, and registrar. You can transfer an existing domain and registrar or obtain a new one through Azure or another source.

    For more information about purchasing domains through Azure, see Buy a custom domain name for Azure App Service in the Azure documentation.

  2. If you are using an existing domain and registrar, migrate its DNS to Azure. See Migrate an active DNS name to Azure App Service in the Azure documentation.

  3. Configure DNS for your domain. Follow the steps in the Tutorial: Host your domain in Azure DNS in the Azure documentation to create a public hosted zone for your domain or subdomain, extract the new authoritative name servers, and update the registrar records for the name servers that your domain uses.

    Use an appropriate root domain, such as openshiftcorp.com, or subdomain, such as clusters.openshiftcorp.com.

  4. If you use a subdomain, follow your company’s procedures to add its delegation records to the parent domain.

You can view Azure’s DNS solution by visiting this example for creating DNS zones.

Increasing Azure account limits

To increase an account limit, file a support request on the Azure portal.

You can increase only one type of quota per support request.

Procedure

  1. From the Azure portal, click Help + support in the lower left corner.

  2. Click New support request and then select the required values:

    1. From the Issue type list, select Service and subscription limits (quotas).

    2. From the Subscription list, select the subscription to modify.

    3. From the Quota type list, select the quota to increase. For example, select Compute-VM (cores-vCPUs) subscription limit increases to increase the number of vCPUs, which is required to install a cluster.

    4. Click Next: Solutions.

  3. On the Problem Details page, provide the required information for your quota increase:

    1. Click Provide details and provide the required details in the Quota details window.

    2. In the SUPPORT METHOD and CONTACT INFO sections, provide the issue severity and your contact details.

  4. Click Next: Review + create and then click Create.

Certificate signing requests management

Because your cluster has limited access to automatic machine management when you use infrastructure that you provision, you must provide a mechanism for approving cluster certificate signing requests (CSRs) after installation. The kube-controller-manager only approves the kubelet client CSRs. The machine-approver cannot guarantee the validity of a serving certificate that is requested by using kubelet credentials because it cannot confirm that the correct machine issued the request. You must determine and implement a method of verifying the validity of the kubelet serving certificate requests and approving them.

Required Azure roles

An OKD cluster requires an Azure identity to create and manage Azure resources. Before you create the identity, verify that your environment meets the following requirements:

  • The Azure account that you use to create the identity is assigned the User Access Administrator and Contributor roles. These roles are required when:

    • Creating a service principal or user-assigned managed identity.

    • Enabling a system-assigned managed identity on a virtual machine.

  • If you are going to use a service principal to complete the installation, verify that the Azure account that you use to create the identity is assigned the microsoft.directory/servicePrincipals/createAsOwner permission in Azure Active Directory.

To set roles on the Azure portal, see the Manage access to Azure resources using RBAC and the Azure portal in the Azure documentation.

Required Azure permissions for user-provisioned infrastructure

The installation program requires access to an Azure service principal or managed identity with the necessary permissions to deploy the cluster and to maintain its daily operation. These permissions must be granted to the Azure subscription that is associated with the identity.

The following options are available to you:

  • You can assign the identity the Contributor and User Access Administrator roles. Assigning these roles is the quickest way to grant all of the required permissions.

    For more information about assigning roles, see the Azure documentation for managing access to Azure resources using the Azure portal.

  • If your organization’s security policies require a more restrictive set of permissions, you can create a custom role with the necessary permissions.

The following permissions are required for creating an OKD cluster on Microsoft Azure.

Required permissions for creating authorization resources

  • Microsoft.Authorization/policies/audit/action

  • Microsoft.Authorization/policies/auditIfNotExists/action

  • Microsoft.Authorization/roleAssignments/read

  • Microsoft.Authorization/roleAssignments/write

Required permissions for creating compute resources

  • Microsoft.Compute/images/read

  • Microsoft.Compute/images/write

  • Microsoft.Compute/images/delete

  • Microsoft.Compute/availabilitySets/read

  • Microsoft.Compute/disks/beginGetAccess/action

  • Microsoft.Compute/disks/delete

  • Microsoft.Compute/disks/read

  • Microsoft.Compute/disks/write

  • Microsoft.Compute/galleries/images/read

  • Microsoft.Compute/galleries/images/versions/read

  • Microsoft.Compute/galleries/images/versions/write

  • Microsoft.Compute/galleries/images/write

  • Microsoft.Compute/galleries/read

  • Microsoft.Compute/galleries/write

  • Microsoft.Compute/snapshots/read

  • Microsoft.Compute/snapshots/write

  • Microsoft.Compute/snapshots/delete

  • Microsoft.Compute/virtualMachines/delete

  • Microsoft.Compute/virtualMachines/powerOff/action

  • Microsoft.Compute/virtualMachines/read

  • Microsoft.Compute/virtualMachines/write

  • Microsoft.Compute/virtualMachines/deallocate/action

Required permissions for creating identity management resources

  • Microsoft.ManagedIdentity/userAssignedIdentities/assign/action

  • Microsoft.ManagedIdentity/userAssignedIdentities/read

  • Microsoft.ManagedIdentity/userAssignedIdentities/write

Required permissions for creating network resources

  • Microsoft.Network/dnsZones/A/write

  • Microsoft.Network/dnsZones/CNAME/write

  • Microsoft.Network/dnszones/CNAME/read

  • Microsoft.Network/dnszones/read

  • Microsoft.Network/loadBalancers/backendAddressPools/join/action

  • Microsoft.Network/loadBalancers/backendAddressPools/read

  • Microsoft.Network/loadBalancers/backendAddressPools/write

  • Microsoft.Network/loadBalancers/read

  • Microsoft.Network/loadBalancers/write

  • Microsoft.Network/networkInterfaces/delete

  • Microsoft.Network/networkInterfaces/join/action

  • Microsoft.Network/networkInterfaces/read

  • Microsoft.Network/networkInterfaces/write

  • Microsoft.Network/networkSecurityGroups/join/action

  • Microsoft.Network/networkSecurityGroups/read

  • Microsoft.Network/networkSecurityGroups/securityRules/delete

  • Microsoft.Network/networkSecurityGroups/securityRules/read

  • Microsoft.Network/networkSecurityGroups/securityRules/write

  • Microsoft.Network/networkSecurityGroups/write

  • Microsoft.Network/privateDnsZones/A/read

  • Microsoft.Network/privateDnsZones/A/write

  • Microsoft.Network/privateDnsZones/A/delete

  • Microsoft.Network/privateDnsZones/SOA/read

  • Microsoft.Network/privateDnsZones/read

  • Microsoft.Network/privateDnsZones/virtualNetworkLinks/read

  • Microsoft.Network/privateDnsZones/virtualNetworkLinks/write

  • Microsoft.Network/privateDnsZones/write

  • Microsoft.Network/publicIPAddresses/delete

  • Microsoft.Network/publicIPAddresses/join/action

  • Microsoft.Network/publicIPAddresses/read

  • Microsoft.Network/publicIPAddresses/write

  • Microsoft.Network/virtualNetworks/join/action

  • Microsoft.Network/virtualNetworks/read

  • Microsoft.Network/virtualNetworks/subnets/join/action

  • Microsoft.Network/virtualNetworks/subnets/read

  • Microsoft.Network/virtualNetworks/subnets/write

  • Microsoft.Network/virtualNetworks/write

Required permissions for checking the health of resources

  • Microsoft.Resourcehealth/healthevent/Activated/action

  • Microsoft.Resourcehealth/healthevent/InProgress/action

  • Microsoft.Resourcehealth/healthevent/Pending/action

  • Microsoft.Resourcehealth/healthevent/Resolved/action

  • Microsoft.Resourcehealth/healthevent/Updated/action

Required permissions for creating a resource group

  • Microsoft.Resources/subscriptions/resourceGroups/read

  • Microsoft.Resources/subscriptions/resourcegroups/write

Required permissions for creating resource tags

  • Microsoft.Resources/tags/write

Required permissions for creating storage resources

  • Microsoft.Storage/storageAccounts/blobServices/read

  • Microsoft.Storage/storageAccounts/blobServices/containers/write

  • Microsoft.Storage/storageAccounts/fileServices/read

  • Microsoft.Storage/storageAccounts/fileServices/shares/read

  • Microsoft.Storage/storageAccounts/fileServices/shares/write

  • Microsoft.Storage/storageAccounts/fileServices/shares/delete

  • Microsoft.Storage/storageAccounts/listKeys/action

  • Microsoft.Storage/storageAccounts/read

  • Microsoft.Storage/storageAccounts/write

Required permissions for creating deployments

  • Microsoft.Resources/deployments/read

  • Microsoft.Resources/deployments/write

  • Microsoft.Resources/deployments/validate/action

  • Microsoft.Resources/deployments/operationstatuses/read

Optional permissions for creating compute resources

  • Microsoft.Compute/availabilitySets/write

Optional permissions for creating marketplace virtual machine resources

  • Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/read

  • Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/write

Optional permissions for enabling user-managed encryption

  • Microsoft.Compute/diskEncryptionSets/read

  • Microsoft.Compute/diskEncryptionSets/write

  • Microsoft.Compute/diskEncryptionSets/delete

  • Microsoft.KeyVault/vaults/read

  • Microsoft.KeyVault/vaults/write

  • Microsoft.KeyVault/vaults/delete

  • Microsoft.KeyVault/vaults/deploy/action

  • Microsoft.KeyVault/vaults/keys/read

  • Microsoft.KeyVault/vaults/keys/write

  • Microsoft.Features/providers/features/register/action

The following permissions are required for deleting an OKD cluster on Microsoft Azure.

Required permissions for deleting authorization resources

  • Microsoft.Authorization/roleAssignments/delete

Required permissions for deleting compute resources

  • Microsoft.Compute/disks/delete

  • Microsoft.Compute/galleries/delete

  • Microsoft.Compute/galleries/images/delete

  • Microsoft.Compute/galleries/images/versions/delete

  • Microsoft.Compute/virtualMachines/delete

  • Microsoft.Compute/images/delete

Required permissions for deleting identity management resources

  • Microsoft.ManagedIdentity/userAssignedIdentities/delete

Required permissions for deleting network resources

  • Microsoft.Network/dnszones/read

  • Microsoft.Network/dnsZones/A/read

  • Microsoft.Network/dnsZones/A/delete

  • Microsoft.Network/dnsZones/CNAME/read

  • Microsoft.Network/dnsZones/CNAME/delete

  • Microsoft.Network/loadBalancers/delete

  • Microsoft.Network/networkInterfaces/delete

  • Microsoft.Network/networkSecurityGroups/delete

  • Microsoft.Network/privateDnsZones/read

  • Microsoft.Network/privateDnsZones/A/read

  • Microsoft.Network/privateDnsZones/delete

  • Microsoft.Network/privateDnsZones/virtualNetworkLinks/delete

  • Microsoft.Network/publicIPAddresses/delete

  • Microsoft.Network/virtualNetworks/delete

Required permissions for checking the health of resources

  • Microsoft.Resourcehealth/healthevent/Activated/action

  • Microsoft.Resourcehealth/healthevent/Resolved/action

  • Microsoft.Resourcehealth/healthevent/Updated/action

Required permissions for deleting a resource group

  • Microsoft.Resources/subscriptions/resourcegroups/delete

Required permissions for deleting storage resources

  • Microsoft.Storage/storageAccounts/delete

  • Microsoft.Storage/storageAccounts/listKeys/action

To install OKD on Azure, you must scope the permissions related to resource group creation to your subscription. After the resource group is created, you can scope the rest of the permissions to the created resource group. If the public DNS zone is present in a different resource group, then the network DNS zone related permissions must always be applied to your subscription.

You can scope all the permissions to your subscription when deleting an OKD cluster.

Creating a service principal

Because OKD and its installation program create Microsoft Azure resources by using the Azure Resource Manager, you must create a service principal to represent it.

Prerequisites

  • Install or update the Azure CLI.

  • Your Azure account has the required roles for the subscription that you use.

  • If you want to use a custom role, you have created a custom role with the required permissions listed in the Required Azure permissions for user-provisioned infrastructure section.

Procedure

  1. Log in to the Azure CLI:

    1. $ az login

  2. If your Azure account uses subscriptions, ensure that you are using the right subscription:

    1. View the list of available accounts and record the tenantId value for the subscription you want to use for your cluster:

      1. $ az account list --refresh

      Example output

      1. [
      2.   {
      3.     "cloudName": "AzureCloud",
      4.     "id": "9bab1460-96d5-40b3-a78e-17b15e978a80",
      5.     "isDefault": true,
      6.     "name": "Subscription Name",
      7.     "state": "Enabled",
      8.     "tenantId": "6057c7e9-b3ae-489d-a54e-de3f6bf6a8ee",
      9.     "user": {
      10.       "name": "you@example.com",
      11.       "type": "user"
      12.     }
      13.   }
      14. ]

    2. View your active account details and confirm that the tenantId value matches the subscription you want to use:

      1. $ az account show

      Example output

      1. {
      2.   "environmentName": "AzureCloud",
      3.   "id": "9bab1460-96d5-40b3-a78e-17b15e978a80",
      4.   "isDefault": true,
      5.   "name": "Subscription Name",
      6.   "state": "Enabled",
      7.   "tenantId": "6057c7e9-b3ae-489d-a54e-de3f6bf6a8ee", (1)
      8.   "user": {
      9.     "name": "you@example.com",
      10.     "type": "user"
      11.   }
      12. }
      1Ensure that the value of the tenantId parameter is the correct subscription ID.

    3. If you are not using the right subscription, change the active subscription:

      1. $ az account set -s <subscription_id> (1)
      1Specify the subscription ID.

    4. Verify the subscription ID update:

      1. $ az account show

      Example output

      1. {
      2.   "environmentName": "AzureCloud",
      3.   "id": "33212d16-bdf6-45cb-b038-f6565b61edda",
      4.   "isDefault": true,
      5.   "name": "Subscription Name",
      6.   "state": "Enabled",
      7.   "tenantId": "8049c7e9-c3de-762d-a54e-dc3f6be6a7ee",
      8.   "user": {
      9.     "name": "you@example.com",
      10.     "type": "user"
      11.   }
      12. }

  3. Record the tenantId and id parameter values from the output. You need these values during the OKD installation.

  4. Create the service principal for your account:

    1. $ az ad sp create-for-rbac --role <role_name> \(1)
    2.      --name <service_principal> \(2)
    3.      --scopes /subscriptions/<subscription_id> (3)
    1Defines the role name. You can use the Contributor role, or you can specify a custom role which contains the necessary permissions.
    2Defines the service principal name.
    3Specifies the subscription ID.

    Example output

    1. Creating 'Contributor' role assignment under scope '/subscriptions/<subscription_id>'
    2. The output includes credentials that you must protect. Be sure that you do not
    3. include these credentials in your code or check the credentials into your source
    4. control. For more information, see https://aka.ms/azadsp-cli
    5. {
    6.   "appId": "ac461d78-bf4b-4387-ad16-7e32e328aec6",
    7.   "displayName": <service_principal>",
    8.   "password": "00000000-0000-0000-0000-000000000000",
    9.   "tenantId": "8049c7e9-c3de-762d-a54e-dc3f6be6a7ee"
    10. }

  5. Record the values of the appId and password parameters from the previous output. You need these values during OKD installation.

  6. If you applied the Contributor role to your service principal, assign the User Administrator Access role by running the following command:

    1. $ az role assignment create --role "User Access Administrator" \
    2.   --assignee-object-id $(az ad sp show --id <appId> --query id -o tsv) (1)
    1Specify the appId parameter value for your service principal.

Additional resources

Supported Azure regions

The installation program dynamically generates the list of available Microsoft Azure regions based on your subscription.

Supported Azure public regions

  • australiacentral (Australia Central)

  • australiaeast (Australia East)

  • australiasoutheast (Australia South East)

  • brazilsouth (Brazil South)

  • canadacentral (Canada Central)

  • canadaeast (Canada East)

  • centralindia (Central India)

  • centralus (Central US)

  • eastasia (East Asia)

  • eastus (East US)

  • eastus2 (East US 2)

  • francecentral (France Central)

  • germanywestcentral (Germany West Central)

  • israelcentral (Israel Central)

  • italynorth (Italy North)

  • japaneast (Japan East)

  • japanwest (Japan West)

  • koreacentral (Korea Central)

  • koreasouth (Korea South)

  • northcentralus (North Central US)

  • northeurope (North Europe)

  • norwayeast (Norway East)

  • qatarcentral (Qatar Central)

  • southafricanorth (South Africa North)

  • southcentralus (South Central US)

  • southeastasia (Southeast Asia)

  • southindia (South India)

  • swedencentral (Sweden Central)

  • switzerlandnorth (Switzerland North)

  • uaenorth (UAE North)

  • uksouth (UK South)

  • ukwest (UK West)

  • westcentralus (West Central US)

  • westeurope (West Europe)

  • westindia (West India)

  • westus (West US)

  • westus2 (West US 2)

  • westus3 (West US 3)

Supported Azure Government regions

Support for the following Microsoft Azure Government (MAG) regions was added in OKD version 4.6:

  • usgovtexas (US Gov Texas)

  • usgovvirginia (US Gov Virginia)

You can reference all available MAG regions in the Azure documentation. Other provided MAG regions are expected to work with OKD, but have not been tested.

Requirements for a cluster with user-provisioned infrastructure

For a cluster that contains user-provisioned infrastructure, you must deploy all of the required machines.

This section describes the requirements for deploying OKD on user-provisioned infrastructure.

Required machines for cluster installation

The smallest OKD clusters require the following hosts:

Table 1. Minimum required hosts
HostsDescription

One temporary bootstrap machine

The cluster requires the bootstrap machine to deploy the OKD cluster on the three control plane machines. You can remove the bootstrap machine after you install the cluster.

Three control plane machines

The control plane machines run the Kubernetes and OKD services that form the control plane.

At least two compute machines, which are also known as worker machines.

The workloads requested by OKD users run on the compute machines.

To maintain high availability of your cluster, use separate physical hosts for these cluster machines.

The bootstrap and control plane machines must use Fedora CoreOS (FCOS) as the operating system. However, the compute machines can choose between Fedora CoreOS (FCOS), Fedora 8.6, Fedora 8.7, or Fedora 8.8.

See Red Hat Enterprise Linux technology capabilities and limits.

Minimum resource requirements for cluster installation

Each cluster machine must meet the following minimum requirements:

Table 2. Minimum resource requirements
MachineOperating SystemvCPU [1]Virtual RAMStorageInput/Output Per Second (IOPS)[2]

Bootstrap

FCOS

4

16 GB

100 GB

300

Control plane

FCOS

4

16 GB

100 GB

300

Compute

FCOS

2

8 GB

100 GB

300

  1. One vCPU is equivalent to one physical core when simultaneous multithreading (SMT), or hyperthreading, is not enabled. When enabled, use the following formula to calculate the corresponding ratio: (threads per core × cores) × sockets = vCPUs.

  2. OKD and Kubernetes are sensitive to disk performance, and faster storage is recommended, particularly for etcd on the control plane nodes which require a 10 ms p99 fsync duration. Note that on many cloud platforms, storage size and IOPS scale together, so you might need to over-allocate storage volume to obtain sufficient performance.

  3. As with all user-provisioned installations, if you choose to use Fedora compute machines in your cluster, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks. Use of Fedora 7 compute machines is deprecated and has been removed in OKD 4.10 and later.

You are required to use Azure virtual machines that have the premiumIO parameter set to true.

If an instance type for your platform meets the minimum requirements for cluster machines, it is supported to use in OKD.

Tested instance types for Azure

The following Microsoft Azure instance types have been tested with OKD.

Machine types based on 64-bit x86 architecture

  • standardBSFamily

  • standardBsv2Family

  • standardDADSv5Family

  • standardDASv4Family

  • standardDASv5Family

  • standardDCACCV5Family

  • standardDCADCCV5Family

  • standardDCADSv5Family

  • standardDCASv5Family

  • standardDCSv3Family

  • standardDCSv2Family

  • standardDDCSv3Family

  • standardDDSv4Family

  • standardDDSv5Family

  • standardDLDSv5Family

  • standardDLSv5Family

  • standardDSFamily

  • standardDSv2Family

  • standardDSv2PromoFamily

  • standardDSv3Family

  • standardDSv4Family

  • standardDSv5Family

  • standardEADSv5Family

  • standardEASv4Family

  • standardEASv5Family

  • standardEBDSv5Family

  • standardEBSv5Family

  • standardECACCV5Family

  • standardECADCCV5Family

  • standardECADSv5Family

  • standardECASv5Family

  • standardEDSv4Family

  • standardEDSv5Family

  • standardEIADSv5Family

  • standardEIASv4Family

  • standardEIASv5Family

  • standardEIBDSv5Family

  • standardEIBSv5Family

  • standardEIDSv5Family

  • standardEISv3Family

  • standardEISv5Family

  • standardESv3Family

  • standardESv4Family

  • standardESv5Family

  • standardFXMDVSFamily

  • standardFSFamily

  • standardFSv2Family

  • standardGSFamily

  • standardHBrsv2Family

  • standardHBSFamily

  • standardHCSFamily

  • standardHXFamily

  • standardLASv3Family

  • standardLSFamily

  • standardLSv2Family

  • standardLSv3Family

  • standardMDSMediumMemoryv2Family

  • standardMIDSMediumMemoryv2Family

  • standardMISMediumMemoryv2Family

  • standardMSFamily

  • standardMSMediumMemoryv2Family

  • StandardNCADSA100v4Family

  • Standard NCASv3_T4 Family

  • standardNCSv2Family

  • standardNCSv3Family

  • standardNDSv2Family

  • standardNPSFamily

  • StandardNVADSA10v5Family

  • standardNVSv3Family

  • standardXEISv4Family

Tested instance types for Azure on 64-bit ARM infrastructures

The following Microsoft Azure ARM64 instance types have been tested with OKD.

Machine types based on 64-bit ARM architecture

  • standardDPSv5Family

  • standardDPDSv5Family

  • standardDPLDSv5Family

  • standardDPLSv5Family

  • standardEPSv5Family

  • standardEPDSv5Family

Using the Azure Marketplace offering

Using the Azure Marketplace offering lets you deploy an OKD cluster, which is billed on pay-per-use basis (hourly, per core) through Azure, while still being supported directly by Red Hat.

To deploy an OKD cluster using the Azure Marketplace offering, you must first obtain the Azure Marketplace image. The installation program uses this image to deploy worker nodes. When obtaining your image, consider the following:

  • While the images are the same, the Azure Marketplace publisher is different depending on your region. If you are located in North America, specify redhat as the publisher. If you are located in EMEA, specify redhat-limited as the publisher.

  • The offer includes a rh-ocp-worker SKU and a rh-ocp-worker-gen1 SKU. The rh-ocp-worker SKU represents a Hyper-V generation version 2 VM image. The default instance types used in OKD are version 2 compatible. If you plan to use an instance type that is only version 1 compatible, use the image associated with the rh-ocp-worker-gen1 SKU. The rh-ocp-worker-gen1 SKU represents a Hyper-V version 1 VM image.

Installing images with the Azure marketplace is not supported on clusters with 64-bit ARM instances.

Prerequisites

  • You have installed the Azure CLI client (az).

  • Your Azure account is entitled for the offer and you have logged into this account with the Azure CLI client.

Procedure

  1. Display all of the available OKD images by running one of the following commands:

    • North America:

      1. $  az vm image list --all --offer rh-ocp-worker --publisher redhat -o table

      Example output

      1. Offer          Publisher       Sku                 Urn                                                             Version
      2. -------------  --------------  ------------------  --------------------------------------------------------------  -----------------
      3. rh-ocp-worker  RedHat          rh-ocp-worker       RedHat:rh-ocp-worker:rh-ocp-worker:413.92.2023101700            413.92.2023101700
      4. rh-ocp-worker  RedHat          rh-ocp-worker-gen1  RedHat:rh-ocp-worker:rh-ocp-worker-gen1:413.92.2023101700       413.92.2023101700

    • EMEA:

      1. $  az vm image list --all --offer rh-ocp-worker --publisher redhat-limited -o table

      Example output

      1. Offer          Publisher       Sku                 Urn                                                                     Version
      2. -------------  --------------  ------------------  --------------------------------------------------------------          -----------------
      3. rh-ocp-worker  redhat-limited  rh-ocp-worker       redhat-limited:rh-ocp-worker:rh-ocp-worker:413.92.2023101700            413.92.2023101700
      4. rh-ocp-worker  redhat-limited  rh-ocp-worker-gen1  redhat-limited:rh-ocp-worker:rh-ocp-worker-gen1:413.92.2023101700       413.92.2023101700

    Regardless of the version of OKD that you install, the correct version of the Azure Marketplace image to use is 4.13. If required, your VMs are automatically upgraded as part of the installation process.

  2. Inspect the image for your offer by running one of the following commands:

    • North America:

      1. $ az vm image show --urn redhat:rh-ocp-worker:rh-ocp-worker:<version>

    • EMEA:

      1. $ az vm image show --urn redhat-limited:rh-ocp-worker:rh-ocp-worker:<version>

  3. Review the terms of the offer by running one of the following commands:

    • North America:

      1. $ az vm image terms show --urn redhat:rh-ocp-worker:rh-ocp-worker:<version>

    • EMEA:

      1. $ az vm image terms show --urn redhat-limited:rh-ocp-worker:rh-ocp-worker:<version>

  4. Accept the terms of the offering by running one of the following commands:

    • North America:

      1. $ az vm image terms accept --urn redhat:rh-ocp-worker:rh-ocp-worker:<version>

    • EMEA:

      1. $ az vm image terms accept --urn redhat-limited:rh-ocp-worker:rh-ocp-worker:<version>

  5. Record the image details of your offer. If you use the Azure Resource Manager (ARM) template to deploy your worker nodes:

    1. Update storageProfile.imageReference by deleting the id parameter and adding the offer, publisher, sku, and version parameters by using the values from your offer.

    2. Specify a plan for the virtual machines (VMs).

      Example 06_workers.json ARM template with an updated storageProfile.imageReference object and a specified plan

      1. ...
      2.   "plan" : {
      3.     "name": "rh-ocp-worker",
      4.     "product": "rh-ocp-worker",
      5.     "publisher": "redhat"
      6.   },
      7.   "dependsOn" : [
      8.     "[concat('Microsoft.Network/networkInterfaces/', concat(variables('vmNames')[copyIndex()], '-nic'))]"
      9.   ],
      10.   "properties" : {
      11. ...
      12.   "storageProfile": {
      13.     "imageReference": {
      14.     "offer": "rh-ocp-worker",
      15.     "publisher": "redhat",
      16.     "sku": "rh-ocp-worker",
      17.     "version": "413.92.2023101700"
      18.     }
      19.     ...
      20.    }
      21. ...
      22.   }

Obtaining the installation program

Before you install OKD, download the installation file on the host you are using for installation.

Prerequisites

  • You have a computer that runs Linux or macOS, with 500 MB of local disk space.

Procedure

  1. Download installer from https://github.com/openshift/okd/releases

    The installation program creates several files on the computer that you use to install your cluster. You must keep the installation program and the files that the installation program creates after you finish installing the cluster. Both files are required to delete the cluster.

    Deleting the files created by the installation program does not remove your cluster, even if the cluster failed during installation. To remove your cluster, complete the OKD uninstallation procedures for your specific cloud provider.

  2. Extract the installation program. For example, on a computer that uses a Linux operating system, run the following command:

    1. $ tar -xvf openshift-install-linux.tar.gz

  3. Download your installation pull secret from the Red Hat OpenShift Cluster Manager. This pull secret allows you to authenticate with the services that are provided by the included authorities, including Quay.io, which serves the container images for OKD components.

    Using a pull secret from the Red Hat OpenShift Cluster Manager is not required. You can use a pull secret for another private registry. Or, if you do not need the cluster to pull images from a private registry, you can use {"auths":{"fake":{"auth":"aWQ6cGFzcwo="}}} as the pull secret when prompted during the installation.

    If you do not use the pull secret from the Red Hat OpenShift Cluster Manager:

    • Red Hat Operators are not available.

    • The Telemetry and Insights operators do not send data to Red Hat.

    • Content from the Red Hat Container Catalog registry, such as image streams and Operators, are not available.

Generating a key pair for cluster node SSH access

During an OKD installation, you can provide an SSH public key to the installation program. The key is passed to the Fedora CoreOS (FCOS) nodes through their Ignition config files and is used to authenticate SSH access to the nodes. The key is added to the ~/.ssh/authorized_keys list for the core user on each node, which enables password-less authentication.

After the key is passed to the nodes, you can use the key pair to SSH in to the FCOS nodes as the user core. To access the nodes through SSH, the private key identity must be managed by SSH for your local user.

If you want to SSH in to your cluster nodes to perform installation debugging or disaster recovery, you must provide the SSH public key during the installation process. The ./openshift-install gather command also requires the SSH public key to be in place on the cluster nodes.

Do not skip this procedure in production environments, where disaster recovery and debugging is required.

You must use a local key, not one that you configured with platform-specific approaches such as AWS key pairs.

On clusters running Fedora CoreOS (FCOS), the SSH keys specified in the Ignition config files are written to the /home/core/.ssh/authorized_keys.d/core file. However, the Machine Config Operator manages SSH keys in the /home/core/.ssh/authorized_keys file and configures sshd to ignore the /home/core/.ssh/authorized_keys.d/core file. As a result, newly provisioned OKD nodes are not accessible using SSH until the Machine Config Operator reconciles the machine configs with the authorized_keys file. After you can access the nodes using SSH, you can delete the /home/core/.ssh/authorized_keys.d/core file.

Procedure

  1. If you do not have an existing SSH key pair on your local machine to use for authentication onto your cluster nodes, create one. For example, on a computer that uses a Linux operating system, run the following command:

    1. $ ssh-keygen -t ed25519 -N '' -f <path>/<file_name> (1)
    1Specify the path and file name, such as ~/.ssh/id_ed25519, of the new SSH key. If you have an existing key pair, ensure your public key is in the your ~/.ssh directory.

    If you plan to install an OKD cluster that uses the Fedora cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64, ppc64le, and s390x architectures, do not create a key that uses the ed25519 algorithm. Instead, create a key that uses the rsa or ecdsa algorithm.

  2. View the public SSH key:

    1. $ cat <path>/<file_name>.pub

    For example, run the following to view the ~/.ssh/id_ed25519.pub public key:

    1. $ cat ~/.ssh/id_ed25519.pub

  3. Add the SSH private key identity to the SSH agent for your local user, if it has not already been added. SSH agent management of the key is required for password-less SSH authentication onto your cluster nodes, or if you want to use the ./openshift-install gather command.

    On some distributions, default SSH private key identities such as ~/.ssh/id_rsa and ~/.ssh/id_dsa are managed automatically.

    1. If the ssh-agent process is not already running for your local user, start it as a background task:

      1. $ eval "$(ssh-agent -s)"

      Example output

      1. Agent pid 31874

      If your cluster is in FIPS mode, only use FIPS-compliant algorithms to generate the SSH key. The key must be either RSA or ECDSA.

  4. Add your SSH private key to the ssh-agent:

    1. $ ssh-add <path>/<file_name> (1)
    1Specify the path and file name for your SSH private key, such as ~/.ssh/id_ed25519

    Example output

    1. Identity added: /home/<you>/<path>/<file_name> (<computer_name>)

Next steps

  • When you install OKD, provide the SSH public key to the installation program. If you install a cluster on infrastructure that you provision, you must provide the key to the installation program.

Creating the installation files for Azure

To install OKD on Microsoft Azure using user-provisioned infrastructure, you must generate the files that the installation program needs to deploy your cluster and modify them so that the cluster creates only the machines that it will use. You generate and customize the install-config.yaml file, Kubernetes manifests, and Ignition config files. You also have the option to first set up a separate var partition during the preparation phases of installation.

Optional: Creating a separate /var partition

It is recommended that disk partitioning for OKD be left to the installer. However, there are cases where you might want to create separate partitions in a part of the filesystem that you expect to grow.

OKD supports the addition of a single partition to attach storage to either the /var partition or a subdirectory of /var. For example:

  • /var/lib/containers: Holds container-related content that can grow as more images and containers are added to a system.

  • /var/lib/etcd: Holds data that you might want to keep separate for purposes such as performance optimization of etcd storage.

  • /var: Holds data that you might want to keep separate for purposes such as auditing.

Storing the contents of a /var directory separately makes it easier to grow storage for those areas as needed and reinstall OKD at a later date and keep that data intact. With this method, you will not have to pull all your containers again, nor will you have to copy massive log files when you update systems.

Because /var must be in place before a fresh installation of Fedora CoreOS (FCOS), the following procedure sets up the separate /var partition by creating a machine config manifest that is inserted during the openshift-install preparation phases of an OKD installation.

If you follow the steps to create a separate /var partition in this procedure, it is not necessary to create the Kubernetes manifest and Ignition config files again as described later in this section.

Procedure

  1. Create a directory to hold the OKD installation files:

    1. $ mkdir $HOME/clusterconfig

  2. Run openshift-install to create a set of files in the manifest and openshift subdirectories. Answer the system questions as you are prompted:

    1. $ openshift-install create manifests --dir $HOME/clusterconfig

    Example output

    1. ? SSH Public Key ...
    2. INFO Credentials loaded from the "myprofile" profile in file "/home/myuser/.aws/credentials"
    3. INFO Consuming Install Config from target directory
    4. INFO Manifests created in: $HOME/clusterconfig/manifests and $HOME/clusterconfig/openshift

  3. Optional: Confirm that the installation program created manifests in the clusterconfig/openshift directory:

    1. $ ls $HOME/clusterconfig/openshift/

    Example output

    1. 99_kubeadmin-password-secret.yaml
    2. 99_openshift-cluster-api_master-machines-0.yaml
    3. 99_openshift-cluster-api_master-machines-1.yaml
    4. 99_openshift-cluster-api_master-machines-2.yaml
    5. ...

  4. Create a Butane config that configures the additional partition. For example, name the file $HOME/clusterconfig/98-var-partition.bu, change the disk device name to the name of the storage device on the worker systems, and set the storage size as appropriate. This example places the /var directory on a separate partition:

    1. variant: openshift
    2. version: 4.14.0
    3. metadata:
    4.   labels:
    5.     machineconfiguration.openshift.io/role: worker
    6.   name: 98-var-partition
    7. storage:
    8.   disks:
    9.   - device: /dev/disk/by-id/<device_name> (1)
    10.     partitions:
    11.     - label: var
    12.       start_mib: <partition_start_offset> (2)
    13.       size_mib: <partition_size> (3)
    14.   filesystems:
    15.     - device: /dev/disk/by-partlabel/var
    16.       path: /var
    17.       format: xfs
    18.       mount_options: [defaults, prjquota] (4)
    19.       with_mount_unit: true
    1The storage device name of the disk that you want to partition.
    2When adding a data partition to the boot disk, a minimum value of 25000 MiB (Mebibytes) is recommended. The root file system is automatically resized to fill all available space up to the specified offset. If no value is specified, or if the specified value is smaller than the recommended minimum, the resulting root file system will be too small, and future reinstalls of FCOS might overwrite the beginning of the data partition.
    3The size of the data partition in mebibytes.
    4The prjquota mount option must be enabled for filesystems used for container storage.

    When creating a separate /var partition, you cannot use different instance types for worker nodes, if the different instance types do not have the same device name.

  5. Create a manifest from the Butane config and save it to the clusterconfig/openshift directory. For example, run the following command:

    1. $ butane $HOME/clusterconfig/98-var-partition.bu -o $HOME/clusterconfig/openshift/98-var-partition.yaml

  6. Run openshift-install again to create Ignition configs from a set of files in the manifest and openshift subdirectories:

    1. $ openshift-install create ignition-configs --dir $HOME/clusterconfig
    2. $ ls $HOME/clusterconfig/
    3. auth  bootstrap.ign  master.ign  metadata.json  worker.ign

Now you can use the Ignition config files as input to the installation procedures to install Fedora CoreOS (FCOS) systems.

Creating the installation configuration file

You can customize the OKD cluster you install on Microsoft Azure.

Prerequisites

  • You have the OKD installation program and the pull secret for your cluster. For a restricted network installation, these files are on your mirror host.

  • You have the imageContentSources values that were generated during mirror registry creation.

  • You have obtained the contents of the certificate for your mirror registry.

  • You have retrieved a Fedora CoreOS (FCOS) image and uploaded it to an accessible location.

  • You have an Azure subscription ID and tenant ID.

  • If you are installing the cluster using a service principal, you have its application ID and password.

  • If you are installing the cluster using a system-assigned managed identity, you have enabled it on the virtual machine that you will run the installation program from.

  • If you are installing the cluster using a user-assigned managed identity, you have met these prerequisites:

    • You have its client ID.

    • You have assigned it to the virtual machine that you will run the installation program from.

Procedure

  1. Optional: If you have run the installation program on this computer before, and want to use an alternative service principal or managed identity, go to the ~/.azure/ directory and delete the osServicePrincipal.json configuration file.

    Deleting this file prevents the installation program from automatically reusing subscription and authentication values from a previous installation.

  2. Create the install-config.yaml file.

    1. Change to the directory that contains the installation program and run the following command:

      1. $ ./openshift-install create install-config --dir <installation_directory> (1)
      1For <installation_directory>, specify the directory name to store the files that the installation program creates.

      When specifying the directory:

      • Verify that the directory has the execute permission. This permission is required to run Terraform binaries under the installation directory.

      • Use an empty directory. Some installation assets, such as bootstrap X.509 certificates, have short expiration intervals, therefore you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier OKD version.

        Always delete the ~/.powervs directory to avoid reusing a stale configuration. Run the following command:

        1. $ rm -rf ~/.powervs

    2. At the prompts, provide the configuration details for your cloud:

      1. Optional: Select an SSH key to use to access 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.

      2. Select azure as the platform to target.

        If the installation program cannot locate the osServicePrincipal.json configuration file from a previous installation, you are prompted for Azure subscription and authentication values.

      3. Enter the following Azure parameter values for your subscription:

        • azure subscription id: Enter the subscription ID to use for the cluster.

        • azure tenant id: Enter the tenant ID.

      4. Depending on the Azure identity you are using to deploy the cluster, do one of the following when prompted for the azure service principal client id:

        • If you are using a service principal, enter its application ID.

        • If you are using a system-assigned managed identity, leave this value blank.

        • If you are using a user-assigned managed identity, specify its client ID.

      5. Depending on the Azure identity you are using to deploy the cluster, do one of the following when prompted for the azure service principal client secret:

        • If you are using a service principal, enter its password.

        • If you are using a system-assigned managed identity, leave this value blank.

        • If you are using a user-assigned managed identity, leave this value blank.

      6. Select the region to deploy the cluster to.

      7. Select the base domain to deploy the cluster to. The base domain corresponds to the Azure DNS Zone that you created for your cluster.

      8. Enter a descriptive name for your cluster.

        All Azure resources that are available through public endpoints are subject to resource name restrictions, and you cannot create resources that use certain terms. For a list of terms that Azure restricts, see Resolve reserved resource name errors in the Azure documentation.

      9. Paste the pull secret from the Red Hat OpenShift Cluster Manager.

  1. Edit the install-config.yaml file to give the additional information that is required for an installation in a restricted network.

    1. Update the pullSecret value to contain the authentication information for your registry:

      1. pullSecret: '{"auths":{"<mirror_host_name>:5000": {"auth": "<credentials>","email": "you@example.com"}}}'

      For <mirror_host_name>, specify the registry domain name that you specified in the certificate for your mirror registry, and for <credentials>, specify the base64-encoded user name and password for your mirror registry.

    2. Add the additionalTrustBundle parameter and value.

      1. additionalTrustBundle: |
      2.   -----BEGIN CERTIFICATE-----
      3.   ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
      4.   -----END CERTIFICATE-----

      The value must be the contents of the certificate file that you used for your mirror registry. The certificate file can be an existing, trusted certificate authority, or the self-signed certificate that you generated for the mirror registry.

    3. Define the network and subnets for the VNet to install the cluster under the platform.azure field:

      1. networkResourceGroupName: <vnet_resource_group> (1)
      2. virtualNetwork: <vnet> (2)
      3. controlPlaneSubnet: <control_plane_subnet> (3)
      4. computeSubnet: <compute_subnet> (4)
      1Replace <vnet_resource_group> with the resource group name that contains the existing virtual network (VNet).
      2Replace <vnet> with the existing virtual network name.
      3Replace <control_plane_subnet> with the existing subnet name to deploy the control plane machines.
      4Replace <compute_subnet> with the existing subnet name to deploy compute machines.

    4. Add the image content resources, which resemble the following YAML excerpt:

      1. imageContentSources:
      2. - mirrors:
      3.   - <mirror_host_name>:5000/<repo_name>/release
      4.   source: quay.io/openshift-release-dev/ocp-release
      5. - mirrors:
      6.   - <mirror_host_name>:5000/<repo_name>/release
      7.   source: registry.redhat.io/ocp/release

      For these values, use the imageContentSources that you recorded during mirror registry creation.

    5. Optional: Set the publishing strategy to Internal:

      1. publish: Internal

      By setting this option, you create an internal Ingress Controller and a private load balancer.

      Azure Firewall does not work seamlessly with Azure Public Load balancers. Thus, when using Azure Firewall for restricting internet access, the publish field in install-config.yaml should be set to Internal.

  2. Make any other modifications to the install-config.yaml file that you require. You can find more information about the available parameters in the Installation configuration parameters section.

  3. Back up the install-config.yaml file so that you can use it to install multiple clusters.

    The install-config.yaml file is consumed during the installation process. If you want to reuse the file, you must back it up now.

If previously not detected, the installation program creates an osServicePrincipal.json configuration file and stores this file in the ~/.azure/ directory on your computer. This ensures that the installation program can load the profile when it is creating an OKD cluster on the target platform.

Configuring the cluster-wide proxy during installation

Production environments can deny direct access to the internet and instead have an HTTP or HTTPS proxy available. You can configure a new OKD cluster to use a proxy by configuring the proxy settings in the install-config.yaml file.

Prerequisites

  • You have an existing install-config.yaml file.

  • You reviewed the sites that your cluster requires access to and determined whether any of them need to bypass the proxy. By default, all cluster egress traffic is proxied, including calls to hosting cloud provider APIs. You added sites to the Proxy object’s spec.noProxy field to bypass the proxy if necessary.

    The Proxy object status.noProxy field is populated with the values of the networking.machineNetwork[].cidr, networking.clusterNetwork[].cidr, and networking.serviceNetwork[] fields from your installation configuration.

    For installations on Amazon Web Services (AWS), Google Cloud Platform (GCP), Microsoft Azure, and OpenStack, the Proxy object status.noProxy field is also populated with the instance metadata endpoint (169.254.169.254).

Procedure

  1. Edit your install-config.yaml file and add the proxy settings. For example:

    1. apiVersion: v1
    2. baseDomain: my.domain.com
    3. proxy:
    4.   httpProxy: http://<username>:<pswd>@<ip>:<port> (1)
    5.   httpsProxy: https://<username>:<pswd>@<ip>:<port> (2)
    6.   noProxy: example.com (3)
    7. additionalTrustBundle: | (4)
    8.     -----BEGIN CERTIFICATE-----
    9.     <MY_TRUSTED_CA_CERT>
    10.     -----END CERTIFICATE-----
    11. additionalTrustBundlePolicy: <policy_to_add_additionalTrustBundle> (5)
    1A proxy URL to use for creating HTTP connections outside the cluster. The URL scheme must be http.
    2A proxy URL to use for creating HTTPS connections outside the cluster.
    3A comma-separated list of destination domain names, IP addresses, or other network CIDRs to exclude from proxying. Preface a domain with . to match subdomains only. For example, .y.com matches x.y.com, but not y.com. Use * to bypass the proxy for all destinations.
    4If provided, the installation program generates a config map that is named user-ca-bundle in the openshift-config namespace that contains one or more additional CA certificates that are required for proxying HTTPS connections. The Cluster Network Operator then creates a trusted-ca-bundle config map that merges these contents with the Fedora CoreOS (FCOS) trust bundle, and this config map is referenced in the trustedCA field of the Proxy object. The additionalTrustBundle field is required unless the proxy’s identity certificate is signed by an authority from the FCOS trust bundle.
    5Optional: The policy to determine the configuration of the Proxy object to reference the user-ca-bundle config map in the trustedCA field. The allowed values are Proxyonly and Always. Use Proxyonly to reference the user-ca-bundle config map only when http/https proxy is configured. Use Always to always reference the user-ca-bundle config map. The default value is Proxyonly.

    The installation program does not support the proxy readinessEndpoints field.

    If the installer times out, restart and then complete the deployment by using the wait-for command of the installer. For example:

    1. $ ./openshift-install wait-for install-complete —log-level debug

  2. Save the file and reference it when installing OKD.

The installation program creates a cluster-wide proxy that is named cluster that uses the proxy settings in the provided install-config.yaml file. If no proxy settings are provided, a cluster Proxy object is still created, but it will have a nil spec.

Only the Proxy object named cluster is supported, and no additional proxies can be created.

Exporting common variables for ARM templates

You must export a common set of variables that are used with the provided Azure Resource Manager (ARM) templates used to assist in completing a user-provided infrastructure install on Microsoft Azure.

Specific ARM templates can also require additional exported variables, which are detailed in their related procedures.

Prerequisites

  • Obtain the OKD installation program and the pull secret for your cluster.

Procedure

  1. Export common variables found in the install-config.yaml to be used by the provided ARM templates:

    1. $ export CLUSTER_NAME=<cluster_name>(1)
    2. $ export AZURE_REGION=<azure_region>(2)
    3. $ export SSH_KEY=<ssh_key>(3)
    4. $ export BASE_DOMAIN=<base_domain>(4)
    5. $ export BASE_DOMAIN_RESOURCE_GROUP=<base_domain_resource_group>(5)
    1The value of the .metadata.name attribute from the install-config.yaml file.
    2The region to deploy the cluster into, for example centralus. This is the value of the .platform.azure.region attribute from the install-config.yaml file.
    3The SSH RSA public key file as a string. You must enclose the SSH key in quotes since it contains spaces. This is the value of the .sshKey attribute from the install-config.yaml file.
    4The base domain to deploy the cluster to. The base domain corresponds to the public DNS zone that you created for your cluster. This is the value of the .baseDomain attribute from the install-config.yaml file.
    5The resource group where the public DNS zone exists. This is the value of the .platform.azure.baseDomainResourceGroupName attribute from the install-config.yaml file.

    For example:

    1. $ export CLUSTER_NAME=test-cluster
    2. $ export AZURE_REGION=centralus
    3. $ export SSH_KEY="ssh-rsa xxx/xxx/xxx= user@email.com"
    4. $ export BASE_DOMAIN=example.com
    5. $ export BASE_DOMAIN_RESOURCE_GROUP=ocp-cluster

  2. Export the kubeadmin credentials:

    1. $ export KUBECONFIG=<installation_directory>/auth/kubeconfig (1)
    1For <installation_directory>, specify the path to the directory that you stored the installation files in.

Creating the Kubernetes manifest and Ignition config files

Because you must modify some cluster definition files and manually start the cluster machines, you must generate the Kubernetes manifest and Ignition config files that the cluster needs to configure the machines.

The installation configuration file transforms into the Kubernetes manifests. The manifests wrap into the Ignition configuration files, which are later used to configure the cluster machines.

  • The Ignition config files that the OKD installation program generates contain certificates that expire after 24 hours, which are then renewed at that time. If the cluster is shut down before renewing the certificates and the cluster is later restarted after the 24 hours have elapsed, the cluster automatically recovers the expired certificates. The exception is that you must manually approve the pending node-bootstrapper certificate signing requests (CSRs) to recover kubelet certificates. See the documentation for Recovering from expired control plane certificates for more information.

  • It is recommended that you use Ignition config files within 12 hours after they are generated because the 24-hour certificate rotates from 16 to 22 hours after the cluster is installed. By using the Ignition config files within 12 hours, you can avoid installation failure if the certificate update runs during installation.

Prerequisites

  • You obtained the OKD installation program.

  • You created the install-config.yaml installation configuration file.

Procedure

  1. Change to the directory that contains the OKD installation program and generate the Kubernetes manifests for the cluster:

    1. $ ./openshift-install create manifests --dir <installation_directory> (1)
    1For <installation_directory>, specify the installation directory that contains the install-config.yaml file you created.

  2. Remove the Kubernetes manifest files that define the control plane machines:

    1. $ rm -f <installation_directory>/openshift/99_openshift-cluster-api_master-machines-*.yaml

    By removing these files, you prevent the cluster from automatically generating control plane machines.

  3. Remove the Kubernetes manifest files that define the control plane machine set:

    1. $ rm -f <installation_directory>/openshift/99_openshift-machine-api_master-control-plane-machine-set.yaml

  4. Remove the Kubernetes manifest files that define the worker machines:

    1. $ rm -f <installation_directory>/openshift/99_openshift-cluster-api_worker-machineset-*.yaml

    Because you create and manage the worker machines yourself, you do not need to initialize these machines.

  5. Check that the mastersSchedulable parameter in the <installation_directory>/manifests/cluster-scheduler-02-config.yml Kubernetes manifest file is set to false. This setting prevents pods from being scheduled on the control plane machines:

    1. Open the <installation_directory>/manifests/cluster-scheduler-02-config.yml file.

    2. Locate the mastersSchedulable parameter and ensure that it is set to false.

    3. Save and exit the file.

  6. Optional: If you do not want the Ingress Operator to create DNS records on your behalf, remove the privateZone and publicZone sections from the <installation_directory>/manifests/cluster-dns-02-config.yml DNS configuration file:

    1. apiVersion: config.openshift.io/v1
    2. kind: DNS
    3. metadata:
    4.   creationTimestamp: null
    5.   name: cluster
    6. spec:
    7.   baseDomain: example.openshift.com
    8.   privateZone: (1)
    9.     id: mycluster-100419-private-zone
    10.   publicZone: (1)
    11.     id: example.openshift.com
    12. status: {}
    1Remove this section completely.

    If you do so, you must add ingress DNS records manually in a later step.

  7. When configuring Azure on user-provisioned infrastructure, you must export some common variables defined in the manifest files to use later in the Azure Resource Manager (ARM) templates:

    1. Export the infrastructure ID by using the following command:

      1. $ export INFRA_ID=<infra_id> (1)
      1The OKD cluster has been assigned an identifier (INFRA_ID) in the form of <cluster_name>-<random_string>. This will be used as the base name for most resources created using the provided ARM templates. This is the value of the .status.infrastructureName attribute from the manifests/cluster-infrastructure-02-config.yml file.

    2. Export the resource group by using the following command:

      1. $ export RESOURCE_GROUP=<resource_group> (1)
      1All resources created in this Azure deployment exists as part of a resource group. The resource group name is also based on the INFRA_ID, in the form of <cluster_name>-<random_string>-rg. This is the value of the .status.platformStatus.azure.resourceGroupName attribute from the manifests/cluster-infrastructure-02-config.yml file.

  8. To create the Ignition configuration files, run the following command from the directory that contains the installation program:

    1. $ ./openshift-install create ignition-configs --dir <installation_directory> (1)
    1For <installation_directory>, specify the same installation directory.

    Ignition config files are created for the bootstrap, control plane, and compute nodes in the installation directory. The kubeadmin-password and kubeconfig files are created in the ./<installation_directory>/auth directory:

    1. .
    2. ├── auth
    3. │   ├── kubeadmin-password
    4. │   └── kubeconfig
    5. ├── bootstrap.ign
    6. ├── master.ign
    7. ├── metadata.json
    8. └── worker.ign

Creating the Azure resource group

You must create a Microsoft Azure resource group and an identity for that resource group. These are both used during the installation of your OKD cluster on Azure.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

Procedure

  1. Create the resource group in a supported Azure region:

    1. $ az group create --name ${RESOURCE_GROUP} --location ${AZURE_REGION}

  2. Create an Azure identity for the resource group:

    1. $ az identity create -g ${RESOURCE_GROUP} -n ${INFRA_ID}-identity

    This is used to grant the required access to Operators in your cluster. For example, this allows the Ingress Operator to create a public IP and its load balancer. You must assign the Azure identity to a role.

  3. Grant the Contributor role to the Azure identity:

    1. Export the following variables required by the Azure role assignment:

      1. $ export PRINCIPAL_ID=`az identity show -g ${RESOURCE_GROUP} -n ${INFRA_ID}-identity --query principalId --out tsv`
      1. $ export RESOURCE_GROUP_ID=`az group show -g ${RESOURCE_GROUP} --query id --out tsv`

    2. Assign the Contributor role to the identity:

      1. $ az role assignment create --assignee "${PRINCIPAL_ID}" --role 'Contributor' --scope "${RESOURCE_GROUP_ID}"

      If you want to assign a custom role with all the required permissions to the identity, run the following command:

      1. $ az role assignment create —assignee “${PRINCIPAL_ID}” —role <custom_role> \ (1)
      2. —scope “${RESOURCE_GROUP_ID}”
      1Specifies the custom role name.

Uploading the FCOS cluster image and bootstrap Ignition config file

The Azure client does not support deployments based on files existing locally. You must copy and store the FCOS virtual hard disk (VHD) cluster image and bootstrap Ignition config file in a storage container so they are accessible during deployment.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

Procedure

  1. Create an Azure storage account to store the VHD cluster image:

    1. $ az storage account create -g ${RESOURCE_GROUP} --location ${AZURE_REGION} --name ${CLUSTER_NAME}sa --kind Storage --sku Standard_LRS

    The Azure storage account name must be between 3 and 24 characters in length and use numbers and lower-case letters only. If your CLUSTER_NAME variable does not follow these restrictions, you must manually define the Azure storage account name. For more information on Azure storage account name restrictions, see Resolve errors for storage account names in the Azure documentation.

  2. Export the storage account key as an environment variable:

    1. $ export ACCOUNT_KEY=`az storage account keys list -g ${RESOURCE_GROUP} --account-name ${CLUSTER_NAME}sa --query "[0].value" -o tsv`

  3. Export the URL of the FCOS VHD to an environment variable:

    1. $ export VHD_URL=`openshift-install coreos print-stream-json | jq -r '.architectures.<architecture>."rhel-coreos-extensions"."azure-disk".url'`

    The FCOS images might not change with every release of OKD. You must specify an image with the highest version that is less than or equal to the OKD version that you install. Use the image version that matches your OKD version if it is available.

  4. Create the storage container for the VHD:

    1. $ az storage container create --name vhd --account-name ${CLUSTER_NAME}sa --account-key ${ACCOUNT_KEY}

  5. Copy the local VHD to a blob:

    1. $ az storage blob copy start --account-name ${CLUSTER_NAME}sa --account-key ${ACCOUNT_KEY} --destination-blob "rhcos.vhd" --destination-container vhd --source-uri "${VHD_URL}"

  6. Create a blob storage container and upload the generated bootstrap.ign file:

    1. $ az storage container create --name files --account-name ${CLUSTER_NAME}sa --account-key ${ACCOUNT_KEY}
    1. $ az storage blob upload --account-name ${CLUSTER_NAME}sa --account-key ${ACCOUNT_KEY} -c "files" -f "<installation_directory>/bootstrap.ign" -n "bootstrap.ign"

Example for creating DNS zones

DNS records are required for clusters that use user-provisioned infrastructure. You should choose the DNS strategy that fits your scenario.

For this example, Azure’s DNS solution is used, so you will create a new public DNS zone for external (internet) visibility and a private DNS zone for internal cluster resolution.

The public DNS zone is not required to exist in the same resource group as the cluster deployment and might already exist in your organization for the desired base domain. If that is the case, you can skip creating the public DNS zone; be sure the installation config you generated earlier reflects that scenario.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

Procedure

  1. Create the new public DNS zone in the resource group exported in the BASE_DOMAIN_RESOURCE_GROUP environment variable:

    1. $ az network dns zone create -g ${BASE_DOMAIN_RESOURCE_GROUP} -n ${CLUSTER_NAME}.${BASE_DOMAIN}

    You can skip this step if you are using a public DNS zone that already exists.

  2. Create the private DNS zone in the same resource group as the rest of this deployment:

    1. $ az network private-dns zone create -g ${RESOURCE_GROUP} -n ${CLUSTER_NAME}.${BASE_DOMAIN}

You can learn more about configuring a public DNS zone in Azure by visiting that section.

Creating a VNet in Azure

You must create a virtual network (VNet) in Microsoft Azure for your OKD cluster to use. You can customize the VNet to meet your requirements. One way to create the VNet is to modify the provided Azure Resource Manager (ARM) template.

If you do not use the provided ARM template to create your Azure infrastructure, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, you might have to contact Red Hat support with your installation logs.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

Procedure

  1. Copy the template from the ARM template for the VNet section of this topic and save it as 01_vnet.json in your cluster’s installation directory. This template describes the VNet that your cluster requires.

  2. Create the deployment by using the az CLI:

    1. $ az deployment group create -g ${RESOURCE_GROUP} \
    2.   --template-file "<installation_directory>/01_vnet.json" \
    3.   --parameters baseName="${INFRA_ID}"(1)
    1The base name to be used in resource names; this is usually the cluster’s infrastructure ID.

  3. Link the VNet template to the private DNS zone:

    1. $ az network private-dns link vnet create -g ${RESOURCE_GROUP} -z ${CLUSTER_NAME}.${BASE_DOMAIN} -n ${INFRA_ID}-network-link -v "${INFRA_ID}-vnet" -e false

ARM template for the VNet

You can use the following Azure Resource Manager (ARM) template to deploy the VNet that you need for your OKD cluster:

01_vnet.json ARM template

  1. {
  2.   "$schema" : "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  3.   "contentVersion" : "1.0.0.0",
  4.   "parameters" : {
  5.     "baseName" : {
  6.       "type" : "string",
  7.       "minLength" : 1,
  8.       "metadata" : {
  9.         "description" : "Base name to be used in resource names (usually the cluster's Infra ID)"
  10.       }
  11.     }
  12.   },
  13.   "variables" : {
  14.     "location" : "[resourceGroup().location]",
  15.     "virtualNetworkName" : "[concat(parameters('baseName'), '-vnet')]",
  16.     "addressPrefix" : "10.0.0.0/16",
  17.     "masterSubnetName" : "[concat(parameters('baseName'), '-master-subnet')]",
  18.     "masterSubnetPrefix" : "10.0.0.0/24",
  19.     "nodeSubnetName" : "[concat(parameters('baseName'), '-worker-subnet')]",
  20.     "nodeSubnetPrefix" : "10.0.1.0/24",
  21.     "clusterNsgName" : "[concat(parameters('baseName'), '-nsg')]"
  22.   },
  23.   "resources" : [
  24.     {
  25.       "apiVersion" : "2018-12-01",
  26.       "type" : "Microsoft.Network/virtualNetworks",
  27.       "name" : "[variables('virtualNetworkName')]",
  28.       "location" : "[variables('location')]",
  29.       "dependsOn" : [
  30.         "[concat('Microsoft.Network/networkSecurityGroups/', variables('clusterNsgName'))]"
  31.       ],
  32.       "properties" : {
  33.         "addressSpace" : {
  34.           "addressPrefixes" : [
  35.             "[variables('addressPrefix')]"
  36.           ]
  37.         },
  38.         "subnets" : [
  39.           {
  40.             "name" : "[variables('masterSubnetName')]",
  41.             "properties" : {
  42.               "addressPrefix" : "[variables('masterSubnetPrefix')]",
  43.               "serviceEndpoints": [],
  44.               "networkSecurityGroup" : {
  45.                 "id" : "[resourceId('Microsoft.Network/networkSecurityGroups', variables('clusterNsgName'))]"
  46.               }
  47.             }
  48.           },
  49.           {
  50.             "name" : "[variables('nodeSubnetName')]",
  51.             "properties" : {
  52.               "addressPrefix" : "[variables('nodeSubnetPrefix')]",
  53.               "serviceEndpoints": [],
  54.               "networkSecurityGroup" : {
  55.                 "id" : "[resourceId('Microsoft.Network/networkSecurityGroups', variables('clusterNsgName'))]"
  56.               }
  57.             }
  58.           }
  59.         ]
  60.       }
  61.     },
  62.     {
  63.       "type" : "Microsoft.Network/networkSecurityGroups",
  64.       "name" : "[variables('clusterNsgName')]",
  65.       "apiVersion" : "2018-10-01",
  66.       "location" : "[variables('location')]",
  67.       "properties" : {
  68.         "securityRules" : [
  69.           {
  70.             "name" : "apiserver_in",
  71.             "properties" : {
  72.               "protocol" : "Tcp",
  73.               "sourcePortRange" : "*",
  74.               "destinationPortRange" : "6443",
  75.               "sourceAddressPrefix" : "*",
  76.               "destinationAddressPrefix" : "*",
  77.               "access" : "Allow",
  78.               "priority" : 101,
  79.               "direction" : "Inbound"
  80.             }
  81.           }
  82.         ]
  83.       }
  84.     }
  85.   ]
  86. }

Deploying the FCOS cluster image for the Azure infrastructure

You must use a valid Fedora CoreOS (FCOS) image for Microsoft Azure for your OKD nodes.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

  • Store the FCOS virtual hard disk (VHD) cluster image in an Azure storage container.

  • Store the bootstrap Ignition config file in an Azure storage container.

Procedure

  1. Copy the template from the ARM template for image storage section of this topic and save it as 02_storage.json in your cluster’s installation directory. This template describes the image storage that your cluster requires.

  2. Export the FCOS VHD blob URL as a variable:

    1. $ export VHD_BLOB_URL=`az storage blob url --account-name ${CLUSTER_NAME}sa --account-key ${ACCOUNT_KEY} -c vhd -n "rhcos.vhd" -o tsv`

  3. Deploy the cluster image:

    1. $ az deployment group create -g ${RESOURCE_GROUP} \
    2.   --template-file "<installation_directory>/02_storage.json" \
    3.   --parameters vhdBlobURL="${VHD_BLOB_URL}" \ (1)
    4.   --parameters baseName="${INFRA_ID}" \ (2)
    5.   --parameters storageAccount="${CLUSTER_NAME}sa" \ (3)
    6.   --parameters architecture="<architecture>" (4)
    1The blob URL of the FCOS VHD to be used to create master and worker machines.
    2The base name to be used in resource names; this is usually the cluster’s infrastructure ID.
    3The name of your Azure storage account.
    4Specify the system architecture. Valid values are x64 (default) or Arm64.

ARM template for image storage

You can use the following Azure Resource Manager (ARM) template to deploy the stored Fedora CoreOS (FCOS) image that you need for your OKD cluster:

02_storage.json ARM template

  1. {
  2.   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  3.   "contentVersion": "1.0.0.0",
  4.   "parameters": {
  5.     "architecture": {
  6.       "type": "string",
  7.       "metadata": {
  8.         "description": "The architecture of the Virtual Machines"
  9.       },
  10.       "defaultValue": "x64",
  11.       "allowedValues": [
  12.         "Arm64",
  13.         "x64"
  14.       ]
  15.     },
  16.     "baseName": {
  17.       "type": "string",
  18.       "minLength": 1,
  19.       "metadata": {
  20.         "description": "Base name to be used in resource names (usually the cluster's Infra ID)"
  21.       }
  22.     },
  23.     "storageAccount": {
  24.       "type": "string",
  25.       "metadata": {
  26.         "description": "The Storage Account name"
  27.       }
  28.     },
  29.     "vhdBlobURL": {
  30.       "type": "string",
  31.       "metadata": {
  32.         "description": "URL pointing to the blob where the VHD to be used to create master and worker machines is located"
  33.       }
  34.     }
  35.   },
  36.   "variables": {
  37.     "location": "[resourceGroup().location]",
  38.     "galleryName": "[concat('gallery_', replace(parameters('baseName'), '-', '_'))]",
  39.     "imageName": "[parameters('baseName')]",
  40.     "imageNameGen2": "[concat(parameters('baseName'), '-gen2')]",
  41.     "imageRelease": "1.0.0"
  42.   },
  43.   "resources": [
  44.     {
  45.       "apiVersion": "2021-10-01",
  46.       "type": "Microsoft.Compute/galleries",
  47.       "name": "[variables('galleryName')]",
  48.       "location": "[variables('location')]",
  49.       "resources": [
  50.         {
  51.           "apiVersion": "2021-10-01",
  52.           "type": "images",
  53.           "name": "[variables('imageName')]",
  54.           "location": "[variables('location')]",
  55.           "dependsOn": [
  56.             "[variables('galleryName')]"
  57.           ],
  58.           "properties": {
  59.             "architecture": "[parameters('architecture')]",
  60.             "hyperVGeneration": "V1",
  61.             "identifier": {
  62.               "offer": "rhcos",
  63.               "publisher": "RedHat",
  64.               "sku": "basic"
  65.             },
  66.             "osState": "Generalized",
  67.             "osType": "Linux"
  68.           },
  69.           "resources": [
  70.             {
  71.               "apiVersion": "2021-10-01",
  72.               "type": "versions",
  73.               "name": "[variables('imageRelease')]",
  74.               "location": "[variables('location')]",
  75.               "dependsOn": [
  76.                 "[variables('imageName')]"
  77.               ],
  78.               "properties": {
  79.                 "publishingProfile": {
  80.                   "storageAccountType": "Standard_LRS",
  81.                   "targetRegions": [
  82.                     {
  83.                       "name": "[variables('location')]",
  84.                       "regionalReplicaCount": "1"
  85.                     }
  86.                   ]
  87.                 },
  88.                 "storageProfile": {
  89.                   "osDiskImage": {
  90.                     "source": {
  91.                       "id": "[resourceId('Microsoft.Storage/storageAccounts', parameters('storageAccount'))]",
  92.                       "uri": "[parameters('vhdBlobURL')]"
  93.                     }
  94.                   }
  95.                 }
  96.               }
  97.             }
  98.           ]
  99.         },
  100.         {
  101.           "apiVersion": "2021-10-01",
  102.           "type": "images",
  103.           "name": "[variables('imageNameGen2')]",
  104.           "location": "[variables('location')]",
  105.           "dependsOn": [
  106.             "[variables('galleryName')]"
  107.           ],
  108.           "properties": {
  109.             "architecture": "[parameters('architecture')]",
  110.             "hyperVGeneration": "V2",
  111.             "identifier": {
  112.               "offer": "rhcos-gen2",
  113.               "publisher": "RedHat-gen2",
  114.               "sku": "gen2"
  115.             },
  116.             "osState": "Generalized",
  117.             "osType": "Linux"
  118.           },
  119.           "resources": [
  120.             {
  121.               "apiVersion": "2021-10-01",
  122.               "type": "versions",
  123.               "name": "[variables('imageRelease')]",
  124.               "location": "[variables('location')]",
  125.               "dependsOn": [
  126.                 "[variables('imageNameGen2')]"
  127.               ],
  128.               "properties": {
  129.                 "publishingProfile": {
  130.                   "storageAccountType": "Standard_LRS",
  131.                   "targetRegions": [
  132.                     {
  133.                       "name": "[variables('location')]",
  134.                       "regionalReplicaCount": "1"
  135.                     }
  136.                   ]
  137.                 },
  138.                 "storageProfile": {
  139.                   "osDiskImage": {
  140.                     "source": {
  141.                       "id": "[resourceId('Microsoft.Storage/storageAccounts', parameters('storageAccount'))]",
  142.                       "uri": "[parameters('vhdBlobURL')]"
  143.                     }
  144.                   }
  145.                 }
  146.               }
  147.             }
  148.           ]
  149.         }
  150.       ]
  151.     }
  152.   ]
  153. }

Networking requirements for user-provisioned infrastructure

All the Fedora CoreOS (FCOS) machines require networking to be configured in initramfs during boot to fetch their Ignition config files.

Network connectivity requirements

You must configure the network connectivity between machines to allow OKD cluster components to communicate. Each machine must be able to resolve the hostnames of all other machines in the cluster.

This section provides details about the ports that are required.

In connected OKD environments, all nodes are required to have internet access to pull images for platform containers and provide telemetry data to Red Hat.

Table 3. Ports used for all-machine to all-machine communications
ProtocolPortDescription

ICMP

N/A

Network reachability tests

TCP

1936

Metrics

9000-9999

Host level services, including the node exporter on ports 9100-9101 and the Cluster Version Operator on port 9099.

10250-10259

The default ports that Kubernetes reserves

10256

openshift-sdn

UDP

4789

VXLAN

6081

Geneve

9000-9999

Host level services, including the node exporter on ports 9100-9101.

500

IPsec IKE packets

4500

IPsec NAT-T packets

TCP/UDP

30000-32767

Kubernetes node port

ESP

N/A

IPsec Encapsulating Security Payload (ESP)

Table 4. Ports used for all-machine to control plane communications
ProtocolPortDescription

TCP

6443

Kubernetes API

Table 5. Ports used for control plane machine to control plane machine communications
ProtocolPortDescription

TCP

2379-2380

etcd server and peer ports

Creating networking and load balancing components in Azure

You must configure networking and load balancing in Microsoft Azure for your OKD cluster to use. One way to create these components is to modify the provided Azure Resource Manager (ARM) template.

If you do not use the provided ARM template to create your Azure infrastructure, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, you might have to contact Red Hat support with your installation logs.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

  • Create and configure a VNet and associated subnets in Azure.

Procedure

  1. Copy the template from the ARM template for the network and load balancers section of this topic and save it as 03_infra.json in your cluster’s installation directory. This template describes the networking and load balancing objects that your cluster requires.

  2. Create the deployment by using the az CLI:

    1. $ az deployment group create -g ${RESOURCE_GROUP} \
    2.   --template-file "<installation_directory>/03_infra.json" \
    3.   --parameters privateDNSZoneName="${CLUSTER_NAME}.${BASE_DOMAIN}" \ (1)
    4.   --parameters baseName="${INFRA_ID}"(2)
    1The name of the private DNS zone.
    2The base name to be used in resource names; this is usually the cluster’s infrastructure ID.

  3. Create an api DNS record in the public zone for the API public load balancer. The ${BASE_DOMAIN_RESOURCE_GROUP} variable must point to the resource group where the public DNS zone exists.

    1. Export the following variable:

      1. $ export PUBLIC_IP=`az network public-ip list -g ${RESOURCE_GROUP} --query "[?name=='${INFRA_ID}-master-pip'] | [0].ipAddress" -o tsv`

    2. Create the api DNS record in a new public zone:

      1. $ az network dns record-set a add-record -g ${BASE_DOMAIN_RESOURCE_GROUP} -z ${CLUSTER_NAME}.${BASE_DOMAIN} -n api -a ${PUBLIC_IP} --ttl 60

      If you are adding the cluster to an existing public zone, you can create the api DNS record in it instead:

      1. $ az network dns record-set a add-record -g ${BASE_DOMAIN_RESOURCE_GROUP} -z ${BASE_DOMAIN} -n api.${CLUSTER_NAME} -a ${PUBLIC_IP} --ttl 60

ARM template for the network and load balancers

You can use the following Azure Resource Manager (ARM) template to deploy the networking objects and load balancers that you need for your OKD cluster:

03_infra.json ARM template

  1. {
  2.   "$schema" : "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  3.   "contentVersion" : "1.0.0.0",
  4.   "parameters" : {
  5.     "baseName" : {
  6.       "type" : "string",
  7.       "minLength" : 1,
  8.       "metadata" : {
  9.         "description" : "Base name to be used in resource names (usually the cluster's Infra ID)"
  10.       }
  11.     },
  12.     "vnetBaseName": {
  13.       "type": "string",
  14.       "defaultValue": "",
  15.       "metadata" : {
  16.         "description" : "The specific customer vnet's base name (optional)"
  17.       }
  18.     },
  19.     "privateDNSZoneName" : {
  20.       "type" : "string",
  21.       "metadata" : {
  22.         "description" : "Name of the private DNS zone"
  23.       }
  24.     }
  25.   },
  26.   "variables" : {
  27.     "location" : "[resourceGroup().location]",
  28.     "virtualNetworkName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-vnet')]",
  29.     "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  30.     "masterSubnetName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-master-subnet')]",
  31.     "masterSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('masterSubnetName'))]",
  32.     "masterPublicIpAddressName" : "[concat(parameters('baseName'), '-master-pip')]",
  33.     "masterPublicIpAddressID" : "[resourceId('Microsoft.Network/publicIPAddresses', variables('masterPublicIpAddressName'))]",
  34.     "masterLoadBalancerName" : "[parameters('baseName')]",
  35.     "masterLoadBalancerID" : "[resourceId('Microsoft.Network/loadBalancers', variables('masterLoadBalancerName'))]",
  36.     "internalLoadBalancerName" : "[concat(parameters('baseName'), '-internal-lb')]",
  37.     "internalLoadBalancerID" : "[resourceId('Microsoft.Network/loadBalancers', variables('internalLoadBalancerName'))]",
  38.     "skuName": "Standard"
  39.   },
  40.   "resources" : [
  41.     {
  42.       "apiVersion" : "2018-12-01",
  43.       "type" : "Microsoft.Network/publicIPAddresses",
  44.       "name" : "[variables('masterPublicIpAddressName')]",
  45.       "location" : "[variables('location')]",
  46.       "sku": {
  47.         "name": "[variables('skuName')]"
  48.       },
  49.       "properties" : {
  50.         "publicIPAllocationMethod" : "Static",
  51.         "dnsSettings" : {
  52.           "domainNameLabel" : "[variables('masterPublicIpAddressName')]"
  53.         }
  54.       }
  55.     },
  56.     {
  57.       "apiVersion" : "2018-12-01",
  58.       "type" : "Microsoft.Network/loadBalancers",
  59.       "name" : "[variables('masterLoadBalancerName')]",
  60.       "location" : "[variables('location')]",
  61.       "sku": {
  62.         "name": "[variables('skuName')]"
  63.       },
  64.       "dependsOn" : [
  65.         "[concat('Microsoft.Network/publicIPAddresses/', variables('masterPublicIpAddressName'))]"
  66.       ],
  67.       "properties" : {
  68.         "frontendIPConfigurations" : [
  69.           {
  70.             "name" : "public-lb-ip-v4",
  71.             "properties" : {
  72.               "publicIPAddress" : {
  73.                 "id" : "[variables('masterPublicIpAddressID')]"
  74.               }
  75.             }
  76.           }
  77.         ],
  78.         "backendAddressPools" : [
  79.           {
  80.             "name" : "[variables('masterLoadBalancerName')]"
  81.           }
  82.         ],
  83.         "loadBalancingRules" : [
  84.           {
  85.             "name" : "api-internal",
  86.             "properties" : {
  87.               "frontendIPConfiguration" : {
  88.                 "id" :"[concat(variables('masterLoadBalancerID'), '/frontendIPConfigurations/public-lb-ip-v4')]"
  89.               },
  90.               "backendAddressPool" : {
  91.                 "id" : "[concat(variables('masterLoadBalancerID'), '/backendAddressPools/', variables('masterLoadBalancerName'))]"
  92.               },
  93.               "protocol" : "Tcp",
  94.               "loadDistribution" : "Default",
  95.               "idleTimeoutInMinutes" : 30,
  96.               "frontendPort" : 6443,
  97.               "backendPort" : 6443,
  98.               "probe" : {
  99.                 "id" : "[concat(variables('masterLoadBalancerID'), '/probes/api-internal-probe')]"
  100.               }
  101.             }
  102.           }
  103.         ],
  104.         "probes" : [
  105.           {
  106.             "name" : "api-internal-probe",
  107.             "properties" : {
  108.               "protocol" : "Https",
  109.               "port" : 6443,
  110.               "requestPath": "/readyz",
  111.               "intervalInSeconds" : 10,
  112.               "numberOfProbes" : 3
  113.             }
  114.           }
  115.         ]
  116.       }
  117.     },
  118.     {
  119.       "apiVersion" : "2018-12-01",
  120.       "type" : "Microsoft.Network/loadBalancers",
  121.       "name" : "[variables('internalLoadBalancerName')]",
  122.       "location" : "[variables('location')]",
  123.       "sku": {
  124.         "name": "[variables('skuName')]"
  125.       },
  126.       "properties" : {
  127.         "frontendIPConfigurations" : [
  128.           {
  129.             "name" : "internal-lb-ip",
  130.             "properties" : {
  131.               "privateIPAllocationMethod" : "Dynamic",
  132.               "subnet" : {
  133.                 "id" : "[variables('masterSubnetRef')]"
  134.               },
  135.               "privateIPAddressVersion" : "IPv4"
  136.             }
  137.           }
  138.         ],
  139.         "backendAddressPools" : [
  140.           {
  141.             "name" : "internal-lb-backend"
  142.           }
  143.         ],
  144.         "loadBalancingRules" : [
  145.           {
  146.             "name" : "api-internal",
  147.             "properties" : {
  148.               "frontendIPConfiguration" : {
  149.                 "id" : "[concat(variables('internalLoadBalancerID'), '/frontendIPConfigurations/internal-lb-ip')]"
  150.               },
  151.               "frontendPort" : 6443,
  152.               "backendPort" : 6443,
  153.               "enableFloatingIP" : false,
  154.               "idleTimeoutInMinutes" : 30,
  155.               "protocol" : "Tcp",
  156.               "enableTcpReset" : false,
  157.               "loadDistribution" : "Default",
  158.               "backendAddressPool" : {
  159.                 "id" : "[concat(variables('internalLoadBalancerID'), '/backendAddressPools/internal-lb-backend')]"
  160.               },
  161.               "probe" : {
  162.                 "id" : "[concat(variables('internalLoadBalancerID'), '/probes/api-internal-probe')]"
  163.               }
  164.             }
  165.           },
  166.           {
  167.             "name" : "sint",
  168.             "properties" : {
  169.               "frontendIPConfiguration" : {
  170.                 "id" : "[concat(variables('internalLoadBalancerID'), '/frontendIPConfigurations/internal-lb-ip')]"
  171.               },
  172.               "frontendPort" : 22623,
  173.               "backendPort" : 22623,
  174.               "enableFloatingIP" : false,
  175.               "idleTimeoutInMinutes" : 30,
  176.               "protocol" : "Tcp",
  177.               "enableTcpReset" : false,
  178.               "loadDistribution" : "Default",
  179.               "backendAddressPool" : {
  180.                 "id" : "[concat(variables('internalLoadBalancerID'), '/backendAddressPools/internal-lb-backend')]"
  181.               },
  182.               "probe" : {
  183.                 "id" : "[concat(variables('internalLoadBalancerID'), '/probes/sint-probe')]"
  184.               }
  185.             }
  186.           }
  187.         ],
  188.         "probes" : [
  189.           {
  190.             "name" : "api-internal-probe",
  191.             "properties" : {
  192.               "protocol" : "Https",
  193.               "port" : 6443,
  194.               "requestPath": "/readyz",
  195.               "intervalInSeconds" : 10,
  196.               "numberOfProbes" : 3
  197.             }
  198.           },
  199.           {
  200.             "name" : "sint-probe",
  201.             "properties" : {
  202.               "protocol" : "Https",
  203.               "port" : 22623,
  204.               "requestPath": "/healthz",
  205.               "intervalInSeconds" : 10,
  206.               "numberOfProbes" : 3
  207.             }
  208.           }
  209.         ]
  210.       }
  211.     },
  212.     {
  213.       "apiVersion": "2018-09-01",
  214.       "type": "Microsoft.Network/privateDnsZones/A",
  215.       "name": "[concat(parameters('privateDNSZoneName'), '/api')]",
  216.       "location" : "[variables('location')]",
  217.       "dependsOn" : [
  218.         "[concat('Microsoft.Network/loadBalancers/', variables('internalLoadBalancerName'))]"
  219.       ],
  220.       "properties": {
  221.         "ttl": 60,
  222.         "aRecords": [
  223.           {
  224.             "ipv4Address": "[reference(variables('internalLoadBalancerName')).frontendIPConfigurations[0].properties.privateIPAddress]"
  225.           }
  226.         ]
  227.       }
  228.     },
  229.     {
  230.       "apiVersion": "2018-09-01",
  231.       "type": "Microsoft.Network/privateDnsZones/A",
  232.       "name": "[concat(parameters('privateDNSZoneName'), '/api-int')]",
  233.       "location" : "[variables('location')]",
  234.       "dependsOn" : [
  235.         "[concat('Microsoft.Network/loadBalancers/', variables('internalLoadBalancerName'))]"
  236.       ],
  237.       "properties": {
  238.         "ttl": 60,
  239.         "aRecords": [
  240.           {
  241.             "ipv4Address": "[reference(variables('internalLoadBalancerName')).frontendIPConfigurations[0].properties.privateIPAddress]"
  242.           }
  243.         ]
  244.       }
  245.     }
  246.   ]
  247. }

Creating the bootstrap machine in Azure

You must create the bootstrap machine in Microsoft Azure to use during OKD cluster initialization. One way to create this machine is to modify the provided Azure Resource Manager (ARM) template.

If you do not use the provided ARM template to create your bootstrap machine, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, you might have to contact Red Hat support with your installation logs.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

  • Create and configure a VNet and associated subnets in Azure.

  • Create and configure networking and load balancers in Azure.

  • Create control plane and compute roles.

Procedure

  1. Copy the template from the ARM template for the bootstrap machine section of this topic and save it as 04_bootstrap.json in your cluster’s installation directory. This template describes the bootstrap machine that your cluster requires.

  2. Export the bootstrap URL variable:

    1. $ bootstrap_url_expiry=`date -u -d "10 hours" '+%Y-%m-%dT%H:%MZ'`
    1. $ export BOOTSTRAP_URL=`az storage blob generate-sas -c 'files' -n 'bootstrap.ign' --https-only --full-uri --permissions r --expiry $bootstrap_url_expiry --account-name ${CLUSTER_NAME}sa --account-key ${ACCOUNT_KEY} -o tsv`

  3. Export the bootstrap ignition variable:

    1. $ export BOOTSTRAP_IGNITION=`jq -rcnM --arg v "3.2.0" --arg url ${BOOTSTRAP_URL} '{ignition:{version:$v,config:{replace:{source:$url}}}}' | base64 | tr -d '\n'`

  4. Create the deployment by using the az CLI:

    1. $ az deployment group create -g ${RESOURCE_GROUP} \
    2.   --template-file "<installation_directory>/04_bootstrap.json" \
    3.   --parameters bootstrapIgnition="${BOOTSTRAP_IGNITION}" \ (1)
    4.   --parameters baseName="${INFRA_ID}" (2)
    1The bootstrap Ignition content for the bootstrap cluster.
    2The base name to be used in resource names; this is usually the cluster’s infrastructure ID.

ARM template for the bootstrap machine

You can use the following Azure Resource Manager (ARM) template to deploy the bootstrap machine that you need for your OKD cluster:

04_bootstrap.json ARM template

  1. {
  2.   "$schema" : "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  3.   "contentVersion" : "1.0.0.0",
  4.   "parameters" : {
  5.     "baseName" : {
  6.       "type" : "string",
  7.       "minLength" : 1,
  8.       "metadata" : {
  9.         "description" : "Base name to be used in resource names (usually the cluster's Infra ID)"
  10.       }
  11.     },
  12.     "vnetBaseName": {
  13.       "type": "string",
  14.       "defaultValue": "",
  15.       "metadata" : {
  16.         "description" : "The specific customer vnet's base name (optional)"
  17.       }
  18.     },
  19.     "bootstrapIgnition" : {
  20.       "type" : "string",
  21.       "minLength" : 1,
  22.       "metadata" : {
  23.         "description" : "Bootstrap ignition content for the bootstrap cluster"
  24.       }
  25.     },
  26.     "sshKeyData" : {
  27.       "type" : "securestring",
  28.       "defaultValue" : "Unused",
  29.       "metadata" : {
  30.         "description" : "Unused"
  31.       }
  32.     },
  33.     "bootstrapVMSize" : {
  34.       "type" : "string",
  35.       "defaultValue" : "Standard_D4s_v3",
  36.       "metadata" : {
  37.         "description" : "The size of the Bootstrap Virtual Machine"
  38.       }
  39.     },
  40.     "hyperVGen": {
  41.       "type": "string",
  42.       "metadata": {
  43.         "description": "VM generation image to use"
  44.       },
  45.       "defaultValue": "V2",
  46.       "allowedValues": [
  47.         "V1",
  48.         "V2"
  49.       ]
  50.     }
  51.   },
  52.   "variables" : {
  53.     "location" : "[resourceGroup().location]",
  54.     "virtualNetworkName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-vnet')]",
  55.     "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  56.     "masterSubnetName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-master-subnet')]",
  57.     "masterSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('masterSubnetName'))]",
  58.     "masterLoadBalancerName" : "[parameters('baseName')]",
  59.     "internalLoadBalancerName" : "[concat(parameters('baseName'), '-internal-lb')]",
  60.     "sshKeyPath" : "/home/core/.ssh/authorized_keys",
  61.     "identityName" : "[concat(parameters('baseName'), '-identity')]",
  62.     "vmName" : "[concat(parameters('baseName'), '-bootstrap')]",
  63.     "nicName" : "[concat(variables('vmName'), '-nic')]",
  64.     "galleryName": "[concat('gallery_', replace(parameters('baseName'), '-', '_'))]",
  65.     "imageName" : "[concat(parameters('baseName'), if(equals(parameters('hyperVGen'), 'V2'), '-gen2', ''))]",
  66.     "clusterNsgName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-nsg')]",
  67.     "sshPublicIpAddressName" : "[concat(variables('vmName'), '-ssh-pip')]"
  68.   },
  69.   "resources" : [
  70.     {
  71.       "apiVersion" : "2018-12-01",
  72.       "type" : "Microsoft.Network/publicIPAddresses",
  73.       "name" : "[variables('sshPublicIpAddressName')]",
  74.       "location" : "[variables('location')]",
  75.       "sku": {
  76.         "name": "Standard"
  77.       },
  78.       "properties" : {
  79.         "publicIPAllocationMethod" : "Static",
  80.         "dnsSettings" : {
  81.           "domainNameLabel" : "[variables('sshPublicIpAddressName')]"
  82.         }
  83.       }
  84.     },
  85.     {
  86.       "apiVersion" : "2018-06-01",
  87.       "type" : "Microsoft.Network/networkInterfaces",
  88.       "name" : "[variables('nicName')]",
  89.       "location" : "[variables('location')]",
  90.       "dependsOn" : [
  91.         "[resourceId('Microsoft.Network/publicIPAddresses', variables('sshPublicIpAddressName'))]"
  92.       ],
  93.       "properties" : {
  94.         "ipConfigurations" : [
  95.           {
  96.             "name" : "pipConfig",
  97.             "properties" : {
  98.               "privateIPAllocationMethod" : "Dynamic",
  99.               "publicIPAddress": {
  100.                 "id": "[resourceId('Microsoft.Network/publicIPAddresses', variables('sshPublicIpAddressName'))]"
  101.               },
  102.               "subnet" : {
  103.                 "id" : "[variables('masterSubnetRef')]"
  104.               },
  105.               "loadBalancerBackendAddressPools" : [
  106.                 {
  107.                   "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('masterLoadBalancerName'), '/backendAddressPools/', variables('masterLoadBalancerName'))]"
  108.                 },
  109.                 {
  110.                   "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('internalLoadBalancerName'), '/backendAddressPools/internal-lb-backend')]"
  111.                 }
  112.               ]
  113.             }
  114.           }
  115.         ]
  116.       }
  117.     },
  118.     {
  119.       "apiVersion" : "2018-06-01",
  120.       "type" : "Microsoft.Compute/virtualMachines",
  121.       "name" : "[variables('vmName')]",
  122.       "location" : "[variables('location')]",
  123.       "identity" : {
  124.         "type" : "userAssigned",
  125.         "userAssignedIdentities" : {
  126.           "[resourceID('Microsoft.ManagedIdentity/userAssignedIdentities/', variables('identityName'))]" : {}
  127.         }
  128.       },
  129.       "dependsOn" : [
  130.         "[concat('Microsoft.Network/networkInterfaces/', variables('nicName'))]"
  131.       ],
  132.       "properties" : {
  133.         "hardwareProfile" : {
  134.           "vmSize" : "[parameters('bootstrapVMSize')]"
  135.         },
  136.         "osProfile" : {
  137.           "computerName" : "[variables('vmName')]",
  138.           "adminUsername" : "core",
  139.           "adminPassword" : "NotActuallyApplied!",
  140.           "customData" : "[parameters('bootstrapIgnition')]",
  141.           "linuxConfiguration" : {
  142.             "disablePasswordAuthentication" : false
  143.           }
  144.         },
  145.         "storageProfile" : {
  146.           "imageReference": {
  147.             "id": "[resourceId('Microsoft.Compute/galleries/images', variables('galleryName'), variables('imageName'))]"
  148.           },
  149.           "osDisk" : {
  150.             "name": "[concat(variables('vmName'),'_OSDisk')]",
  151.             "osType" : "Linux",
  152.             "createOption" : "FromImage",
  153.             "managedDisk": {
  154.               "storageAccountType": "Premium_LRS"
  155.             },
  156.             "diskSizeGB" : 100
  157.           }
  158.         },
  159.         "networkProfile" : {
  160.           "networkInterfaces" : [
  161.             {
  162.               "id" : "[resourceId('Microsoft.Network/networkInterfaces', variables('nicName'))]"
  163.             }
  164.           ]
  165.         }
  166.       }
  167.     },
  168.     {
  169.       "apiVersion" : "2018-06-01",
  170.       "type": "Microsoft.Network/networkSecurityGroups/securityRules",
  171.       "name" : "[concat(variables('clusterNsgName'), '/bootstrap_ssh_in')]",
  172.       "location" : "[variables('location')]",
  173.       "dependsOn" : [
  174.         "[resourceId('Microsoft.Compute/virtualMachines', variables('vmName'))]"
  175.       ],
  176.       "properties": {
  177.         "protocol" : "Tcp",
  178.         "sourcePortRange" : "*",
  179.         "destinationPortRange" : "22",
  180.         "sourceAddressPrefix" : "*",
  181.         "destinationAddressPrefix" : "*",
  182.         "access" : "Allow",
  183.         "priority" : 100,
  184.         "direction" : "Inbound"
  185.       }
  186.     }
  187.   ]
  188. }

Creating the control plane machines in Azure

You must create the control plane machines in Microsoft Azure for your cluster to use. One way to create these machines is to modify the provided Azure Resource Manager (ARM) template.

By default, Microsoft Azure places control plane machines and compute machines in a pre-set availability zone. You can manually set an availability zone for a compute node or control plane node. To do this, modify a vendor’s Azure Resource Manager (ARM) template by specifying each of your availability zones in the zones parameter of the virtual machine resource.

If you do not use the provided ARM template to create your control plane machines, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, consider contacting Red Hat support with your installation logs.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

  • Create and configure a VNet and associated subnets in Azure.

  • Create and configure networking and load balancers in Azure.

  • Create control plane and compute roles.

  • Create the bootstrap machine.

Procedure

  1. Copy the template from the ARM template for control plane machines section of this topic and save it as 05_masters.json in your cluster’s installation directory. This template describes the control plane machines that your cluster requires.

  2. Export the following variable needed by the control plane machine deployment:

    1. $ export MASTER_IGNITION=`cat <installation_directory>/master.ign | base64 | tr -d '\n'`

  3. Create the deployment by using the az CLI:

    1. $ az deployment group create -g ${RESOURCE_GROUP} \
    2.   --template-file "<installation_directory>/05_masters.json" \
    3.   --parameters masterIgnition="${MASTER_IGNITION}" \ (1)
    4.   --parameters baseName="${INFRA_ID}" (2)
    1The Ignition content for the control plane nodes.
    2The base name to be used in resource names; this is usually the cluster’s infrastructure ID.

ARM template for control plane machines

You can use the following Azure Resource Manager (ARM) template to deploy the control plane machines that you need for your OKD cluster:

05_masters.json ARM template

  1. {
  2.   "$schema" : "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  3.   "contentVersion" : "1.0.0.0",
  4.   "parameters" : {
  5.     "baseName" : {
  6.       "type" : "string",
  7.       "minLength" : 1,
  8.       "metadata" : {
  9.         "description" : "Base name to be used in resource names (usually the cluster's Infra ID)"
  10.       }
  11.     },
  12.     "vnetBaseName": {
  13.       "type": "string",
  14.       "defaultValue": "",
  15.       "metadata" : {
  16.         "description" : "The specific customer vnet's base name (optional)"
  17.       }
  18.     },
  19.     "masterIgnition" : {
  20.       "type" : "string",
  21.       "metadata" : {
  22.         "description" : "Ignition content for the master nodes"
  23.       }
  24.     },
  25.     "numberOfMasters" : {
  26.       "type" : "int",
  27.       "defaultValue" : 3,
  28.       "minValue" : 2,
  29.       "maxValue" : 30,
  30.       "metadata" : {
  31.         "description" : "Number of OpenShift masters to deploy"
  32.       }
  33.     },
  34.     "sshKeyData" : {
  35.       "type" : "securestring",
  36.       "defaultValue" : "Unused",
  37.       "metadata" : {
  38.         "description" : "Unused"
  39.       }
  40.     },
  41.     "privateDNSZoneName" : {
  42.       "type" : "string",
  43.       "defaultValue" : "",
  44.       "metadata" : {
  45.         "description" : "unused"
  46.       }
  47.     },
  48.     "masterVMSize" : {
  49.       "type" : "string",
  50.       "defaultValue" : "Standard_D8s_v3",
  51.       "metadata" : {
  52.         "description" : "The size of the Master Virtual Machines"
  53.       }
  54.     },
  55.     "diskSizeGB" : {
  56.       "type" : "int",
  57.       "defaultValue" : 1024,
  58.       "metadata" : {
  59.         "description" : "Size of the Master VM OS disk, in GB"
  60.       }
  61.     },
  62.     "hyperVGen": {
  63.       "type": "string",
  64.       "metadata": {
  65.         "description": "VM generation image to use"
  66.       },
  67.       "defaultValue": "V2",
  68.       "allowedValues": [
  69.         "V1",
  70.         "V2"
  71.       ]
  72.     }
  73.   },
  74.   "variables" : {
  75.     "location" : "[resourceGroup().location]",
  76.     "virtualNetworkName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-vnet')]",
  77.     "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  78.     "masterSubnetName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-master-subnet')]",
  79.     "masterSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('masterSubnetName'))]",
  80.     "masterLoadBalancerName" : "[parameters('baseName')]",
  81.     "internalLoadBalancerName" : "[concat(parameters('baseName'), '-internal-lb')]",
  82.     "sshKeyPath" : "/home/core/.ssh/authorized_keys",
  83.     "identityName" : "[concat(parameters('baseName'), '-identity')]",
  84.     "galleryName": "[concat('gallery_', replace(parameters('baseName'), '-', '_'))]",
  85.     "imageName" : "[concat(parameters('baseName'), if(equals(parameters('hyperVGen'), 'V2'), '-gen2', ''))]",
  86.     "copy" : [
  87.       {
  88.         "name" : "vmNames",
  89.         "count" :  "[parameters('numberOfMasters')]",
  90.         "input" : "[concat(parameters('baseName'), '-master-', copyIndex('vmNames'))]"
  91.       }
  92.     ]
  93.   },
  94.   "resources" : [
  95.     {
  96.       "apiVersion" : "2018-06-01",
  97.       "type" : "Microsoft.Network/networkInterfaces",
  98.       "copy" : {
  99.         "name" : "nicCopy",
  100.         "count" : "[length(variables('vmNames'))]"
  101.       },
  102.       "name" : "[concat(variables('vmNames')[copyIndex()], '-nic')]",
  103.       "location" : "[variables('location')]",
  104.       "properties" : {
  105.         "ipConfigurations" : [
  106.           {
  107.             "name" : "pipConfig",
  108.             "properties" : {
  109.               "privateIPAllocationMethod" : "Dynamic",
  110.               "subnet" : {
  111.                 "id" : "[variables('masterSubnetRef')]"
  112.               },
  113.               "loadBalancerBackendAddressPools" : [
  114.                 {
  115.                   "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('masterLoadBalancerName'), '/backendAddressPools/', variables('masterLoadBalancerName'))]"
  116.                 },
  117.                 {
  118.                   "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('internalLoadBalancerName'), '/backendAddressPools/internal-lb-backend')]"
  119.                 }
  120.               ]
  121.             }
  122.           }
  123.         ]
  124.       }
  125.     },
  126.     {
  127.       "apiVersion" : "2018-06-01",
  128.       "type" : "Microsoft.Compute/virtualMachines",
  129.       "copy" : {
  130.         "name" : "vmCopy",
  131.         "count" : "[length(variables('vmNames'))]"
  132.       },
  133.       "name" : "[variables('vmNames')[copyIndex()]]",
  134.       "location" : "[variables('location')]",
  135.       "identity" : {
  136.         "type" : "userAssigned",
  137.         "userAssignedIdentities" : {
  138.           "[resourceID('Microsoft.ManagedIdentity/userAssignedIdentities/', variables('identityName'))]" : {}
  139.         }
  140.       },
  141.       "dependsOn" : [
  142.         "[concat('Microsoft.Network/networkInterfaces/', concat(variables('vmNames')[copyIndex()], '-nic'))]"
  143.       ],
  144.       "properties" : {
  145.         "hardwareProfile" : {
  146.           "vmSize" : "[parameters('masterVMSize')]"
  147.         },
  148.         "osProfile" : {
  149.           "computerName" : "[variables('vmNames')[copyIndex()]]",
  150.           "adminUsername" : "core",
  151.           "adminPassword" : "NotActuallyApplied!",
  152.           "customData" : "[parameters('masterIgnition')]",
  153.           "linuxConfiguration" : {
  154.             "disablePasswordAuthentication" : false
  155.           }
  156.         },
  157.         "storageProfile" : {
  158.           "imageReference": {
  159.             "id": "[resourceId('Microsoft.Compute/galleries/images', variables('galleryName'), variables('imageName'))]"
  160.           },
  161.           "osDisk" : {
  162.             "name": "[concat(variables('vmNames')[copyIndex()], '_OSDisk')]",
  163.             "osType" : "Linux",
  164.             "createOption" : "FromImage",
  165.             "caching": "ReadOnly",
  166.             "writeAcceleratorEnabled": false,
  167.             "managedDisk": {
  168.               "storageAccountType": "Premium_LRS"
  169.             },
  170.             "diskSizeGB" : "[parameters('diskSizeGB')]"
  171.           }
  172.         },
  173.         "networkProfile" : {
  174.           "networkInterfaces" : [
  175.             {
  176.               "id" : "[resourceId('Microsoft.Network/networkInterfaces', concat(variables('vmNames')[copyIndex()], '-nic'))]",
  177.               "properties": {
  178.                 "primary": false
  179.               }
  180.             }
  181.           ]
  182.         }
  183.       }
  184.     }
  185.   ]
  186. }

Wait for bootstrap completion and remove bootstrap resources in Azure

After you create all of the required infrastructure in Microsoft Azure, wait for the bootstrap process to complete on the machines that you provisioned by using the Ignition config files that you generated with the installation program.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

  • Create and configure a VNet and associated subnets in Azure.

  • Create and configure networking and load balancers in Azure.

  • Create control plane and compute roles.

  • Create the bootstrap machine.

  • Create the control plane machines.

Procedure

  1. Change to the directory that contains the installation program and run the following command:

    1. $ ./openshift-install wait-for bootstrap-complete --dir <installation_directory> \ (1)
    2.     --log-level info (2)
    1For <installation_directory>, specify the path to the directory that you stored the installation files in.
    2To view different installation details, specify warn, debug, or error instead of info.

    If the command exits without a FATAL warning, your production control plane has initialized.

  2. Delete the bootstrap resources:

    1. $ az network nsg rule delete -g ${RESOURCE_GROUP} --nsg-name ${INFRA_ID}-nsg --name bootstrap_ssh_in
    2. $ az vm stop -g ${RESOURCE_GROUP} --name ${INFRA_ID}-bootstrap
    3. $ az vm deallocate -g ${RESOURCE_GROUP} --name ${INFRA_ID}-bootstrap
    4. $ az vm delete -g ${RESOURCE_GROUP} --name ${INFRA_ID}-bootstrap --yes
    5. $ az disk delete -g ${RESOURCE_GROUP} --name ${INFRA_ID}-bootstrap_OSDisk --no-wait --yes
    6. $ az network nic delete -g ${RESOURCE_GROUP} --name ${INFRA_ID}-bootstrap-nic --no-wait
    7. $ az storage blob delete --account-key ${ACCOUNT_KEY} --account-name ${CLUSTER_NAME}sa --container-name files --name bootstrap.ign
    8. $ az network public-ip delete -g ${RESOURCE_GROUP} --name ${INFRA_ID}-bootstrap-ssh-pip

If you do not delete the bootstrap server, installation may not succeed due to API traffic being routed to the bootstrap server.

Creating additional worker machines in Azure

You can create worker machines in Microsoft Azure for your cluster to use by launching individual instances discretely or by automated processes outside the cluster, such as auto scaling groups. You can also take advantage of the built-in cluster scaling mechanisms and the machine API in OKD.

In this example, you manually launch one instance by using the Azure Resource Manager (ARM) template. Additional instances can be launched by including additional resources of type 06_workers.json in the file.

By default, Microsoft Azure places control plane machines and compute machines in a pre-set availability zone. You can manually set an availability zone for a compute node or control plane node. To do this, modify a vendor’s ARM template by specifying each of your availability zones in the zones parameter of the virtual machine resource.

If you do not use the provided ARM template to create your control plane machines, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, consider contacting Red Hat support with your installation logs.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

  • Create and configure a VNet and associated subnets in Azure.

  • Create and configure networking and load balancers in Azure.

  • Create control plane and compute roles.

  • Create the bootstrap machine.

  • Create the control plane machines.

Procedure

  1. Copy the template from the ARM template for worker machines section of this topic and save it as 06_workers.json in your cluster’s installation directory. This template describes the worker machines that your cluster requires.

  2. Export the following variable needed by the worker machine deployment:

    1. $ export WORKER_IGNITION=`cat <installation_directory>/worker.ign | base64 | tr -d '\n'`

  3. Create the deployment by using the az CLI:

    1. $ az deployment group create -g ${RESOURCE_GROUP} \
    2.   --template-file "<installation_directory>/06_workers.json" \
    3.   --parameters workerIgnition="${WORKER_IGNITION}" \ (1)
    4.   --parameters baseName="${INFRA_ID}" (2)
    1The Ignition content for the worker nodes.
    2The base name to be used in resource names; this is usually the cluster’s infrastructure ID.

ARM template for worker machines

You can use the following Azure Resource Manager (ARM) template to deploy the worker machines that you need for your OKD cluster:

06_workers.json ARM template

  1. {
  2.   "$schema" : "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  3.   "contentVersion" : "1.0.0.0",
  4.   "parameters" : {
  5.     "baseName" : {
  6.       "type" : "string",
  7.       "minLength" : 1,
  8.       "metadata" : {
  9.         "description" : "Base name to be used in resource names (usually the cluster's Infra ID)"
  10.       }
  11.     },
  12.     "vnetBaseName": {
  13.       "type": "string",
  14.       "defaultValue": "",
  15.       "metadata" : {
  16.         "description" : "The specific customer vnet's base name (optional)"
  17.       }
  18.     },
  19.     "workerIgnition" : {
  20.       "type" : "string",
  21.       "metadata" : {
  22.         "description" : "Ignition content for the worker nodes"
  23.       }
  24.     },
  25.     "numberOfNodes" : {
  26.       "type" : "int",
  27.       "defaultValue" : 3,
  28.       "minValue" : 2,
  29.       "maxValue" : 30,
  30.       "metadata" : {
  31.         "description" : "Number of OpenShift compute nodes to deploy"
  32.       }
  33.     },
  34.     "sshKeyData" : {
  35.       "type" : "securestring",
  36.       "defaultValue" : "Unused",
  37.       "metadata" : {
  38.         "description" : "Unused"
  39.       }
  40.     },
  41.     "nodeVMSize" : {
  42.       "type" : "string",
  43.       "defaultValue" : "Standard_D4s_v3",
  44.       "metadata" : {
  45.         "description" : "The size of the each Node Virtual Machine"
  46.       }
  47.     },
  48.     "hyperVGen": {
  49.       "type": "string",
  50.       "metadata": {
  51.         "description": "VM generation image to use"
  52.       },
  53.       "defaultValue": "V2",
  54.       "allowedValues": [
  55.         "V1",
  56.         "V2"
  57.       ]
  58.     }
  59.   },
  60.   "variables" : {
  61.     "location" : "[resourceGroup().location]",
  62.     "virtualNetworkName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-vnet')]",
  63.     "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  64.     "nodeSubnetName" : "[concat(if(not(empty(parameters('vnetBaseName'))), parameters('vnetBaseName'), parameters('baseName')), '-worker-subnet')]",
  65.     "nodeSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('nodeSubnetName'))]",
  66.     "infraLoadBalancerName" : "[parameters('baseName')]",
  67.     "sshKeyPath" : "/home/capi/.ssh/authorized_keys",
  68.     "identityName" : "[concat(parameters('baseName'), '-identity')]",
  69.     "galleryName": "[concat('gallery_', replace(parameters('baseName'), '-', '_'))]",
  70.     "imageName" : "[concat(parameters('baseName'), if(equals(parameters('hyperVGen'), 'V2'), '-gen2', ''))]",
  71.     "copy" : [
  72.       {
  73.         "name" : "vmNames",
  74.         "count" :  "[parameters('numberOfNodes')]",
  75.         "input" : "[concat(parameters('baseName'), '-worker-', variables('location'), '-', copyIndex('vmNames', 1))]"
  76.       }
  77.     ]
  78.   },
  79.   "resources" : [
  80.     {
  81.       "apiVersion" : "2019-05-01",
  82.       "name" : "[concat('node', copyIndex())]",
  83.       "type" : "Microsoft.Resources/deployments",
  84.       "copy" : {
  85.         "name" : "nodeCopy",
  86.         "count" : "[length(variables('vmNames'))]"
  87.       },
  88.       "properties" : {
  89.         "mode" : "Incremental",
  90.         "template" : {
  91.           "$schema" : "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  92.           "contentVersion" : "1.0.0.0",
  93.           "resources" : [
  94.             {
  95.               "apiVersion" : "2018-06-01",
  96.               "type" : "Microsoft.Network/networkInterfaces",
  97.               "name" : "[concat(variables('vmNames')[copyIndex()], '-nic')]",
  98.               "location" : "[variables('location')]",
  99.               "properties" : {
  100.                 "ipConfigurations" : [
  101.                   {
  102.                     "name" : "pipConfig",
  103.                     "properties" : {
  104.                       "privateIPAllocationMethod" : "Dynamic",
  105.                       "subnet" : {
  106.                         "id" : "[variables('nodeSubnetRef')]"
  107.                       }
  108.                     }
  109.                   }
  110.                 ]
  111.               }
  112.             },
  113.             {
  114.               "apiVersion" : "2018-06-01",
  115.               "type" : "Microsoft.Compute/virtualMachines",
  116.               "name" : "[variables('vmNames')[copyIndex()]]",
  117.               "location" : "[variables('location')]",
  118.               "tags" : {
  119.                 "kubernetes.io-cluster-ffranzupi": "owned"
  120.               },
  121.               "identity" : {
  122.                 "type" : "userAssigned",
  123.                 "userAssignedIdentities" : {
  124.                   "[resourceID('Microsoft.ManagedIdentity/userAssignedIdentities/', variables('identityName'))]" : {}
  125.                 }
  126.               },
  127.               "dependsOn" : [
  128.                 "[concat('Microsoft.Network/networkInterfaces/', concat(variables('vmNames')[copyIndex()], '-nic'))]"
  129.               ],
  130.               "properties" : {
  131.                 "hardwareProfile" : {
  132.                   "vmSize" : "[parameters('nodeVMSize')]"
  133.                 },
  134.                 "osProfile" : {
  135.                   "computerName" : "[variables('vmNames')[copyIndex()]]",
  136.                   "adminUsername" : "capi",
  137.                   "adminPassword" : "NotActuallyApplied!",
  138.                   "customData" : "[parameters('workerIgnition')]",
  139.                   "linuxConfiguration" : {
  140.                     "disablePasswordAuthentication" : false
  141.                   }
  142.                 },
  143.                 "storageProfile" : {
  144.                   "imageReference": {
  145.                     "id": "[resourceId('Microsoft.Compute/galleries/images', variables('galleryName'), variables('imageName'))]"
  146.                   },
  147.                   "osDisk" : {
  148.                     "name": "[concat(variables('vmNames')[copyIndex()],'_OSDisk')]",
  149.                     "osType" : "Linux",
  150.                     "createOption" : "FromImage",
  151.                     "managedDisk": {
  152.                       "storageAccountType": "Premium_LRS"
  153.                     },
  154.                     "diskSizeGB": 128
  155.                   }
  156.                 },
  157.                 "networkProfile" : {
  158.                   "networkInterfaces" : [
  159.                     {
  160.                       "id" : "[resourceId('Microsoft.Network/networkInterfaces', concat(variables('vmNames')[copyIndex()], '-nic'))]",
  161.                       "properties": {
  162.                         "primary": true
  163.                       }
  164.                     }
  165.                   ]
  166.                 }
  167.               }
  168.             }
  169.           ]
  170.         }
  171.       }
  172.     }
  173.   ]
  174. }

Installing the OpenShift CLI by downloading the binary

You can install the OpenShift CLI (oc) to interact with OKD from a command-line interface. You can install oc on Linux, Windows, or macOS.

If you installed an earlier version of oc, you cannot use it to complete all of the commands in OKD 4.14. Download and install the new version of oc.

Installing the OpenShift CLI on Linux

You can install the OpenShift CLI (oc) binary on Linux by using the following procedure.

Procedure

  1. Navigate to https://mirror.openshift.com/pub/openshift-v4/clients/oc/latest/ and choose the folder for your operating system and architecture.

  2. Download oc.tar.gz.

  3. Unpack the archive:

    1. $ tar xvf <file>

  4. Place the oc binary in a directory that is on your PATH.

    To check your PATH, execute the following command:

    1. $ echo $PATH

After you install the OpenShift CLI, it is available using the oc command:

  1. $ oc <command>

Installing the OpenShift CLI on Windows

You can install the OpenShift CLI (oc) binary on Windows by using the following procedure.

Procedure

  1. Navigate to https://mirror.openshift.com/pub/openshift-v4/clients/oc/latest/ and choose the folder for your operating system and architecture.

  2. Download oc.zip.

  3. Unzip the archive with a ZIP program.

  4. Move the oc binary to a directory that is on your PATH.

    To check your PATH, open the command prompt and execute the following command:

    1. C:\> path

After you install the OpenShift CLI, it is available using the oc command:

  1. C:\> oc <command>

Installing the OpenShift CLI on macOS

You can install the OpenShift CLI (oc) binary on macOS by using the following procedure.

Procedure

  1. Navigate to https://mirror.openshift.com/pub/openshift-v4/clients/oc/latest/ and choose the folder for your operating system and architecture.

  2. Download oc.tar.gz.

  3. Unpack and unzip the archive.

  4. Move the oc binary to a directory on your PATH.

    To check your PATH, open a terminal and execute the following command:

    1. $ echo $PATH

After you install the OpenShift CLI, it is available using the oc command:

  1. $ oc <command>

Logging in to the cluster by using the CLI

You can log in to your cluster as a default system user by exporting the cluster kubeconfig file. The kubeconfig file contains information about the cluster that is used by the CLI to connect a client to the correct cluster and API server. The file is specific to a cluster and is created during OKD installation.

Prerequisites

  • You deployed an OKD cluster.

  • You installed the oc CLI.

Procedure

  1. Export the kubeadmin credentials:

    1. $ export KUBECONFIG=<installation_directory>/auth/kubeconfig (1)
    1For <installation_directory>, specify the path to the directory that you stored the installation files in.

  2. Verify you can run oc commands successfully using the exported configuration:

    1. $ oc whoami

    Example output

    1. system:admin

Approving the certificate signing requests for your machines

When you add machines to a cluster, two pending certificate signing requests (CSRs) are generated for each machine that you added. You must confirm that these CSRs are approved or, if necessary, approve them yourself. The client requests must be approved first, followed by the server requests.

Prerequisites

  • You added machines to your cluster.

Procedure

  1. Confirm that the cluster recognizes the machines:

    1. $ oc get nodes

    Example output

    1. NAME      STATUS    ROLES   AGE  VERSION
    2. master-0  Ready     master  63m  v1.27.3
    3. master-1  Ready     master  63m  v1.27.3
    4. master-2  Ready     master  64m  v1.27.3

    The output lists all of the machines that you created.

    The preceding output might not include the compute nodes, also known as worker nodes, until some CSRs are approved.

  2. Review the pending CSRs and ensure that you see the client requests with the Pending or Approved status for each machine that you added to the cluster:

    1. $ oc get csr

    Example output

    1. NAME        AGE     REQUESTOR                                                                   CONDITION
    2. csr-8b2br   15m     system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   Pending
    3. csr-8vnps   15m     system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   Pending
    4. ...

    In this example, two machines are joining the cluster. You might see more approved CSRs in the list.

  3. If the CSRs were not approved, after all of the pending CSRs for the machines you added are in Pending status, approve the CSRs for your cluster machines:

    Because the CSRs rotate automatically, approve your CSRs within an hour of adding the machines to the cluster. If you do not approve them within an hour, the certificates will rotate, and more than two certificates will be present for each node. You must approve all of these certificates. After the client CSR is approved, the Kubelet creates a secondary CSR for the serving certificate, which requires manual approval. Then, subsequent serving certificate renewal requests are automatically approved by the machine-approver if the Kubelet requests a new certificate with identical parameters.

    For clusters running on platforms that are not machine API enabled, such as bare metal and other user-provisioned infrastructure, you must implement a method of automatically approving the kubelet serving certificate requests (CSRs). If a request is not approved, then the oc exec, oc rsh, and oc logs commands cannot succeed, because a serving certificate is required when the API server connects to the kubelet. Any operation that contacts the Kubelet endpoint requires this certificate approval to be in place. The method must watch for new CSRs, confirm that the CSR was submitted by the node-bootstrapper service account in the system:node or system:admin groups, and confirm the identity of the node.

    • To approve them individually, run the following command for each valid CSR:

      1. $ oc adm certificate approve <csr_name> (1)
      1<csr_name> is the name of a CSR from the list of current CSRs.

    • To approve all pending CSRs, run the following command:

      1. $ oc get csr -o go-template='{{range .items}}{{if not .status}}{{.metadata.name}}{{"\n"}}{{end}}{{end}}' | xargs --no-run-if-empty oc adm certificate approve

      Some Operators might not become available until some CSRs are approved.

  4. Now that your client requests are approved, you must review the server requests for each machine that you added to the cluster:

    1. $ oc get csr

    Example output

    1. NAME        AGE     REQUESTOR                                                                   CONDITION
    2. csr-bfd72   5m26s   system:node:ip-10-0-50-126.us-east-2.compute.internal                       Pending
    3. csr-c57lv   5m26s   system:node:ip-10-0-95-157.us-east-2.compute.internal                       Pending
    4. ...

  5. If the remaining CSRs are not approved, and are in the Pending status, approve the CSRs for your cluster machines:

    • To approve them individually, run the following command for each valid CSR:

      1. $ oc adm certificate approve <csr_name> (1)
      1<csr_name> is the name of a CSR from the list of current CSRs.

    • To approve all pending CSRs, run the following command:

      1. $ oc get csr -o go-template='{{range .items}}{{if not .status}}{{.metadata.name}}{{"\n"}}{{end}}{{end}}' | xargs oc adm certificate approve

  6. After all client and server CSRs have been approved, the machines have the Ready status. Verify this by running the following command:

    1. $ oc get nodes

    Example output

    1. NAME      STATUS    ROLES   AGE  VERSION
    2. master-0  Ready     master  73m  v1.27.3
    3. master-1  Ready     master  73m  v1.27.3
    4. master-2  Ready     master  74m  v1.27.3
    5. worker-0  Ready     worker  11m  v1.27.3
    6. worker-1  Ready     worker  11m  v1.27.3

    It can take a few minutes after approval of the server CSRs for the machines to transition to the Ready status.

Additional information

Adding the Ingress DNS records

If you removed the DNS Zone configuration when creating Kubernetes manifests and generating Ignition configs, you must manually create DNS records that point at the Ingress load balancer. You can create either a wildcard *.apps.{baseDomain}. or specific records. You can use A, CNAME, and other records per your requirements.

Prerequisites

  • You deployed an OKD cluster on Microsoft Azure by using infrastructure that you provisioned.

  • Install the OpenShift CLI (oc).

  • Install or update the Azure CLI.

Procedure

  1. Confirm the Ingress router has created a load balancer and populated the EXTERNAL-IP field:

    1. $ oc -n openshift-ingress get service router-default

    Example output

    1. NAME             TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                      AGE
    2. router-default   LoadBalancer   172.30.20.10   35.130.120.110   80:32288/TCP,443:31215/TCP   20

  2. Export the Ingress router IP as a variable:

    1. $ export PUBLIC_IP_ROUTER=`oc -n openshift-ingress get service router-default --no-headers | awk '{print $4}'`

  3. Add a *.apps record to the public DNS zone.

    1. If you are adding this cluster to a new public zone, run:

      1. $ az network dns record-set a add-record -g ${BASE_DOMAIN_RESOURCE_GROUP} -z ${CLUSTER_NAME}.${BASE_DOMAIN} -n *.apps -a ${PUBLIC_IP_ROUTER} --ttl 300

    2. If you are adding this cluster to an already existing public zone, run:

      1. $ az network dns record-set a add-record -g ${BASE_DOMAIN_RESOURCE_GROUP} -z ${BASE_DOMAIN} -n *.apps.${CLUSTER_NAME} -a ${PUBLIC_IP_ROUTER} --ttl 300

  4. Add a *.apps record to the private DNS zone:

    1. Create a *.apps record by using the following command:

      1. $ az network private-dns record-set a create -g ${RESOURCE_GROUP} -z ${CLUSTER_NAME}.${BASE_DOMAIN} -n *.apps --ttl 300

    2. Add the *.apps record to the private DNS zone by using the following command:

      1. $ az network private-dns record-set a add-record -g ${RESOURCE_GROUP} -z ${CLUSTER_NAME}.${BASE_DOMAIN} -n *.apps -a ${PUBLIC_IP_ROUTER}

If you prefer to add explicit domains instead of using a wildcard, you can create entries for each of the cluster’s current routes:

  1. $ oc get --all-namespaces -o jsonpath='{range .items[*]}{range .status.ingress[*]}{.host}{"\n"}{end}{end}' routes

Example output

  1. oauth-openshift.apps.cluster.basedomain.com
  2. console-openshift-console.apps.cluster.basedomain.com
  3. downloads-openshift-console.apps.cluster.basedomain.com
  4. alertmanager-main-openshift-monitoring.apps.cluster.basedomain.com
  5. prometheus-k8s-openshift-monitoring.apps.cluster.basedomain.com

Completing an Azure installation on user-provisioned infrastructure

After you start the OKD installation on Microsoft Azure user-provisioned infrastructure, you can monitor the cluster events until the cluster is ready.

Prerequisites

  • Deploy the bootstrap machine for an OKD cluster on user-provisioned Azure infrastructure.

  • Install the oc CLI and log in.

Procedure

  • Complete the cluster installation:

    1. $ ./openshift-install --dir <installation_directory> wait-for install-complete (1)

    Example output

    1. INFO Waiting up to 30m0s for the cluster to initialize...
    1For <installation_directory>, specify the path to the directory that you stored the installation files in.

    • The Ignition config files that the installation program generates contain certificates that expire after 24 hours, which are then renewed at that time. If the cluster is shut down before renewing the certificates and the cluster is later restarted after the 24 hours have elapsed, the cluster automatically recovers the expired certificates. The exception is that you must manually approve the pending node-bootstrapper certificate signing requests (CSRs) to recover kubelet certificates. See the documentation for Recovering from expired control plane certificates for more information.

    • It is recommended that you use Ignition config files within 12 hours after they are generated because the 24-hour certificate rotates from 16 to 22 hours after the cluster is installed. By using the Ignition config files within 12 hours, you can avoid installation failure if the certificate update runs during installation.

Additional resources