Quick Deploy

Deploy an application to an existing AKS cluster with production-grade artifacts.

Section 1: Detection

Scan the project and Azure environment. Ask at most one clarifying question if genuinely ambiguous (multiple Dockerfiles, ACRs, or identities).

Framework Detection

Follow the framework detection table in references/detection.md. Scan for signal files at the project root (and one level deep for monorepos).

Port and Health Endpoint Detection

Follow the port and health endpoint detection tables in references/detection.md (first match wins). If none found, use /health as default in probes.

Existing Artifact Detection

Check for existing Dockerfile and k8s/ (or manifests/, deploy/) directories.

Azure Infrastructure Detection

kubectl config current-context
az aks show -g <rg> -n <cluster> -o json

Extract from cluster details:

• AKS flavor: nodeProvisioningProfile.mode — "Auto" = AKS Automatic, otherwise Standard
• OIDC issuer: oidcIssuerProfile.issuerUrl
• Azure RBAC: aadProfile.enableAzureRBAC

Routing Detection

az aks show -g <rg> -n <cluster> --query '{webAppRoutingEnabled: ingressProfile.webAppRouting.enabled, istioMode: serviceMeshProfile.istio.mode}' -o json

• If webAppRoutingEnabled is not true, stop with error: az aks approuting enable -g <rg> -n <cluster>
• If istioMode is "Enabled" → use Gateway API (gateway.yaml + httproute.yaml, gatewayClassName: istio)
• Otherwise → use Ingress (ingress.yaml, ingressClassName: webapprouting.kubernetes.azure.com)

az acr list -g <rg> -o json
az identity list -g <rg> -o json

ACR-AKS Integration

Verify the AKS kubelet identity can pull images from the detected ACR: