Microsoft Azure resource prerequisites

1. Create a Resource Group (guide) to hold all the resources you will create in steps 2 through 5

2. Create an Azure Linux virtual machine (guide) with Dash Enterprise installed on it according to our instructions in Dash Enterprise Single Server: On-Premise Installation on Own Server

   1. In the Networking section, set NIC network security group to advanced and add inbound ports as described in Open ports

   2. In the Management section, enable System assigned managed identity

3. Create an Azure Database for PostgreSQL (guide) instance using Postgres 11 and configure as follows:

   1. In Connection Security:

      1. Set Allow access to Azure services to Yes and add the IP address of the VM you created in Step 2 to the field

      2. Set Enforce SSL connection to Disabled

      3. Under Allow access to Azure services, add the IP address of your workstation, then connect to the Postgres instance and create the following two databases:

         • dashauth

         • dash_deployment_server

4. Create an Azure Cache for Redis (guide) and unblock port 6379

5. Create an Azure Kubernetes Service cluster (guide) and configure it as follows:

   1. Kubernetes version: choose the latest supported version from supported Kubernetes versions.

   2. Recommended node size: D4_v3

      1. Set this to N12s_v2 if the cluster will be used to deploy RAPIDS apps

   3. Node count: >= 4

   4. Authentication method: System-assigned managed identity

   5. Network configuration: advanced

      1. Use the same virtual network as the resource group

   6. Select Calico network services

   7. In the Integrations section, create a new container registry

6. Assign the virtual machine from Step 2 the Contributor IAM role to the cluster as well as the container registry (guide):

   1. Go to the cluster’s page, select Add a role assignment from IAM roles and select the created VM as a Contributor

   2. Go to the container registry’s page and add the role assignment following similar steps

As part of installation, Azure will create a new resource group with the following naming structure:

MC_{resource group from step 1}_{cluster name}_{region}

To avoid configuration problems, do not modify this group.