AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

airunway-aks-setup

Set up AI Runway on AKS — from bare cluster to running model. Covers cluster verification, controller install, GPU assessment, provider setup, and first deployment. WHEN: "setup AI Runway", "onboard AKS cluster", "install AI Runway", "airunway setup", "deploy model to AKS", "GPU inference on AKS", "KAITO setup on AKS", "run LLM on AKS", "vLLM on AKS", "set up model serving on AKS", "AI Runway controller".

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--airunway-aks-setup at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 12

references/steps/step-1-verify.md

Step 1 — Cluster Verification

Goal: Confirm prerequisites are met, validate the cluster connection, and inventory available nodes and GPUs.

Prerequisites

Verify required CLI tools are available before proceeding:

# Check all required tools are installed
for tool in kubectl make curl; do
  command -v "$tool" >/dev/null 2>&1 && echo "✓ $tool found" || echo "✗ $tool NOT FOUND — install before continuing"
done

See powershell-notes.md for the PowerShell equivalent.

If any tool is missing, STOP and tell the user which tools to install before continuing.

Cluster Connection

# Confirm active context
kubectl config current-context

# Inventory all nodes
kubectl get nodes -o wide

GPU Detection

# Extract GPU count and model per node (requires NVIDIA device plugin labels)
kubectl get nodes -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.allocatable['\''nvidia.com/gpu'\'']}{"\t"}{.metadata.labels['\''nvidia.com/gpu.product'\'']}{"\n"}{end}'

Note: The above command relies on nvidia.com/gpu.product node labels, which are set by the NVIDIA device plugin or GPU operator. If the output shows empty GPU fields, try the fallback:

# Fallback: check node descriptions for GPU capacity
kubectl describe nodes | grep -A 5 "Allocatable:" | grep -i nvidia

If neither approach shows GPUs but you know the nodes have GPU hardware, the NVIDIA device plugin may not be installed yet. Guide the user to install it before proceeding.

Report to user:

  • Cluster context name
  • Total node count and GPU node count
  • Per GPU type: model, count, VRAM per card, total cluster VRAM

Decision logic:

  • No kubeconfig context → STOP. Tell user to configure kubeconfig (e.g., az aks get-credentials) and retry.
  • No GPU nodes detected → Note "CPU-only cluster" and proceed; CPU-only inference is available via KAITO + llama.cpp.