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?
For a complete list of available regions, see AKS Regions and availability.
Does AKS support node autoscaling?
Does AKS support Kubernetes role-based access control (RBAC)?
Yes, Kubernetes RBAC is enabled by default when clusters are created with the Azure CLI. RBAC can be enabled for clusters created using the Azure portal or templates.
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.
Can I restrict the Kubernetes API server to only be accessible within my virtual network?
Not at this time. The Kubernetes API server is exposed as a public fully qualified domain name (FQDN). You can control access to your cluster using Kubernetes role-based access control (RBAC) and Azure Active Directory (AAD)
Are security updates applied to AKS agent nodes?
Yes, 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 each node back up with the latest Ubuntu image and a new patch version or a minor Kubernetes version. For more information, see Upgrade an AKS cluster.
- 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. OS reboots are managed across the cluster using the same cordon and drain process as a cluster upgrade.
For more information about using kured, see Apply security and kernel updates to nodes in AKS.
Why are two resource groups created with AKS?
Each AKS deployment spans two resource groups:
- The first resource group is created by you and contains only the Kubernetes service resource. The AKS resource provider automatically creates the second one during deployment, such as MC_myResourceGroup_myAKSCluster_eastus. For information on how you can specify the name of this second resource group, see the next section.
- This second resource group, such as MC_myResourceGroup_myAKSCluster_eastus, contains all of the infrastructure resources associated with the cluster. These resources include the Kubernetes node VMs, virtual networking, and storage. This separate resource group is created to simplify resource cleanup.
If you create resources for use with your AKS cluster, such as storage accounts or reserved public IP addresses, place them in the automatically generated resource group.
Can I provide my own name for the AKS infrastructure resource group?
Yes. By default, the AKS resource provider automatically creates a secondary resource group during deployment, such as MC_myResourceGroup_myAKSCluster_eastus. To comply with corporate policy, you can provide your own name for this managed cluster (MC_) resource group.
To specify your own resource group name, install the aks-preview Azure CLI extension version 0.3.2 or later. When you create an AKS cluster using the az aks create command, use the --node-resource-group parameter and specify a name for the resource group. If you use an Azure Resource Manager template to deploy an AKS cluster, you can define the resource group name using the nodeResourceGroup property.
- This resource group is automatically created by the Azure resource provider in your own subscription.
- You can only specify a custom resource group name when the cluster is created.
The following scenarios are not supported:
- You cannot specify an existing resource group for MC_ group.
- You cannot specify a different subscription for the MC_ resource group.
- You cannot change the MC_ resource group name after the cluster has been created.
- You cannot specify names for the managed resources within the MC_ resource group.
- You cannot modify or delete tags of managed resources within the MC_ resource-group (see additional information in the next section).
Can I modify tags and other properties of the AKS resources in the MC_* resource group?
Modifying and deleting the Azure-created tags and other properties of resources in the MC_* resource group can lead to unexpected results such as scaling and upgrading errors. It is supported to create and modify additional custom tags, such as to assign a business unit or cost center. Modifying the resources under the MC_* in the AKS cluster breaks the service level objective (SLO). For more information, see Does AKS offer a service level agreement?
What Kubernetes admission controllers does AKS support? Can admission controllers be added or removed?
AKS supports the following admission controllers:
It is not currently possible to modify the list of admission controllers in AKS.
Is Azure Key Vault integrated with AKS?
AKS is not currently natively integrated with Azure Key Vault. However, the Azure Key Vault FlexVolume for Kubernetes project enables direct integration from Kubernetes pods to KeyVault secrets.
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.
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 if the published service level isn't met. Since AKS itself is free, there is no cost available to reimburse and thus no formal SLA. However, AKS seeks to maintain availability of at least 99.5% for the Kubernetes API server.
Pošlji povratne informacije o:
Nalaganje povratnih informacij ...