Provision Infrastructure and Runtime Environment

You can use Domino’s public-facing Azure-specific reference terraform (TF) module as-is (recommended) or use the TF module as a resource to provision the infrastructure manually.

Provision your infrastructure using Domino’s terraform module as-is:

Use Azure Portal or Azure CLI to create a resource group in your subscription. You must reference the resource group name in the next steps.
Open the main.tf file and edit the attributes as follows:
- azurerm.subscription_id: ID of the subscription where the AKS will be deployed.
- domino-aks.api_server_authorized_ip_ranges: The IP ranges to allow incoming traffic into the server nodes or null to allow all traffic.
- domino-aks.resource_group: The name of the resource group that you created in the previous step.
- domino-aks.cluster_name: The name of the AKS to create.
- domino-aks.kubernetes_version: The Kubernetes version must be 1.20.x.
- domino-aks.node_pools.compute.vm_size: Change it if you don’t want to use the DS5_v2 SKU.
- domino-aks.node_pools.compute.gpu: Change it if you don’t want to use the NC6s_v3 SKU.
- domino-aks.node_pools.compute.platform: Change it if you don’t want to use the DS5_v2 SKU.
Confirm that your vCPU quotas in your Azure subscription are large enough to meet the node_pools values. See the instructions to check your vCPU quotas.
Run terraform init in the folder where the main.tf file is located to initialize the modules.
Run the following commands to start the infrastructure deployment. Make sure the directory where you’re running these commands is writable.

Note
```
terraform plan -out=terraform.plan
terraform apply terraform.plan
```
Note