Continental Innovates with Rancher and Kubernetes
When using the Azure cloud provider, you can leverage the following capabilities:
Load Balancers: Launches an Azure Load Balancer within a specific Network Security Group.
Persistent Volumes: Supports using Azure Blob disks and Azure Managed Disks with standard and premium storage accounts.
Network Storage: Support Azure Files via CIFS mounts.
The following account types are not supported for Azure Subscriptions:
To set up the Azure cloud provider following credentials need to be configured:
Visit Azure portal, login and go to Azure Active Directory and select Properties. Your Directory ID is your Tenant ID (tenantID).
If you want to use the Azure CLI, you can run the command az account show to get the information.
az account show
Visit Azure portal, login and follow the steps below to create an App Registration and the corresponding Azure Client ID (aadClientId) and Azure Client Secret (aadClientSecret).
Web app / API
In the App registrations view, you should see your created App registration. The value shown in the column APPLICATION ID is what you need to use as Azure Client ID.
The next step is to generate the Azure Client Secret:
The last thing you will need to do, is assign the appropriate permissions to your App registration.
A custom Azure Network Security Group (securityGroupName) is needed to allow Azure Load Balancers to work.
If you provision hosts using Rancher Machine Azure driver, you will need to edit them manually to assign them to this Network Security Group.
You should already assign custom hosts to this Network Security Group during provisioning.
Only hosts expected to be load balancer back ends need to be in this group.