You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article addresses frequent questions about Azure Kubernetes Service (AKS).
12
12
13
-
## Pricing and platform support
14
-
15
-
### Can I run Windows Server containers on AKS?
16
-
17
-
Yes, Windows Server containers are available on AKS. To run Windows Server containers in AKS, you create a node pool that runs Windows Server as the guest OS. Windows Server containers can use only Windows Server 2019. To get started, see [Create an AKS cluster with a Windows Server node pool](./learn/quick-windows-container-deploy-cli.md).
18
-
19
-
Windows Server support for node pool includes some limitations that are part of the upstream Windows Server in Kubernetes project. For more information on these limitations, see [Windows Server containers in AKS limitations][aks-windows-limitations].
13
+
## Support
20
14
21
15
### Does AKS offer a service-level agreement?
22
16
23
17
AKS provides SLA guarantees in the [Standard pricing tier with the Uptime SLA feature][pricing-tiers].
24
18
25
19
The Free pricing tier doesn't have an associated Service Level *Agreement*, but has a Service Level *Objective* of 99.5%. Transient connectivity issues are observed if there's an upgrade, unhealthy underlay nodes, platform maintenance, an application overwhelms the API Server with requests, etc. For mission-critical and production workloads, or if your workload doesn't tolerate API Server restarts, we recommend using the Standard tier, which includes Uptime SLA.
26
20
21
+
### What is platform support, and what does it include?
22
+
23
+
Platform support is a reduced support plan for unsupported "N-3" version clusters. Platform support only includes Azure infrastructure support. Platform support doesn't include anything related to the following:
24
+
25
+
- Kubernetes functionality and components
26
+
- Cluster or node pool creation
27
+
- Hotfixes
28
+
- Bug fixes
29
+
- Security patches
30
+
- Retired components
31
+
32
+
For more information on restrictions, see the [platform support policy][supported-kubernetes-versions].
33
+
34
+
AKS relies on the releases and patches from [Kubernetes](https://kubernetes.io/releases/), which is an Open Source project that only supports a sliding window of *three* minor versions. AKS can only guarantee [full support](./supported-kubernetes-versions.md#kubernetes-version-support-policy) while those versions are being serviced upstream. Since there's no more patches being produced upstream, AKS can either leave those versions unpatched or fork. Due to this limitation, platform support doesn't support anything from relying on kubernetes upstream.
35
+
36
+
### Does AKS automatically upgrade my unsupported clusters?
37
+
38
+
AKS initiates auto-upgrades for unsupported clusters. When a cluster in an n-3 version (where n is the latest supported AKS GA minor version) is about to drop to n-4, AKS automatically upgrades the cluster to n-2 to remain in an AKS support [policy][supported-kubernetes-versions]. Automatically upgrading a platform supported cluster to a supported version is enabled by default.
39
+
40
+
For example, kubernetes v1.25 upgrades to v1.26 during the v1.29 GA release. To minimize disruptions, set up [maintenance windows][planned-maintenance]. See [auto-upgrade][auto-upgrade-cluster] for details on automatic upgrade channels.
41
+
42
+
### Can I run Windows Server containers on AKS?
43
+
44
+
Yes, Windows Server containers are available on AKS. To run Windows Server containers in AKS, you create a node pool that runs Windows Server as the guest OS. Windows Server containers can use only Windows Server 2019. To get started, see [Create an AKS cluster with a Windows Server node pool](./learn/quick-windows-container-deploy-cli.md).
45
+
46
+
Windows Server support for node pool includes some limitations that are part of the upstream Windows Server in Kubernetes project. For more information on these limitations, see [Windows Server containers in AKS limitations][aks-windows-limitations].
47
+
27
48
### Can I apply Azure reservation discounts to my AKS agent nodes?
28
49
29
50
AKS agent nodes are billed as standard Azure virtual machines. If you purchased [Azure reservations][reservation-discounts] for the VM size that you're using in AKS, those discounts are automatically applied.
30
51
52
+
## Operations
53
+
31
54
### Can I move/migrate my cluster between Azure tenants?
32
55
33
56
Moving your AKS cluster between tenants is currently unsupported.
@@ -44,6 +67,30 @@ Moving your AKS cluster and its associated resources between Azure subscriptions
44
67
45
68
Moving or renaming your AKS cluster and its associated resources isn't supported.
46
69
70
+
### Can I restore my cluster after deleting it?
71
+
72
+
No, you cannot restore your cluster after deleting it. When you delete your cluster, the node resource group and all its resources are also deleted. An example of the second resource group is *MC_myResourceGroup_myAKSCluster_eastus*.
73
+
74
+
If you want to keep any of your resources, move them to another resource group before deleting your cluster. If you want to protect against accidental deletes, you can lock the AKS managed resource group hosting your cluster resources using [Node resource group lockdown][node-resource-group-lockdown].
75
+
76
+
### Can I scale my AKS cluster to zero?
77
+
78
+
You can completely [stop a running AKS cluster](start-stop-cluster.md), saving on the respective compute costs. Additionally, you may also choose to [scale or autoscale all or specific `User` node pools](scale-cluster.md#scale-user-node-pools-to-0) to 0, maintaining only the necessary cluster configuration.
79
+
80
+
You can't directly scale [system node pools](use-system-pools.md) to zero.
81
+
82
+
### Can I use the Virtual Machine Scale Set APIs to scale manually?
83
+
84
+
No, scale operations by using the Virtual Machine Scale Set APIs aren't supported. Use the AKS APIs (`az aks scale`).
85
+
86
+
### Can I use Virtual Machine Scale Sets to manually scale to zero nodes?
87
+
88
+
No, scale operations by using the Virtual Machine Scale Set APIs aren't supported. You can use the AKS API to scale to zero nonsystem node pools or [stop your cluster](start-stop-cluster.md) instead.
89
+
90
+
### Can I stop or de-allocate all my VMs?
91
+
92
+
While AKS has resilience mechanisms to withstand such a config and recover from it, it isn't a supported configuration. [Stop your cluster](start-stop-cluster.md) instead.
93
+
47
94
### Why are two resource groups created with AKS?
48
95
49
96
AKS builds upon many Azure infrastructure resources, including Virtual Machine Scale Sets, virtual networks, and managed disks. These integrations enable you to apply many of the core capabilities of the Azure platform within the managed Kubernetes environment provided by AKS. For example, most Azure virtual machine types can be used directly with AKS and Azure Reservations can be used to receive discounts on those resources automatically.
@@ -82,51 +129,6 @@ Azure-created tags are created for their respective Azure Services and should al
82
129
> [!NOTE]
83
130
> In the past, the tag name "Owner" was reserved for AKS to manage the public IP that is assigned on front end IP of the loadbalancer. Now, services follow use the `aks-managed` prefix. For legacy resources, don't use Azure policies to apply the "Owner" tag name. Otherwise, all resources on your AKS cluster deployment and update operations will break. This does not apply to newly created resources.
84
131
85
-
### What is platform support, and what does it include?
86
-
87
-
Platform support is a reduced support plan for unsupported "N-3" version clusters. Platform support only includes Azure infrastructure support. Platform support doesn't include anything related to the following:
88
-
89
-
- Kubernetes functionality and components
90
-
- Cluster or node pool creation
91
-
- Hotfixes
92
-
- Bug fixes
93
-
- Security patches
94
-
- Retired components
95
-
96
-
For more information on restrictions, see the [platform support policy][supported-kubernetes-versions].
97
-
98
-
AKS relies on the releases and patches from [Kubernetes](https://kubernetes.io/releases/), which is an Open Source project that only supports a sliding window of *three* minor versions. AKS can only guarantee [full support](./supported-kubernetes-versions.md#kubernetes-version-support-policy) while those versions are being serviced upstream. Since there's no more patches being produced upstream, AKS can either leave those versions unpatched or fork. Due to this limitation, platform support doesn't support anything from relying on kubernetes upstream.
99
-
100
-
### Does AKS automatically upgrade my unsupported clusters?
101
-
102
-
AKS initiates auto-upgrades for unsupported clusters. When a cluster in an n-3 version (where n is the latest supported AKS GA minor version) is about to drop to n-4, AKS automatically upgrades the cluster to n-2 to remain in an AKS support [policy][supported-kubernetes-versions]. Automatically upgrading a platform supported cluster to a supported version is enabled by default.
103
-
104
-
For example, kubernetes v1.25 upgrades to v1.26 during the v1.29 GA release. To minimize disruptions, set up [maintenance windows][planned-maintenance]. See [auto-upgrade][auto-upgrade-cluster] for details on automatic upgrade channels.
105
-
106
-
### Can I restore my cluster after deleting it?
107
-
108
-
No, you cannot restore your cluster after deleting it. When you delete your cluster, the node resource group and all its resources are also deleted. An example of the second resource group is *MC_myResourceGroup_myAKSCluster_eastus*.
109
-
110
-
If you want to keep any of your resources, move them to another resource group before deleting your cluster. If you want to protect against accidental deletes, you can lock the AKS managed resource group hosting your cluster resources using [Node resource group lockdown][node-resource-group-lockdown].
111
-
112
-
### Can I scale my AKS cluster to zero?
113
-
114
-
You can completely [stop a running AKS cluster](start-stop-cluster.md), saving on the respective compute costs. Additionally, you may also choose to [scale or autoscale all or specific `User` node pools](scale-cluster.md#scale-user-node-pools-to-0) to 0, maintaining only the necessary cluster configuration.
115
-
116
-
You can't directly scale [system node pools](use-system-pools.md) to zero.
117
-
118
-
### Can I use the Virtual Machine Scale Set APIs to scale manually?
119
-
120
-
No, scale operations by using the Virtual Machine Scale Set APIs aren't supported. Use the AKS APIs (`az aks scale`).
121
-
122
-
### Can I use Virtual Machine Scale Sets to manually scale to zero nodes?
123
-
124
-
No, scale operations by using the Virtual Machine Scale Set APIs aren't supported. You can use the AKS API to scale to zero nonsystem node pools or [stop your cluster](start-stop-cluster.md) instead.
125
-
126
-
### Can I stop or de-allocate all my VMs?
127
-
128
-
While AKS has resilience mechanisms to withstand such a config and recover from it, it isn't a supported configuration. [Stop your cluster](start-stop-cluster.md) instead.
0 commit comments