Robertjam954/multimodal_rag_application / .claude/skills/airunway-aks-setup
airunway-aks-setup
VerifiedSet 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".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
| references/gpu-profiles.md | markdown | 2.5 KB |
| references/model-sizing.md | markdown | 1.8 KB |
| references/powershell-notes.md | markdown | 3.1 KB |
| references/steps/step-1-verify.md | markdown | 1.9 KB |
| references/steps/step-2-controller.md | markdown | 1.0 KB |
| references/steps/step-3-gpu.md | markdown | 834 B |
| references/steps/step-4-provider.md | markdown | 2.0 KB |
| references/steps/step-5-deploy.md | markdown | 3.6 KB |
| references/steps/step-6-summary.md | markdown | 1.7 KB |
| references/troubleshooting.md | markdown | 1.5 KB |
references/steps/step-4-provider.md
View on GitHub# Step 4 — Provider Recommendation & Installation
**Goal**: Select and install the right inference provider for the detected hardware.
```bash
# Check if providers are already registered
kubectl get inferenceproviderconfigs --all-namespaces 2>/dev/null || kubectl get inferenceproviderconfigs
```
> See [powershell-notes.md](../powershell-notes.md) for the PowerShell equivalent.
**If providers already registered:** Show name and status, skip installation.
**Provider recommendation logic:**
| Hardware | Use Case | Recommended Provider |
|----------|----------|---------------------|
| CPU-only | Any | KAITO (llama.cpp) |
| GPUs | Standard inference (most users start here) | KAITO |
| GPUs | High-throughput serving with separate prefill/decode phases | Dynamo |
| GPUs | Already using Ray for ML workloads | KubeRay |
> **Default to KAITO** unless the user has a specific reason to choose otherwise. KAITO is the simplest to set up and handles most use cases. Dynamo is for teams that need to independently scale the prefill and decode stages of inference for high throughput. KubeRay is for teams already invested in the Ray ecosystem.
Present recommendation with reasoning. Ask user to confirm before installing.
**Installation** — from the **repository root**:
First, check the provider's Makefile or README for the default image:
```bash
# List available providers and their default images
ls providers/
cat providers/<provider>/Makefile | grep -E 'IMG\s*\?='
```
> See [powershell-notes.md](../powershell-notes.md) for the PowerShell equivalent.
Then deploy:
```bash
cd providers/<provider>
make deploy IMG=<image>
```
> **Tip:** If the Makefile defines a default `IMG`, you can omit the `IMG=` argument and just run `make deploy`.
**Verify registration:**
```bash
kubectl get inferenceproviderconfigs <provider> -o yaml
```
Check `status.ready: true`. If not ready within 2 minutes, inspect provider pod logs with `kubectl logs <pod-name>` and optionally use `kubectl describe pod <pod-name>` to review events and pod status.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |