Deploy to AKS
Use when: deploying a web app/API to AKS; containerizing for Kubernetes; generating manifests; AKS CI/CD; DS001–DS013 failures.
Not for: provisioning clusters (azure-kubernetes), AKS Automatic readiness (azure-kubernetes-automatic-readiness), non-AKS targets.
When to invoke
- "Deploy my web app to an existing AKS cluster."
- "Containerize this API and generate Kubernetes manifests."
- "Set up CI/CD for my AKS deployment."
- "My AKS deployment is failing Deployment Safeguards checks."
Workflow
Requires: existing AKS cluster, az login, kubectl configured. Follow phases/quick-deploy.md. On failure: references/rollback.md.
References
- detection.md — framework/port/health detection
- safeguards.md — DS001-DS013 checklist
- workload-identity.md — Workload Identity setup
- rollback.md — recovery procedures
- base-images.md — base image policy and
<LATEST_STABLE_*>resolution
Knowledge Packs
Load knowledge-packs/frameworks/<framework>.md per detected framework. Available: spring-boot, express, nextjs, fastapi, django, nestjs, aspnet-core, go, flask
Templates
templates/ (dockerfiles/, k8s/, github-actions/, mermaid/).
Output template
## AKS deployment result
**Status:** deployed | failed | blocked
**Summary:** <one sentence covering scope and outcome>
### Details
Detected framework, generated Dockerfile and manifests, and rollout status.
### Validation
- <check performed>: <result and evidence>
Quality gate
- Manifests satisfy the Deployment Safeguards checklist.
- Rollout status and pod health were verified after apply.
- The output follows
## Output templateexactly. - Every reported check was performed and its evidence is shown.
- Irreversible Azure actions were confirmed with the user first.