Guide for deploying the Anyscale Azure AKS new cluster example from examples/azure/aks-new_cluster/. Use when the user asks about deploying, setting up, or configuring Azure AKS for Anyscale.
72
91%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Walk the user through deploying the Azure AKS example at examples/azure/aks-new_cluster/.
If $ARGUMENTS specifies a step (e.g., "terraform", "nginx", "gpu", "register", "operator"), skip to that step. Otherwise, guide from the beginning.
Ensure the user has:
az login)The user needs a terraform.tfvars file in examples/azure/aks-new_cluster/. Required variables:
azure_tenant_id = "" # az account show --query tenantId -o tsv
azure_subscription_id = "" # az account show --query id -o tsv
azure_location = "" # e.g. "Central US"
aks_cluster_name = "" # e.g. "my-anyscale-cluster"Key optional variables:
gpu_pool_configs - Map of GPU pool configs. Keys like "T4", "A100". Each needs name (max 8 lowercase alphanum chars), vm_size, product_name, gpu_count. Set to {} for CPU-only.enable_nfs - Enable NFS storage (default: false)enable_blob_driver - Enable Azure Blob CSI driver (default: false)system_vm_size - System node VM size (default: "Standard_D2s_v5")cpu_vm_size - CPU node VM size (default: "Standard_D16s_v5")Read examples/azure/aks-new_cluster/variables.tf for the full list.
Run from examples/azure/aks-new_cluster/:
terraform init
terraform plan
terraform applySave the outputs - they contain commands for the remaining steps. Key outputs:
aks_get_credentials_command - Command to authenticate kubectlanyscale_registration_command - Command to register the Anyscale cloudhelm_upgrade_command - Command to install the Anyscale operatorUse the terraform output command:
# From terraform output: aks_get_credentials_command
az aks get-credentials --resource-group <rg-name> --name <cluster-name> --overwrite-existinghelm repo add nginx https://kubernetes.github.io/ingress-nginx
helm upgrade ingress-nginx nginx/ingress-nginx \
--version 4.12.1 \
--namespace ingress-nginx \
--values sample-values_nginx.yaml \
--create-namespace \
--installThe sample values file is at examples/azure/aks-new_cluster/sample-values_nginx.yaml.
Only needed if using GPU node pools. The sample values file is at examples/azure/aks-new_cluster/sample-values_nvdp.yaml.
helm repo add nvdp https://nvidia.github.io/k8s-device-plugin
helm upgrade nvdp nvdp/nvidia-device-plugin \
--namespace nvidia-device-plugin \
--version 0.17.1 \
--values sample-values_nvdp.yaml \
--create-namespace \
--installEnsure anyscale login is done, then use the registration command from terraform output:
anyscale cloud register \
--name <anyscale_cloud_name> \
--region <region> \
--provider azure \
--compute-stack k8s \
--azure-tenant-id <tenant-id> \
--anyscale-operator-iam-identity <principal-id> \
--cloud-storage-bucket-name 'abfss://<container>@<storage-account>.dfs.core.windows.net' \
--cloud-storage-bucket-endpoint 'https://<storage-account>.blob.core.windows.net'helm repo add anyscale https://anyscale.github.io/helm-charts
helm repo updateThen use the helm command from terraform output, replacing <cloud-deployment-id> with the ID from the cloud register step:
helm upgrade anyscale-operator anyscale/anyscale-operator \
--set-string global.cloudDeploymentId=<cloud-deployment-id> \
--set-string global.controlPlaneURL=https://console.azure.anyscale.com \
--set-string global.cloudProvider=azure \
--set-string global.auth.iamIdentity=<client-id> \
--set-string global.auth.audience=api://086bc555-6989-4362-ba30-fded273e432b/.default \
--set-string workloads.serviceAccount.name=anyscale-operator \
--namespace anyscale-operator \
--create-namespace \
-iFor custom GPU types (other than T4), copy sample-custom_values.yaml to custom_values.yaml, edit it, and add -f custom_values.yaml to the helm command.
To destroy all resources:
# Remove helm releases first
helm uninstall anyscale-operator -n anyscale-operator
helm uninstall nvdp -n nvidia-device-plugin
helm uninstall ingress-nginx -n ingress-nginx
# Then destroy terraform resources
terraform destroyIf the user hits issues, check:
kubectl get nodes - Verify nodes are readykubectl get pods -A - Check for failing podsaz aks show -g <rg> -n <cluster> - Verify cluster stateb3e1428
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.