Motivation

• Provide a CI/CD flow that builds Docker images, pushes to ACR, and deploys to AKS for a dev environment sized for ~10 users.
• Include Kubernetes manifests and Prometheus scrape annotations so the service can be run and monitored in AKS.
• Document provisioning and monitoring steps (Azure Managed Prometheus/Grafana) so operators can reproduce the dev setup.

Description

• Replace the previous pipeline steps in azure-pipelines.yml with a two-stage Azure DevOps pipeline that builds and pushes a Docker image using the Docker@2 task and then applies Kubernetes manifests to AKS using Kubernetes@1 tasks, with variables for dockerRegistryServiceConnection, kubernetesServiceConnection, imageRepository, containerRegistry, dockerfilePath, tag, and namespace.
• Add Kubernetes manifests in k8s/ including namespace.yaml, deployment.yaml, service.yaml, and ingress.yaml; the deployment sets replicas: 2, resource requests/limits, readiness and liveness probes, and Prometheus scrape annotations.
• Add docs/aks-cicd.md documenting AKS/ACR provisioning commands, suggested sizing (2x Standard_B2s nodes), enabling Azure Managed Prometheus/Grafana, and setup of the Azure DevOps service connections used by the pipeline.
• Keep the ingress host and ACR/AKS connection names configurable so the pipeline and manifests can be adapted to different environments.

Testing

• No automated tests were run against these changes (documentation and manifest updates only).

Codex Task