Frequently asked questions about Azure Kubernetes Service (AKS)
This article addresses frequent questions about Azure Kubernetes Service (AKS).
Which Azure regions provide the Azure Kubernetes Service (AKS) today?
See the Azure Kubernetes Service Regions and availability documentation for a complete list.
Are security updates applied to AKS agent nodes?
Azure automatically applies security patches to the nodes in your cluster on a nightly schedule. However, you are responsible for ensuring that nodes are rebooted as required. You have several options for performing node reboots:
- Manually, through the Azure portal or the Azure CLI.
- By upgrading your AKS cluster. Cluster upgrades automatically cordon and drain nodes, then bring them back up with the latest Ubuntu image. Update the OS image on your nodes without changing Kubernetes versions by specifying the current cluster version in
az aks upgrade.
- Using Kured, an open-source reboot daemon for Kubernetes. Kured runs as a DaemonSet and monitors each node for the presence of a file indicating that a reboot is required. It then orchestrates reboots across the cluster, following the same cordon and drain process described earlier.
Does AKS support node autoscaling?
Yes, autoscaling is available via the Kubernetes autoscaler as of Kubernetes 1.10.
Does AKS support Kubernetes role-based access control (RBAC)?
Yes, RBAC can be enabled when deploying an AKS cluster from the Azure CLI or Azure Resource Manager template. This functionality will soon come to the Azure portal.
What Kubernetes admission controllers does AKS support? Can this be configured?
AKS supports the following admission controllers:
It is not currently possible to modify the list of admission controllers in AKS.
Can I deploy AKS into my existing virtual network?
Yes, you can deploy an AKS cluster into an existing virtual network using the advanced networking feature.
Is Azure Key Vault integrated with AKS?
AKS is not natively integrated with Azure Key Vault at this time. However, there are community solutions like the acs-keyvault-agent from Hexadite.
Can I run Windows Server containers on AKS?
To run Windows Server containers, you need to run Windows Server-based nodes. Windows Server-based nodes are not available in AKS at this time. You can, however, use Virtual Kubelet to schedule Windows containers on Azure Container Instances and manage them as part of your AKS cluster. For more information, see Use Virtual Kubelet with AKS.
Why are two resource groups created with AKS?
Each AKS deployment spans two resource groups. The first is created by you and contains only the Kubernetes service resource. The AKS resource provider automatically creates the second one during deployment with a name like MC_myResourceGroup_myAKSCluster_eastus. The second resource group contains all of the infrastructure resources associated with the cluster, such as VMs, networking, and storage. It is created to simplify resource cleanup.
If you are creating resources that will be used with your AKS cluster, such as storage accounts or reserved public IP address, you should place them in the automatically generated resource group.
Does AKS offer a service level agreement?
In a service level agreement (SLA), the provider agrees to reimburse the customer for the cost of the service should the published service level not be met. Since AKS itself is free, there is no cost available to reimburse and thus no formal SLA. However, we seek to maintain availability of at least 99.5% for the Kubernetes API server.