Set Up Cloud Environment for Azure

This guide will walk you through setting up the necessary environment that you will use throughout your installation to create cloud resources on Azure.

See also

Procedure

  1. Find all available regions and decide on the region you will use to create all necessary resources:

    root@rok-tools:~# az account list-locations -o table
DisplayName               Name                 RegionalDisplayName
------------------------  -------------------  -------------------------------------
East US                   eastus               (US) East US
East US 2                 eastus2              (US) East US 2
South Central US          southcentralus       (US) South Central US
West US 2                 westus2              (US) West US 2
West US 3                 westus3              (US) West US 3
...

  2. Go to the Azure products availability page and ensure that the Virtual Machine sizes that you want to use for your AKS cluster are available in the region you selected. If not, select a different region.

    Note

    In this guide, we are going to use the Lsv2-series Virtual Machines.

  3. Store the region you selected in a variable so you can retrieve it later. The remaining of the guide assumes that you will be using this location when creating resources via the Azure portal. The corresponding regional display name is (US) East US. We will refer to it as your desired region.

    root@rok-tools:~# export AZURE_DEFAULTS_LOCATION=eastus

  4. Find your current active subscription. The remaining of the guide assumes that you will be using this subscription when you create resources via the Azure portal. We will refer to it as your desired subscription.

    root@rok-tools:~# az account show --query name -o tsv
Azure subscription

  5. Store the ID of your desired subscription so you can retrieve it later:

    root@rok-tools:~# export SUBSCRIPTION_ID=$(az account show --query id -o tsv)

Summary

You have successfully set up the environment necessary for creating Cloud resources on Azure.

What's Next

The next step is to configure access to Arrikto's private container registry.

PreviousNext