This reference implementation demonstrates the recommended starting (baseline) infrastructure architecture for a general purpose AKS cluster. This implementation and document is meant to guide an interdisciplinary team or multiple distinct teams like networking, security and development through the process of getting this general purpose baseline infrastructure deployed and understanding the components of it.

We walk through the deployment here in a rather verbose method to help you understand each component of this cluster, ideally teaching you about each layer and providing you with the knowledge necessary to apply it to your workload.

This project has a companion set of articles that describe challenges, design patterns, and best practices for a secure AKS cluster. You can find this article on the Azure Architecture Center at Azure Kubernetes Service (AKS) baseline cluster. If you haven't reviewed it, we suggest you read it as it will give added context to the considerations applied in this implementation. Ultimately, this is the direct implementation of that specific architectural guidance.

This architecture is infrastructure focused, more so than on workload. It concentrates on the AKS cluster itself, including concerns with identity, post-deployment configuration, secret management, and network topologies.

The implementation presented here is the minimum recommended baseline for most AKS clusters. This implementation integrates with Azure services that will deliver observability, provide a network topology that will support multiregional growth, and keep the in-cluster traffic secure as well. This architecture should be considered your starting point for preproduction and production stages.

The material here is relatively dense. We strongly encourage you to dedicate time to walk through these instructions, with a mind to learning. Therefore, we do NOT provide any "one click" deployment here. To understand the relationship between the deployed resources, we suggest that you consult the detailed architecture overview while exploring your deployment. Once you've understood the components involved and identified the shared responsibilities between your team and your great organization, it is encouraged that you build suitable, auditable deployment processes around your final infrastructure.

Throughout the reference implementation, you will see reference to Contoso Bicycle. They are a fictional small and fast-growing startup that provides online web services to its clientele on the west coast of North America. They have no on-premises datacenters and all their containerized line of business applications are now about to be orchestrated by secure, enterprise-ready AKS clusters. You can read more about their requirements and their IT team composition. This narrative provides grounding for some implementation details, naming conventions, and so on. You should adapt as you see fit.

Finally, this implementation uses the ASP.NET Core Docker sample web app as an example workload. This workload is purposefully uninteresting, as it is here exclusively to help you experience the baseline infrastructure.

• AKS v1.27
  • System and User node pool separation
  • AKS-managed Microsoft Entra ID integration
  • Microsoft Entra ID-backed Kubernetes RBAC (local user accounts disabled)
  • Managed Identities
  • Azure CNI
  • Azure Monitor for containers
• Azure Virtual Networks (hub-spoke)
  • Azure Firewall managed egress
• Azure Application Gateway (WAF)
• AKS-managed Internal Load Balancers

• Azure Workload Identity [AKS-managed add-on]
• Flux GitOps Operator [AKS-managed extension]
• ImageCleaner (Eraser) [AKS-managed add-on]
• Kubernetes Reboot Daemon
• Secrets Store CSI Driver for Kubernetes [AKS-managed add-on]
• Traefik Ingress Controller

Also do not forget to view the detailed architecture diagram to understand how the deployed resources work together in this reference architecture.

A deployment of AKS-hosted workloads typically experiences a separation of duties and lifecycle management in the area of prerequisites, the host network, the cluster infrastructure, and finally the workload itself. This reference implementation is similar. Also, be aware our primary purpose is to illustrate the topology and decisions of a baseline cluster. We feel a "step-by-step" flow will help you learn the pieces of the solution and give you insight into the relationship between them. Ultimately, lifecycle/SDLC management of your cluster and its dependencies will depend on your situation (team roles, organizational standards, and so on), and will be implemented as appropriate for your needs.

Please start this learning journey in the Preparing for the cluster section. If you follow this through to the end, you'll have our recommended baseline cluster installed, with an end-to-end sample workload running for you to reference in your own Azure subscription.

There are considerations that must be addressed before you start deploying your cluster. Do I have enough permissions in my subscription and AD tenant to do a deployment of this size? How much of this will be handled by my team directly vs having another team be responsible?

• Begin by ensuring you install and meet the prerequisites
• Procure client-facing and AKS Ingress Controller TLS certificates
• Plan your Microsoft Entra ID integration

Microsoft recommends AKS be deploy into a carefully planned network; sized appropriately for your needs and with proper network observability. Organizations typically favor a traditional hub-spoke model, which is reflected in this implementation. While this is a standard hub-spoke model, there are fundamental sizing and portioning considerations included that should be understood.

• Build the hub-spoke network

This is the heart of the guidance in this reference implementation; paired with prior network topology guidance. Here you will deploy the Azure resources for your cluster and the adjacent services such as Azure Application Gateway WAF, Azure Monitor, Azure Container Registry, and Azure Key Vault. This is also where you will validate the cluster is bootstrapped.

• Prep for cluster bootstrapping
• Deploy the AKS cluster and supporting services
• Validate cluster bootsrapping

We perform the prior steps manually here for you to understand the involved components, but we advocate for an automated DevOps process. Therefore, incorporate the prior steps into your CI/CD pipeline, as you would any infrastructure as code (IaC). See the dedicated AKS baseline automation guidance for additional details.

Without a workload deployed to the cluster it will be hard to see how these decisions come together to work as a reliable application platform for your business. The deployment of this workload would typically follow a CI/CD pattern and may involve even more advanced deployment strategies (such as blue/green). The following steps represent a manual deployment, suitable for illustration purposes of this infrastructure.

• Just like the cluster, there are workload prerequisites to address
• Configure AKS Ingress Controller with Azure Key Vault integration
• Deploy the workload

Now that the cluster and the sample workload is deployed; it's time to look at how the cluster is functioning.

• Perform end-to-end deployment validation

Most of the Azure resources deployed in the prior steps will incur ongoing charges unless removed.

• Cleanup all resources

Kubernetes and, by extension, AKS are fast-evolving products. The AKS roadmap shows how quick the product is changing. This reference implementation does take dependencies on select preview features which the AKS team describes as "Shipped & Improving." The rational behind that is that many of the preview features stay in that state for only a few months before entering GA. If you are just artchitecting your cluster today, by the time you're ready for production, there is a good chance that many of the preview features are nearing or will have hit GA.

This implementation will not include every preview feature, but instead only those that add significant value to a general-purpose cluster. There are some additional preview features you may wish to evaluate in preproduction clusters that augment your posture around security, manageability, and so on. As these features come out of preview, this reference implementation may be updated to incorporate them. Consider trying out and providing feedback on the following:

• BYO Kubelet Identity
• Planned maintenance window
• BYO CNI (--network-plugin none)
• Simplified application autoscaling with Kubernetes Event-driven Autoscaling (KEDA) add-on

The AKS baseline was used as the foundation for the following additional reference implementations. These build on the learnings of the AKS baseline and applies a specific Lens to the cluster to align a specific topology, requirement, or workload type.

• AKS baseline for multiregion clusters
• AKS baseline for regulated workloads
• AKS baseline for microservices
• Azure landing zones, enterprise-scale reference implementation using Terraform

This reference implementation intentionally does not cover more advanced scenarios. For example topics like the following are not addressed:

• Cluster lifecycle management with regard to SDLC and GitOps
• Workload SDLC integration (including concepts like Bridge to Kubernetes, advanced deployment techniques, Draft, and so on)
• Container security
• Multiple (related or unrelated) workloads owned by the same team
• Multiple workloads owned by disparate teams (AKS as a shared platform in your organization)
• Cluster-contained state (PV and PVC)
• Windows node pools
• Scale-to-zero node pools and event-based scaling (KEDA)
• Terraform
• dapr

Keep watching this space, as we build out reference implementation guidance on topics such as these. Further guidance delivered will use this baseline AKS implementation as their starting point. If you would like to contribute or suggest a pattern built on this baseline, please get in touch.

Kubernetes is a very flexible platform, giving infrastructure and application operators many choices to achieve their business and technology objectives. At points along your journey, you will need to consider when to take dependencies on Azure platform features, OSS solutions, support channels, regulatory compliance, and operational processes. We encourage this reference implementation to be the place for you to start architectural conversations within your own team; adapting to your specific requirements, and ultimately delivering a solution that delights your customers.

• Azure Kubernetes Service Documentation
• Microsoft Azure Well-Architected Framework
• Microservices architecture on AKS

Please see our Contributor guide.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

With ❤️ from Microsoft Patterns & Practices, Azure Architecture Center.