Cluster operator and developer best practices to build and manage applications on Azure Kubernetes Service (AKS)

Building and running applications successfully in Azure Kubernetes Service (AKS) require understanding and implementation of some key considerations, including:

  • Multi-tenancy and scheduler features.
  • Cluster and pod security.
  • Business continuity and disaster recovery.

The AKS product group, engineering teams, and field teams (including global black belts [GBBs]) contributed to, wrote, and grouped the following best practices and conceptual articles. Their purpose is to help cluster operators and developers understand the considerations above and implement the appropriate features.

Cluster operator best practices

As a cluster operator, work together with application owners and developers to understand their needs. You can then use the following best practices to configure your AKS clusters as needed.

Multi-tenancy

Security

Network and storage

Running enterprise-ready workloads

Developer best practices

As a developer or application owner, you can simplify your development experience and define require application performance needs.

Kubernetes / AKS concepts

To help understand some of the features and components of these best practices, you can also see the following conceptual articles for clusters in Azure Kubernetes Service (AKS):

Next steps

If you need to get started with AKS, see the AKS quickstart using the Azure CLI, using Azure PowerShell, or using the Azure portal.