Installing a cluster on Azure Stack Hub using ARM templates

In OKD version 4.12, you can install a cluster on Microsoft Azure Stack Hub 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; the templates are just an example.

Prerequisites

Configuring your Azure Stack Hub project

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

All Azure Stack Hub 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 Stack Hub restricts, see Resolve reserved resource name errors in the Azure documentation.

Azure Stack Hub account limits

The OKD cluster uses a number of Microsoft Azure Stack Hub components, and the default Quota types in Azure Stack Hub affect your ability to install OKD clusters.

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

ComponentNumber of components required by defaultDescription

vCPU

56

A default cluster requires 56 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, control plane, and worker machines use Standard_DS4_v2 virtual machines, which use 8 vCPUs, a default cluster requires 56 vCPUs. The bootstrap node VM 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.

VNet

1

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

Network interfaces

7

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

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

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

2

The public load balancer 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.

Configuring a DNS zone in Azure Stack Hub

To successfully install OKD on Azure Stack Hub, you must create DNS records in an Azure Stack Hub DNS zone. The DNS zone must be authoritative for the domain. To delegate a registrar’s DNS zone to Azure Stack Hub, see Microsoft’s documentation for Azure Stack Hub datacenter DNS integration.

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

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 Stack Hub roles

Your Microsoft Azure Stack Hub account must have the following roles for the subscription that you use:

  • Owner

To set roles on the Azure portal, see the Manage access to resources in Azure Stack Hub with role-based access control in the Microsoft documentation.

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.

Procedure

  1. Register your environment:

    1. $ az cloud register -n AzureStackCloud --endpoint-resource-manager <endpoint> (1)
    1Specify the Azure Resource Manager endpoint, https://management.&lt;region&gt;.&lt;fqdn&gt;/.

    See the Microsoft documentation for details.

  2. Set the active environment:

    1. $ az cloud set -n AzureStackCloud
  3. Update your environment configuration to use the specific API version for Azure Stack Hub:

    1. $ az cloud update --profile 2019-03-01-hybrid
  4. Log in to the Azure CLI:

    1. $ az login

    If you are in a multitenant environment, you must also supply the tenant ID.

  5. 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": AzureStackCloud",
      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": AzureStackCloud",
      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": AzureStackCloud",
      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. }
  6. Record the tenantId and id parameter values from the output. You need these values during the OKD installation.

  7. Create the service principal for your account:

    1. $ az ad sp create-for-rbac --role Contributor --name <service_principal> \ (1)
    2. --scopes /subscriptions/<subscription_id> (2)
    1Specify the service principal name.
    2Specify 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. }
  8. Record the values of the appId and password parameters from the previous output. You need these values during OKD installation.

Additional resources

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 FIPS Validated / Modules in Process cryptographic libraries on the x86_64 architecture, 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.

Creating the installation files for Azure Stack Hub

To install OKD on Microsoft Azure Stack Hub 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 manually create the install-config.yaml file, and then generate and customize the 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.

Manually creating the installation configuration file

Prerequisites

  • You have an SSH public key on your local machine to provide to the installation program. The key will be used for SSH authentication onto your cluster nodes for debugging and disaster recovery.

  • You have obtained the OKD installation program and the pull secret for your cluster.

Procedure

  1. Create an installation directory to store your required installation assets in:

    1. $ mkdir <installation_directory>

    You must create a directory. Some installation assets, like bootstrap X.509 certificates have short expiration intervals, so 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.

  2. Customize the sample install-config.yaml file template that is provided and save it in the <installation_directory>.

    You must name this configuration file install-config.yaml.

    Make the following modifications for Azure Stack Hub:

    1. Set the replicas parameter to 0 for the compute pool:

      1. compute:
      2. - hyperthreading: Enabled
      3. name: worker
      4. platform: {}
      5. replicas: 0 (1)
      1Set to 0.

      The compute machines will be provisioned manually later.

    2. Update the platform.azure section of the install-config.yaml file to configure your Azure Stack Hub configuration:

      1. platform:
      2. azure:
      3. armEndpoint: <azurestack_arm_endpoint> (1)
      4. baseDomainResourceGroupName: <resource_group> (2)
      5. cloudName: AzureStackCloud (3)
      6. region: <azurestack_region> (4)
      1Specify the Azure Resource Manager endpoint of your Azure Stack Hub environment, like https://management.local.azurestack.external.
      2Specify the name of the resource group that contains the DNS zone for your base domain.
      3Specify the Azure Stack Hub environment, which is used to configure the Azure SDK with the appropriate Azure API endpoints.
      4Specify the name of your Azure Stack Hub region.
  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 next step of the installation process. You must back it up now.

Sample customized install-config.yaml file for Azure Stack Hub

You can customize the install-config.yaml file to specify more details about your OKD cluster’s platform or modify the values of the required parameters.

This sample YAML file is provided for reference only. Use it as a resource to enter parameter values into the installation configuration file that you created manually.

  1. apiVersion: v1
  2. baseDomain: example.com
  3. controlPlane: (1)
  4. name: master
  5. platform:
  6. azure:
  7. osDisk:
  8. diskSizeGB: 1024 (2)
  9. diskType: premium_LRS
  10. replicas: 3
  11. compute: (1)
  12. - name: worker
  13. platform:
  14. azure:
  15. osDisk:
  16. diskSizeGB: 512 (2)
  17. diskType: premium_LRS
  18. replicas: 0
  19. metadata:
  20. name: test-cluster (3)
  21. networking:
  22. clusterNetwork:
  23. - cidr: 10.128.0.0/14
  24. hostPrefix: 23
  25. machineNetwork:
  26. - cidr: 10.0.0.0/16
  27. networkType: OVNKubernetes (4)
  28. serviceNetwork:
  29. - 172.30.0.0/16
  30. platform:
  31. azure:
  32. armEndpoint: azurestack_arm_endpoint (5)
  33. baseDomainResourceGroupName: resource_group (6)
  34. region: azure_stack_local_region (7)
  35. resourceGroupName: existing_resource_group (8)
  36. outboundType: Loadbalancer
  37. cloudName: AzureStackCloud (9)
  38. pullSecret: '{"auths": ...}' (10)
  39. additionalTrustBundle: | (11)
  40. -----BEGIN CERTIFICATE-----
  41. <MY_TRUSTED_CA_CERT>
  42. -----END CERTIFICATE-----
  43. sshKey: ssh-ed25519 AAAA... (12)
1The controlPlane section is a single mapping, but the compute section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the compute section must begin with a hyphen, -, and the first line of the controlPlane section must not. Only one control plane pool is used.
2You can specify the size of the disk to use in GB. Minimum recommendation for control plane nodes is 1024 GB.
3Specify the name of the cluster.
4The cluster network plugin to install. The supported values are OVNKubernetes and OpenShiftSDN. The default value is OVNKubernetes.
5Specify the Azure Resource Manager endpoint that your Azure Stack Hub operator provides.
6Specify the name of the resource group that contains the DNS zone for your base domain.
7Specify the name of your Azure Stack Hub local region.
8Specify the name of an already existing resource group to install your cluster to. If undefined, a new resource group is created for the cluster.
9Specify the Azure Stack Hub environment as your target platform.
10Specify the pull secret required to authenticate your cluster.
11If your Azure Stack Hub environment uses an internal certificate authority (CA), add the necessary certificate bundle in .pem format.
12You can optionally provide the sshKey value that you use to access the machines in your cluster.

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.

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.

  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 Stack Hub.

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

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

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

  6. Optional: If your Azure Stack Hub environment uses an internal certificate authority (CA), you must update the .spec.trustedCA.name field in the <installation_directory>/manifests/cluster-proxy-01-config.yaml file to use user-ca-bundle:

    1. ...
    2. spec:
    3. trustedCA:
    4. name: user-ca-bundle
    5. ...

    Later, you must update your bootstrap ignition to include the CA.

  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. Manually create your cloud credentials.

    1. From the directory that contains the installation program, obtain details of the OKD release image that your openshift-install binary is built to use:

      1. $ openshift-install version

      Example output

      1. release image quay.io/openshift-release-dev/ocp-release:4.y.z-x86_64
    2. Locate all CredentialsRequest objects in this release image that target the cloud you are deploying on:

      1. $ oc adm release extract quay.io/openshift-release-dev/ocp-release:4.y.z-x86_64 --credentials-requests --cloud=azure

      This command creates a YAML file for each CredentialsRequest object.

      Sample CredentialsRequest object

      1. apiVersion: cloudcredential.openshift.io/v1
      2. kind: CredentialsRequest
      3. metadata:
      4. labels:
      5. controller-tools.k8s.io: "1.0"
      6. name: openshift-image-registry-azure
      7. namespace: openshift-cloud-credential-operator
      8. spec:
      9. secretRef:
      10. name: installer-cloud-credentials
      11. namespace: openshift-image-registry
      12. providerSpec:
      13. apiVersion: cloudcredential.openshift.io/v1
      14. kind: AzureProviderSpec
      15. roleBindings:
      16. - role: Contributor
    3. Create YAML files for secrets in the openshift-install manifests directory that you generated previously. The secrets must be stored using the namespace and secret name defined in the spec.secretRef for each CredentialsRequest object. The format for the secret data varies for each cloud provider.

      Sample secrets.yaml file:

      1. apiVersion: v1
      2. kind: Secret
      3. metadata:
      4. name: ${secret_name}
      5. namespace: ${secret_namespace}
      6. stringData:
      7. azure_subscription_id: ${subscription_id}
      8. azure_client_id: ${app_id}
      9. azure_client_secret: ${client_secret}
      10. azure_tenant_id: ${tenant_id}
      11. azure_resource_prefix: ${cluster_name}
      12. azure_resourcegroup: ${resource_group}
      13. azure_region: ${azure_region}

The release image includes CredentialsRequest objects for Technology Preview features that are enabled by the TechPreviewNoUpgrade feature set. You can identify these objects by their use of the release.openshift.io/feature-set: TechPreviewNoUpgrade annotation.

  • If you are not using any of these features, do not create secrets for these objects. Creating secrets for Technology Preview features that you are not using can cause the installation to fail.

  • If you are using any of these features, you must create secrets for the corresponding objects.

  • To find CredentialsRequest objects with the TechPreviewNoUpgrade annotation, run the following command:

    1. $ grep "release.openshift.io/feature-set" *

    Example output

    1. 0000_30_capi-operator_00_credentials-request.yaml: release.openshift.io/feature-set: TechPreviewNoUpgrade
    1. Create a cco-configmap.yaml file in the manifests directory with the Cloud Credential Operator (CCO) disabled:

      Sample ConfigMap object

      1. apiVersion: v1
      2. kind: ConfigMap
      3. metadata:
      4. name: cloud-credential-operator-config
      5. namespace: openshift-cloud-credential-operator
      6. annotations:
      7. release.openshift.io/create-only: "true"
      8. data:
      9. disabled: "true"
      1. 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

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.12.0
    3. metadata:
    4. labels:
    5. machineconfiguration.openshift.io/role: worker
    6. name: 98-var-partition
    7. storage:
    8. disks:
    9. - device: /dev/<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 Azure resource group

You must create a Microsoft Azure resource group. This is used during the installation of your OKD cluster on Azure Stack Hub.

Prerequisites

  • Configure an Azure account.

  • Generate the Ignition config files for your cluster.

Procedure

  • Create the resource group in a supported Azure region:

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

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 COMPRESSED_VHD_URL=$(openshift-install coreos print-stream-json | jq -r '.architectures.x86_64.artifacts.azurestack.formats."vhd.gz".disk.location')

    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. Download the compressed FCOS VHD file locally:

    1. $ curl -O -L ${COMPRESSED_VHD_URL}
  6. Decompress the VHD file.

    The decompressed VHD file is approximately 16 GB, so be sure that your host system has 16 GB of free space available. You can delete the VHD file after you upload it.

  7. Copy the local VHD to a blob:

    1. $ az storage blob upload --account-name ${CLUSTER_NAME}sa --account-key ${ACCOUNT_KEY} -c vhd -n "rhcos.vhd" -f rhcos-<rhcos_version>-azurestack.x86_64.vhd
  8. 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 Stack Hub’s datacenter DNS integration is used, so you will create a DNS zone.

The 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 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

  • Create the new 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 DNS zone that already exists.

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

Creating a VNet in Azure Stack Hub

You must create a virtual network (VNet) in Microsoft Azure Stack Hub 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 Stack Hub 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.

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" : "2017-10-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" : "2017-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. "name" : "ign_in",
  84. "properties" : {
  85. "protocol" : "*",
  86. "sourcePortRange" : "*",
  87. "destinationPortRange" : "22623",
  88. "sourceAddressPrefix" : "*",
  89. "destinationAddressPrefix" : "*",
  90. "access" : "Allow",
  91. "priority" : 102,
  92. "direction" : "Inbound"
  93. }
  94. }
  95. ]
  96. }
  97. }
  98. ]
  99. }

Deploying the FCOS cluster image for the Azure Stack Hub infrastructure

You must use a valid Fedora CoreOS (FCOS) image for Microsoft Azure Stack Hub 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)
    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.

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/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. "vhdBlobURL" : {
  13. "type" : "string",
  14. "metadata" : {
  15. "description" : "URL pointing to the blob where the VHD to be used to create master and worker machines is located"
  16. }
  17. }
  18. },
  19. "variables" : {
  20. "location" : "[resourceGroup().location]",
  21. "imageName" : "[concat(parameters('baseName'), '-image')]"
  22. },
  23. "resources" : [
  24. {
  25. "apiVersion" : "2017-12-01",
  26. "type": "Microsoft.Compute/images",
  27. "name": "[variables('imageName')]",
  28. "location" : "[variables('location')]",
  29. "properties": {
  30. "storageProfile": {
  31. "osDisk": {
  32. "osType": "Linux",
  33. "osState": "Generalized",
  34. "blobUri": "[parameters('vhdBlobURL')]",
  35. "storageAccountType": "Standard_LRS"
  36. }
  37. }
  38. }
  39. }
  40. ]
  41. }

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 1. 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 2. Ports used for all-machine to control plane communications
ProtocolPortDescription

TCP

6443

Kubernetes API

Table 3. 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 Stack Hub

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

Load balancing requires the following DNS records:

  • An api DNS record for the API public load balancer in the DNS zone.

  • An api-int DNS record for the API internal load balancer in the DNS zone.

If you do not use the provided ARM template to create your Azure Stack Hub 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 Stack Hub.

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 baseName="${INFRA_ID}"(1)
    1The base name to be used in resource names; this is usually the cluster’s infrastructure ID.
  3. Create an api DNS record and an api-int DNS record. When creating the API DNS records, the ${BASE_DOMAIN_RESOURCE_GROUP} variable must point to the resource group where the 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. Export the following variable:

      1. $ export PRIVATE_IP=`az network lb frontend-ip show -g "$RESOURCE_GROUP" --lb-name "${INFRA_ID}-internal" -n internal-lb-ip --query "privateIpAddress" -o tsv`
    3. Create the api DNS record in a new DNS 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 DNS 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
    4. Create the api-int DNS record in a new DNS zone:

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

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

      1. $ az network dns record-set a add-record -g ${BASE_DOMAIN_RESOURCE_GROUP} -z ${BASE_DOMAIN} -n api-int.${CLUSTER_NAME} -a ${PRIVATE_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. },
  13. "variables" : {
  14. "location" : "[resourceGroup().location]",
  15. "virtualNetworkName" : "[concat(parameters('baseName'), '-vnet')]",
  16. "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  17. "masterSubnetName" : "[concat(parameters('baseName'), '-master-subnet')]",
  18. "masterSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('masterSubnetName'))]",
  19. "masterPublicIpAddressName" : "[concat(parameters('baseName'), '-master-pip')]",
  20. "masterPublicIpAddressID" : "[resourceId('Microsoft.Network/publicIPAddresses', variables('masterPublicIpAddressName'))]",
  21. "masterLoadBalancerName" : "[concat(parameters('baseName'))]",
  22. "masterLoadBalancerID" : "[resourceId('Microsoft.Network/loadBalancers', variables('masterLoadBalancerName'))]",
  23. "masterAvailabilitySetName" : "[concat(parameters('baseName'), '-avset')]",
  24. "internalLoadBalancerName" : "[concat(parameters('baseName'), '-internal')]",
  25. "internalLoadBalancerID" : "[resourceId('Microsoft.Network/loadBalancers', variables('internalLoadBalancerName'))]",
  26. "skuName": "Basic"
  27. },
  28. "resources" : [
  29. {
  30. "apiVersion": "2017-03-30",
  31. "type" : "Microsoft.Compute/availabilitySets",
  32. "name" : "[variables('masterAvailabilitySetName')]",
  33. "location" : "[variables('location')]",
  34. "properties": {
  35. "platformFaultDomainCount": "2",
  36. "platformUpdateDomainCount": "5"
  37. },
  38. "sku": {
  39. "name": "Aligned"
  40. }
  41. },
  42. {
  43. "apiVersion" : "2017-10-01",
  44. "type" : "Microsoft.Network/publicIPAddresses",
  45. "name" : "[variables('masterPublicIpAddressName')]",
  46. "location" : "[variables('location')]",
  47. "sku": {
  48. "name": "[variables('skuName')]"
  49. },
  50. "properties" : {
  51. "publicIPAllocationMethod" : "Static",
  52. "dnsSettings" : {
  53. "domainNameLabel" : "[variables('masterPublicIpAddressName')]"
  54. }
  55. }
  56. },
  57. {
  58. "apiVersion" : "2017-10-01",
  59. "type" : "Microsoft.Network/loadBalancers",
  60. "name" : "[variables('masterLoadBalancerName')]",
  61. "location" : "[variables('location')]",
  62. "sku": {
  63. "name": "[variables('skuName')]"
  64. },
  65. "dependsOn" : [
  66. "[concat('Microsoft.Network/publicIPAddresses/', variables('masterPublicIpAddressName'))]"
  67. ],
  68. "properties" : {
  69. "frontendIPConfigurations" : [
  70. {
  71. "name" : "public-lb-ip",
  72. "properties" : {
  73. "publicIPAddress" : {
  74. "id" : "[variables('masterPublicIpAddressID')]"
  75. }
  76. }
  77. }
  78. ],
  79. "backendAddressPools" : [
  80. {
  81. "name" : "[variables('masterLoadBalancerName')]"
  82. }
  83. ],
  84. "loadBalancingRules" : [
  85. {
  86. "name" : "api-public",
  87. "properties" : {
  88. "frontendIPConfiguration" : {
  89. "id" :"[concat(variables('masterLoadBalancerID'), '/frontendIPConfigurations/public-lb-ip')]"
  90. },
  91. "backendAddressPool" : {
  92. "id" : "[concat(variables('masterLoadBalancerID'), '/backendAddressPools/', variables('masterLoadBalancerName'))]"
  93. },
  94. "protocol" : "Tcp",
  95. "loadDistribution" : "Default",
  96. "idleTimeoutInMinutes" : 30,
  97. "frontendPort" : 6443,
  98. "backendPort" : 6443,
  99. "probe" : {
  100. "id" : "[concat(variables('masterLoadBalancerID'), '/probes/api-public-probe')]"
  101. }
  102. }
  103. }
  104. ],
  105. "probes" : [
  106. {
  107. "name" : "api-public-probe",
  108. "properties" : {
  109. "protocol" : "Tcp",
  110. "port" : 6443,
  111. "intervalInSeconds" : 10,
  112. "numberOfProbes" : 3
  113. }
  114. }
  115. ]
  116. }
  117. },
  118. {
  119. "apiVersion" : "2017-10-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" : "[variables('internalLoadBalancerName')]"
  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/', variables('internalLoadBalancerName'))]"
  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/', variables('internalLoadBalancerName'))]"
  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" : "Tcp",
  193. "port" : 6443,
  194. "intervalInSeconds" : 10,
  195. "numberOfProbes" : 3
  196. }
  197. },
  198. {
  199. "name" : "sint-probe",
  200. "properties" : {
  201. "protocol" : "Tcp",
  202. "port" : 22623,
  203. "intervalInSeconds" : 10,
  204. "numberOfProbes" : 3
  205. }
  206. }
  207. ]
  208. }
  209. }
  210. ]
  211. }

Creating the bootstrap machine in Azure Stack Hub

You must create the bootstrap machine in Microsoft Azure Stack Hub 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 Stack Hub.

  • Create and configure networking and load balancers in Azure Stack Hub.

  • 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. If your environment uses a public certificate authority (CA), run this command:

      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'`
    2. If your environment uses an internal CA, you must add your PEM encoded bundle to the bootstrap ignition stub so that your bootstrap virtual machine can pull the bootstrap ignition from the storage account. Run the following commands, which assume your CA is in a file called CA.pem:

      1. $ export CA="data:text/plain;charset=utf-8;base64,$(cat CA.pem |base64 |tr -d '\n')"
      1. $ export BOOTSTRAP_IGNITION=`jq -rcnM --arg v "3.2.0" --arg url "$BOOTSTRAP_URL" --arg cert "$CA" '{ignition:{version:$v,security:{tls:{certificateAuthorities:[{source:$cert}]}},config:{replace:{source:$url}}}}' | base64 | tr -d '\n'`
  4. Create the deployment by using the az CLI:

    1. $ az deployment group create --verbose -g ${RESOURCE_GROUP} \
    2. --template-file "<installation_directory>/04_bootstrap.json" \
    3. --parameters bootstrapIgnition="${BOOTSTRAP_IGNITION}" \ (1)
    4. --parameters baseName="${INFRA_ID}" \ (2)
    5. --parameters diagnosticsStorageAccountName="${CLUSTER_NAME}sa" (3)
    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.
    3The name of the storage account for your cluster.

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. "bootstrapIgnition" : {
  13. "type" : "string",
  14. "minLength" : 1,
  15. "metadata" : {
  16. "description" : "Bootstrap ignition content for the bootstrap cluster"
  17. }
  18. },
  19. "sshKeyData" : {
  20. "type" : "securestring",
  21. "metadata" : {
  22. "description" : "SSH RSA public key file as a string."
  23. }
  24. },
  25. "diagnosticsStorageAccountName": {
  26. "type": "string"
  27. },
  28. "bootstrapVMSize" : {
  29. "type" : "string",
  30. "defaultValue" : "Standard_DS4_v2",
  31. "metadata" : {
  32. "description" : "The size of the Bootstrap Virtual Machine"
  33. }
  34. }
  35. },
  36. "variables" : {
  37. "location" : "[resourceGroup().location]",
  38. "virtualNetworkName" : "[concat(parameters('baseName'), '-vnet')]",
  39. "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  40. "masterSubnetName" : "[concat(parameters('baseName'), '-master-subnet')]",
  41. "masterSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('masterSubnetName'))]",
  42. "masterLoadBalancerName" : "[concat(parameters('baseName'))]",
  43. "masterAvailabilitySetName" : "[concat(parameters('baseName'), '-avset')]",
  44. "internalLoadBalancerName" : "[concat(parameters('baseName'), '-internal')]",
  45. "sshKeyPath" : "/home/core/.ssh/authorized_keys",
  46. "vmName" : "[concat(parameters('baseName'), '-bootstrap')]",
  47. "nicName" : "[concat(variables('vmName'), '-nic')]",
  48. "imageName" : "[concat(parameters('baseName'), '-image')]",
  49. "clusterNsgName" : "[concat(parameters('baseName'), '-nsg')]",
  50. "sshPublicIpAddressName" : "[concat(variables('vmName'), '-ssh-pip')]"
  51. },
  52. "resources" : [
  53. {
  54. "apiVersion" : "2017-10-01",
  55. "type" : "Microsoft.Network/publicIPAddresses",
  56. "name" : "[variables('sshPublicIpAddressName')]",
  57. "location" : "[variables('location')]",
  58. "sku": {
  59. "name": "Basic"
  60. },
  61. "properties" : {
  62. "publicIPAllocationMethod" : "Static",
  63. "dnsSettings" : {
  64. "domainNameLabel" : "[variables('sshPublicIpAddressName')]"
  65. }
  66. }
  67. },
  68. {
  69. "apiVersion" : "2017-10-01",
  70. "type" : "Microsoft.Network/networkInterfaces",
  71. "name" : "[variables('nicName')]",
  72. "location" : "[variables('location')]",
  73. "dependsOn" : [
  74. "[resourceId('Microsoft.Network/publicIPAddresses', variables('sshPublicIpAddressName'))]"
  75. ],
  76. "properties" : {
  77. "securityRules": [
  78. {
  79. "properties": {
  80. "description": "ssh-in-nic",
  81. "protocol": "Tcp",
  82. "sourcePortRange": "*",
  83. "destinationPortRange": "22"
  84. }}],
  85. "ipConfigurations" : [
  86. {
  87. "name" : "pipConfig",
  88. "properties" : {
  89. "privateIPAllocationMethod" : "Dynamic",
  90. "publicIPAddress": {
  91. "id": "[resourceId('Microsoft.Network/publicIPAddresses', variables('sshPublicIpAddressName'))]"
  92. },
  93. "subnet" : {
  94. "id" : "[variables('masterSubnetRef')]"
  95. },
  96. "loadBalancerBackendAddressPools" : [
  97. {
  98. "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('masterLoadBalancerName'), '/backendAddressPools/', variables('masterLoadBalancerName'))]"
  99. },
  100. {
  101. "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('internalLoadBalancerName'), '/backendAddressPools/', variables('internalLoadBalancerName'))]"
  102. }
  103. ]
  104. }
  105. }
  106. ]
  107. }
  108. },
  109. {
  110. "name": "[parameters('diagnosticsStorageAccountName')]",
  111. "type": "Microsoft.Storage/storageAccounts",
  112. "apiVersion": "2017-10-01",
  113. "location": "[variables('location')]",
  114. "properties": {},
  115. "kind": "Storage",
  116. "sku": {
  117. "name": "Standard_LRS"
  118. }
  119. },
  120. {
  121. "apiVersion" : "2017-12-01",
  122. "type" : "Microsoft.Compute/virtualMachines",
  123. "name" : "[variables('vmName')]",
  124. "location" : "[variables('location')]",
  125. "dependsOn" : [
  126. "[concat('Microsoft.Network/networkInterfaces/', variables('nicName'))]",
  127. "[concat('Microsoft.Storage/storageAccounts/', parameters('diagnosticsStorageAccountName'))]"
  128. ],
  129. "properties" : {
  130. "availabilitySet": {
  131. "id": "[resourceId('Microsoft.Compute/availabilitySets',variables('masterAvailabilitySetName'))]"
  132. },
  133. "hardwareProfile" : {
  134. "vmSize" : "[parameters('bootstrapVMSize')]"
  135. },
  136. "osProfile" : {
  137. "computerName" : "[variables('vmName')]",
  138. "adminUsername" : "core",
  139. "customData" : "[parameters('bootstrapIgnition')]",
  140. "linuxConfiguration" : {
  141. "disablePasswordAuthentication" : true,
  142. "ssh" : {
  143. "publicKeys" : [
  144. {
  145. "path" : "[variables('sshKeyPath')]",
  146. "keyData" : "[parameters('sshKeyData')]"
  147. }
  148. ]
  149. }
  150. }
  151. },
  152. "storageProfile" : {
  153. "imageReference": {
  154. "id": "[resourceId('Microsoft.Compute/images', variables('imageName'))]"
  155. },
  156. "osDisk" : {
  157. "name": "[concat(variables('vmName'),'_OSDisk')]",
  158. "osType" : "Linux",
  159. "createOption" : "FromImage",
  160. "managedDisk": {
  161. "storageAccountType": "Standard_LRS"
  162. },
  163. "diskSizeGB" : 100
  164. }
  165. },
  166. "networkProfile" : {
  167. "networkInterfaces" : [
  168. {
  169. "id" : "[resourceId('Microsoft.Network/networkInterfaces', variables('nicName'))]"
  170. }
  171. ]
  172. },
  173. "diagnosticsProfile": {
  174. "bootDiagnostics": {
  175. "enabled": true,
  176. "storageUri": "[reference(resourceId('Microsoft.Storage/storageAccounts', parameters('diagnosticsStorageAccountName'))).primaryEndpoints.blob]"
  177. }
  178. }
  179. }
  180. },
  181. {
  182. "apiVersion" : "2017-10-01",
  183. "type": "Microsoft.Network/networkSecurityGroups/securityRules",
  184. "name" : "[concat(variables('clusterNsgName'), '/bootstrap_ssh_in')]",
  185. "location" : "[variables('location')]",
  186. "dependsOn" : [
  187. "[resourceId('Microsoft.Compute/virtualMachines', variables('vmName'))]"
  188. ],
  189. "properties": {
  190. "protocol" : "Tcp",
  191. "sourcePortRange" : "*",
  192. "destinationPortRange" : "22",
  193. "sourceAddressPrefix" : "*",
  194. "destinationAddressPrefix" : "*",
  195. "access" : "Allow",
  196. "priority" : 100,
  197. "direction" : "Inbound"
  198. }
  199. }
  200. ]
  201. }

Creating the control plane machines in Azure Stack Hub

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

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, 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 Stack Hub.

  • Create and configure networking and load balancers in Azure Stack Hub.

  • 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)
    5. --parameters diagnosticsStorageAccountName="${CLUSTER_NAME}sa" (3)
    1The Ignition content for the control plane nodes (also known as the master nodes).
    2The base name to be used in resource names; this is usually the cluster’s infrastructure ID.
    3The name of the storage account for your cluster.

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. "masterIgnition" : {
  13. "type" : "string",
  14. "metadata" : {
  15. "description" : "Ignition content for the master nodes"
  16. }
  17. },
  18. "sshKeyData" : {
  19. "type" : "securestring",
  20. "metadata" : {
  21. "description" : "SSH RSA public key file as a string"
  22. }
  23. },
  24. "diagnosticsStorageAccountName": {
  25. "type": "string"
  26. },
  27. "masterVMSize" : {
  28. "type" : "string",
  29. "defaultValue" : "Standard_DS4_v2",
  30. "metadata" : {
  31. "description" : "The size of the Master Virtual Machines"
  32. }
  33. },
  34. "diskSizeGB" : {
  35. "type" : "int",
  36. "defaultValue" : 1023,
  37. "metadata" : {
  38. "description" : "Size of the Master VM OS disk, in GB"
  39. }
  40. }
  41. },
  42. "variables" : {
  43. "location" : "[resourceGroup().location]",
  44. "virtualNetworkName" : "[concat(parameters('baseName'), '-vnet')]",
  45. "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  46. "masterSubnetName" : "[concat(parameters('baseName'), '-master-subnet')]",
  47. "masterSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('masterSubnetName'))]",
  48. "masterLoadBalancerName" : "[concat(parameters('baseName'))]",
  49. "masterAvailabilitySetName" : "[concat(parameters('baseName'), '-avset')]",
  50. "internalLoadBalancerName" : "[concat(parameters('baseName'), '-internal')]",
  51. "sshKeyPath" : "/home/core/.ssh/authorized_keys",
  52. "clusterNsgName" : "[concat(parameters('baseName'), '-nsg')]",
  53. "imageName" : "[concat(parameters('baseName'), '-image')]",
  54. "numberOfMasters" : 3,
  55. "vms" : {
  56. "copy" : [
  57. {
  58. "name" : "vmNames",
  59. "count" : "[variables('numberOfMasters')]",
  60. "input" : {
  61. "name" : "[concat(parameters('baseName'), string('-master-'), string(copyIndex('vmNames')))]"
  62. }
  63. }
  64. ]
  65. }
  66. },
  67. "resources" : [
  68. {
  69. "name": "[parameters('diagnosticsStorageAccountName')]",
  70. "type": "Microsoft.Storage/storageAccounts",
  71. "apiVersion": "2017-10-01",
  72. "location": "[variables('location')]",
  73. "properties": {},
  74. "kind": "Storage",
  75. "sku": {
  76. "name": "Standard_LRS"
  77. }
  78. },
  79. {
  80. "apiVersion" : "2017-10-01",
  81. "type" : "Microsoft.Network/networkInterfaces",
  82. "location": "[variables('location')]",
  83. "copy" : {
  84. "name" : "nicCopy",
  85. "count" : "[variables('numberOfMasters')]"
  86. },
  87. "name" : "[concat(variables('vms').vmNames[copyIndex()].name, '-nic')]",
  88. "properties" : {
  89. "ipConfigurations" : [
  90. {
  91. "name" : "pipConfig",
  92. "properties" : {
  93. "privateIPAllocationMethod" : "Dynamic",
  94. "subnet" : {
  95. "id" : "[variables('masterSubnetRef')]"
  96. },
  97. "loadBalancerBackendAddressPools" : [
  98. {
  99. "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('masterLoadBalancerName'), '/backendAddressPools/', variables('masterLoadBalancerName'))]"
  100. },
  101. {
  102. "id" : "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Network/loadBalancers/', variables('internalLoadBalancerName'), '/backendAddressPools/', variables('internalLoadBalancerName'))]"
  103. }
  104. ]
  105. }
  106. }
  107. ]
  108. }
  109. },
  110. {
  111. "apiVersion" : "2017-12-01",
  112. "type" : "Microsoft.Compute/virtualMachines",
  113. "location" : "[variables('location')]",
  114. "copy" : {
  115. "name" : "vmCopy",
  116. "count" : "[variables('numberOfMasters')]"
  117. },
  118. "name" : "[variables('vms').vmNames[copyIndex()].name]",
  119. "dependsOn" : [
  120. "[concat('Microsoft.Network/networkInterfaces/', concat(variables('vms').vmNames[copyIndex()].name, '-nic'))]",
  121. "[concat('Microsoft.Storage/storageAccounts/', parameters('diagnosticsStorageAccountName'))]"
  122. ],
  123. "properties" : {
  124. "availabilitySet": {
  125. "id": "[resourceId('Microsoft.Compute/availabilitySets',variables('masterAvailabilitySetName'))]"
  126. },
  127. "hardwareProfile" : {
  128. "vmSize" : "[parameters('masterVMSize')]"
  129. },
  130. "osProfile" : {
  131. "computerName" : "[variables('vms').vmNames[copyIndex()].name]",
  132. "adminUsername" : "core",
  133. "customData" : "[parameters('masterIgnition')]",
  134. "linuxConfiguration" : {
  135. "disablePasswordAuthentication" : true,
  136. "ssh" : {
  137. "publicKeys" : [
  138. {
  139. "path" : "[variables('sshKeyPath')]",
  140. "keyData" : "[parameters('sshKeyData')]"
  141. }
  142. ]
  143. }
  144. }
  145. },
  146. "storageProfile" : {
  147. "imageReference": {
  148. "id": "[resourceId('Microsoft.Compute/images', variables('imageName'))]"
  149. },
  150. "osDisk" : {
  151. "name": "[concat(variables('vms').vmNames[copyIndex()].name, '_OSDisk')]",
  152. "osType" : "Linux",
  153. "createOption" : "FromImage",
  154. "writeAcceleratorEnabled": false,
  155. "managedDisk": {
  156. "storageAccountType": "Standard_LRS"
  157. },
  158. "diskSizeGB" : "[parameters('diskSizeGB')]"
  159. }
  160. },
  161. "networkProfile" : {
  162. "networkInterfaces" : [
  163. {
  164. "id" : "[resourceId('Microsoft.Network/networkInterfaces', concat(variables('vms').vmNames[copyIndex()].name, '-nic'))]",
  165. "properties": {
  166. "primary": false
  167. }
  168. }
  169. ]
  170. },
  171. "diagnosticsProfile": {
  172. "bootDiagnostics": {
  173. "enabled": true,
  174. "storageUri": "[reference(resourceId('Microsoft.Storage/storageAccounts', parameters('diagnosticsStorageAccountName'))).primaryEndpoints.blob]"
  175. }
  176. }
  177. }
  178. }
  179. ]
  180. }

Wait for bootstrap completion and remove bootstrap resources in Azure Stack Hub

After you create all of the required infrastructure in Microsoft Azure Stack Hub, 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 Stack Hub.

  • Create and configure networking and load balancers in Azure Stack Hub.

  • 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 Stack Hub

You can create worker machines in Microsoft Azure Stack Hub 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.

If you do not use the provided ARM template to create your worker machines, 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 Stack Hub.

  • Create and configure networking and load balancers in Azure Stack Hub.

  • 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)
    5. --parameters diagnosticsStorageAccountName="${CLUSTER_NAME}sa" (3)
    1The Ignition content for the worker nodes.
    2The base name to be used in resource names; this is usually the cluster’s infrastructure ID.
    3The name of the storage account for your cluster.

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. "workerIgnition" : {
  13. "type" : "string",
  14. "metadata" : {
  15. "description" : "Ignition content for the worker nodes"
  16. }
  17. },
  18. "numberOfNodes" : {
  19. "type" : "int",
  20. "defaultValue" : 3,
  21. "minValue" : 2,
  22. "maxValue" : 30,
  23. "metadata" : {
  24. "description" : "Number of OpenShift compute nodes to deploy"
  25. }
  26. },
  27. "sshKeyData" : {
  28. "type" : "securestring",
  29. "metadata" : {
  30. "description" : "SSH RSA public key file as a string"
  31. }
  32. },
  33. "diagnosticsStorageAccountName": {
  34. "type": "string"
  35. },
  36. "nodeVMSize" : {
  37. "type" : "string",
  38. "defaultValue" : "Standard_DS4_v2",
  39. "metadata" : {
  40. "description" : "The size of the each Node Virtual Machine"
  41. }
  42. }
  43. },
  44. "variables" : {
  45. "location" : "[resourceGroup().location]",
  46. "virtualNetworkName" : "[concat(parameters('baseName'), '-vnet')]",
  47. "virtualNetworkID" : "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
  48. "nodeSubnetName" : "[concat(parameters('baseName'), '-worker-subnet')]",
  49. "nodeSubnetRef" : "[concat(variables('virtualNetworkID'), '/subnets/', variables('nodeSubnetName'))]",
  50. "infraLoadBalancerName" : "[parameters('baseName')]",
  51. "sshKeyPath" : "/home/core/.ssh/authorized_keys",
  52. "identityName" : "[concat(parameters('baseName'), '-identity')]",
  53. "imageName" : "[concat(parameters('baseName'), '-image')]",
  54. "masterAvailabilitySetName" : "[concat(parameters('baseName'), '-avset')]",
  55. "numberOfNodes" : "[parameters('numberOfNodes')]",
  56. "vms" : {
  57. "copy" : [
  58. {
  59. "name" : "vmNames",
  60. "count" : "[parameters('numberOfNodes')]",
  61. "input" : {
  62. "name" : "[concat(parameters('baseName'), string('-worker-'), string(copyIndex('vmNames')))]"
  63. }
  64. }
  65. ]
  66. }
  67. },
  68. "resources" : [
  69. {
  70. "name": "[parameters('diagnosticsStorageAccountName')]",
  71. "type": "Microsoft.Storage/storageAccounts",
  72. "apiVersion": "2017-10-01",
  73. "location": "[variables('location')]",
  74. "properties": {},
  75. "kind": "Storage",
  76. "sku": {
  77. "name": "Standard_LRS"
  78. }
  79. },
  80. {
  81. "apiVersion" : "2017-10-01",
  82. "type" : "Microsoft.Network/networkInterfaces",
  83. "location": "[variables('location')]",
  84. "copy" : {
  85. "name" : "nicCopy",
  86. "count" : "[variables('numberOfNodes')]"
  87. },
  88. "name" : "[concat(variables('vms').vmNames[copyIndex()].name, '-nic')]",
  89. "properties" : {
  90. "ipConfigurations" : [
  91. {
  92. "name" : "pipConfig",
  93. "properties" : {
  94. "privateIPAllocationMethod" : "Dynamic",
  95. "subnet" : {
  96. "id" : "[variables('nodeSubnetRef')]"
  97. }
  98. }
  99. }
  100. ]
  101. }
  102. },
  103. {
  104. "apiVersion" : "2017-12-01",
  105. "type" : "Microsoft.Compute/virtualMachines",
  106. "location" : "[variables('location')]",
  107. "copy" : {
  108. "name" : "vmCopy",
  109. "count" : "[variables('numberOfNodes')]"
  110. },
  111. "name" : "[variables('vms').vmNames[copyIndex()].name]",
  112. "dependsOn" : [
  113. "[concat('Microsoft.Network/networkInterfaces/', concat(variables('vms').vmNames[copyIndex()].name, '-nic'))]",
  114. "[concat('Microsoft.Storage/storageAccounts/', parameters('diagnosticsStorageAccountName'))]"
  115. ],
  116. "properties" : {
  117. "availabilitySet": {
  118. "id": "[resourceId('Microsoft.Compute/availabilitySets',variables('masterAvailabilitySetName'))]"
  119. },
  120. "hardwareProfile" : {
  121. "vmSize" : "[parameters('nodeVMSize')]"
  122. },
  123. "osProfile" : {
  124. "computerName" : "[variables('vms').vmNames[copyIndex()].name]",
  125. "adminUsername" : "core",
  126. "customData" : "[parameters('workerIgnition')]",
  127. "linuxConfiguration" : {
  128. "disablePasswordAuthentication" : true,
  129. "ssh" : {
  130. "publicKeys" : [
  131. {
  132. "path" : "[variables('sshKeyPath')]",
  133. "keyData" : "[parameters('sshKeyData')]"
  134. }
  135. ]
  136. }
  137. }
  138. },
  139. "storageProfile" : {
  140. "imageReference": {
  141. "id": "[resourceId('Microsoft.Compute/images', variables('imageName'))]"
  142. },
  143. "osDisk" : {
  144. "name": "[concat(variables('vms').vmNames[copyIndex()].name,'_OSDisk')]",
  145. "osType" : "Linux",
  146. "createOption" : "FromImage",
  147. "managedDisk": {
  148. "storageAccountType": "Standard_LRS"
  149. },
  150. "diskSizeGB": 128
  151. }
  152. },
  153. "networkProfile" : {
  154. "networkInterfaces" : [
  155. {
  156. "id" : "[resourceId('Microsoft.Network/networkInterfaces', concat(variables('vms').vmNames[copyIndex()].name, '-nic'))]",
  157. "properties": {
  158. "primary": true
  159. }
  160. }
  161. ]
  162. },
  163. "diagnosticsProfile": {
  164. "bootDiagnostics": {
  165. "enabled": true,
  166. "storageUri": "[reference(resourceId('Microsoft.Storage/storageAccounts', parameters('diagnosticsStorageAccountName'))).primaryEndpoints.blob]"
  167. }
  168. }
  169. }
  170. }
  171. ]
  172. }

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.12. 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 link: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 xvzf <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 link: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 link: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.25.0
    3. master-1 Ready master 63m v1.25.0
    4. master-2 Ready master 64m v1.25.0

    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.25.0
    3. master-1 Ready master 73m v1.25.0
    4. master-2 Ready master 74m v1.25.0
    5. worker-0 Ready worker 11m v1.25.0
    6. worker-1 Ready worker 11m v1.25.0

    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 Stack Hub 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 DNS zone.

    1. If you are adding this cluster to a new DNS 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 DNS 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

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 Stack Hub installation on user-provisioned infrastructure

After you start the OKD installation on Microsoft Azure Stack Hub 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 Stack Hub 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