A practical AKS platform checklist before you scale

Azure Kubernetes Service (AKS) is easy to create and hard to operate well. Before you scale workloads, confirm node-pool strategy, RBAC boundaries, network policy intent, and how releases roll forward and back.

Treat observability as part of the platform: cluster signals, workload SLIs, and deploy health checks should answer “is user impact happening?” — not just “is a pod restarting?”

If you cannot explain promotion from build artifact to production in one page, fix delivery documentation before adding more microservices.