此内容没有您所选择的语言版本。

Chapter 19. Configuring for Azure

19.1. Overview

OpenShift Container Platform can be configured to access a Microsoft Azure infrastructure, including using Azure disk as persistent storage for application data. After Microsoft Azure is configured properly, some additional configurations need to be completed on the OpenShift Container Platform hosts.

19.2. Permissions

Configuring Microsoft Azure for OpenShift Container Platform requires the following role:

Contributor

To create and manage all types of Microsoft Azure resources.

For more information about adding administrator roles, see Add or change Azure subscription administrators.

19.3. Prerequisites

If you are using Microsoft Azure Disk as a persistent volume on the OpenShift Container Platform version 3.5 or later, you must enable Azure Cloud Provider.
All OpenShift Container Platform node virtual machines (VMs) running in Microsoft Azure must belong to a single resource group.
Microsoft Azure VMs must be named the same as OpenShift Container Platform nodes and this cannot include capital letters.
If you plan to use Azure Managed Disks:
- OpenShift Container Platform version 3.7 or later is required.
- You must create VMs with Azure Managed Disks.
If you plan to use unmanaged disks:
- You must create VMs with unmanaged disks.
If you are using a custom DNS configuration for your OpenShift Container Platform cluster or your cluster nodes are in different Microsoft Azure Virtual Networks (VNet), you must configure DNS so that each node in the cluster can resolve IP addresses for other nodes.

19.4. The Azure Configuration File

Configuring OpenShift Container Platform for Azure requires the /etc/azure/azure.conf file, on each node host.

If the file does not exist, create it, and add the following:

tenantId: <> 1
subscriptionId: <> 2
aadClientId: <> 3
aadClientSecret: <> 4
aadTenantId: <> 5
resourceGroup: <> 6
location: <> 7

1: The AAD tenant ID for the subscription that the cluster is deployed in.
2: The Azure subscription ID that the cluster is deployed in.
3: The client ID for an AAD application with RBAC access to talk to Azure RM APIs.
4: The client secret for an AAD application with RBAC access to talk to Azure RM APIs.
5: Ensure this is the same as tenant ID (optional).
6: The Azure Resource Group name that Azure VM belongs to.
7: The compact style Azure region, for example southeastasia (optional).

19.5. Configuring Masters

Edit or create the master configuration file on all masters (/etc/origin/master/master-config.yaml by default) and update the contents of the apiServerArguments and controllerArguments sections:

kubernetesMasterConfig:
  ...
  apiServerArguments:
    cloud-provider:
      - "azure"
    cloud-config:
      - "/etc/azure/azure.conf"
  controllerArguments:
    cloud-provider:
      - "azure"
    cloud-config:
      - "/etc/azure/azure.conf"

Important

When triggering a containerized installation, only the /etc/origin and /var/lib/origin directories are mounted to the master and node container. Therefore, master-config.yaml should be in /etc/origin/master instead of /etc/.

19.6. Configuring Nodes

Edit or create the node configuration file on all nodes (/etc/origin/node/node-config.yaml by default) and update the contents of the kubeletArguments section:
```
kubeletArguments:
  cloud-provider:
    - "azure"
  cloud-config:
    - "/etc/azure/azure.conf"
```
Important
When triggering a containerized installation, only the /etc/origin and /var/lib/origin directories are mounted to the master and node container. Therefore, node-config.yaml should be in /etc/origin/node instead of /etc/.

19.7. Applying Configuration Changes

Start or restart OpenShift Container Platform services on all master and node hosts to apply your configuration changes, see Restarting OpenShift Container Platform services:

# systemctl restart atomic-openshift-master-api atomic-openshift-master-controllers
# systemctl restart atomic-openshift-node

Switching from not using a cloud provider to using a cloud provider produces an error message. Adding the cloud provider tries to delete the node because the node switches from using the hostname as the externalID (which would have been the case when no cloud provider was being used) to using the cloud provider’s instance-id (which is what the cloud provider specifies). To resolve this issue:

Check and back up existing node labels:

$ oc describe node <node_name> | grep -Poz '(?s)Labels.*\n.*(?=Taints)'

Delete the nodes:
```
$ oc delete node <node_name>
```
On each node host, restart the OpenShift Container Platform service.
```
# systemctl restart atomic-openshift-node
```
Add back any labels on each node that you previously had.