domino logo
About DominoArchitecture
Kubernetes
Cluster RequirementsDomino on EKSDomino Kubernetes Version CompatibilityDomino on GKEDomino on AKSDomino on OpenShiftNVIDIA DGX in DominoDomino in Multi-Tenant Kubernetes ClusterEncryption in Transit
Installation
Installation ProcessConfiguration ReferenceInstaller Configuration ExamplesPrivate or Offline InstallationCustom Certificatesfleetcommand-agent release notes
Azure Deployments
Prepare for InstallationProvision Infrastructure and Runtime EnvironmentDeploy Domino
Google Cloud Deployments
Prepare for InstallationProvision Infrastructure and Runtime EnvironmentDeploy Domino
Amazon Web Services Deployments
Prepare for InstallationProvision Infrastructure and Runtime EnvironmentDeploy Domino
Configuration
Central ConfigurationNotificationsFeature FlagsChange The Default Project For New UsersProject Stage ConfigurationDomino Integration With Atlassian Jira
Compute
Manage Domino Compute ResourcesHardware Tier Best PracticesModel Resource QuotasPersistent Volume ManagementAdding a Node Pool to your Domino ClusterRemove a Node from Service
Keycloak Authentication Service
Operations
Domino Application LoggingDomino MonitoringSizing Infrastructure for Domino
Data Management
Data in DominoData Flow In DominoExternal Data VolumesConfigure Data Source AuthenticationDatasets AdministrationSubmit GDPR Requests
User Management
RolesManage UsersView User InformationRun a User Activity ReportSchedule a User Activity Report
Environments
Environment Management Best PracticesCache Environment Images in EKSImages From Authenticated External Registries
Backup and Restore
Backup StructureBackup LocationCustomize BackupsRun a Manual, On-Demand BackupRestore backups
Control Center
Control Center OverviewExport Control Center Data with The API
Troubleshooting
domino logo
About Domino
Domino Data LabKnowledge BaseData Science BlogTraining
Admin Guide
>
Installation
>
Azure Deployments
>
Provision Infrastructure and Runtime Environment

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:
  1. 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.

  2. 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.

  3. 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.

  4. Run terraform init in the folder where the main.tf file is located to initialize the modules.

  5. 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
Domino Data LabKnowledge BaseData Science BlogTraining
Copyright © 2022 Domino Data Lab. All rights reserved.