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
Copy file name to clipboardExpand all lines: articles/aks/long-term-support.md
+19-6Lines changed: 19 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,15 +15,15 @@ The Kubernetes community releases a new minor version approximately every four m
15
15
16
16
AKS supports versions of Kubernetes that are within this Community support window, to push bug fixes and security updates from community releases.
17
17
18
-
While innovation delivered with this release cadence provides huge benefits to you, it challenges you to keep up to date with Kubernetes releases, which can be made more difficult based on the number of AKS clusters you have to maintain.
18
+
While innovation delivered with this release cadence provides huge benefits to you, it challenges you to keep up to date with Kubernetes releases, which can be made more difficult based on the number of AKS clusters you have to maintain.
19
19
20
20
## AKS support types
21
21
22
-
After approximately one year, the Kubernetes version exits Community support and your AKS clusters are now at risk as bug fixes and security updates become unavailable.
22
+
After approximately one year, the Kubernetes version exits Community support and your AKS clusters are now at risk as bug fixes and security updates become unavailable.
23
23
24
24
AKS provides one year Community support and one year of long-term support (LTS) to back port security fixes from the community upstream in our public repository. Our upstream LTS working group contributes efforts back to the community to provide our customers with a longer support window.
25
25
26
-
LTS intends to give you an extended period of time to plan and test for upgrades over a two-year period from the General Availability of the designated Kubernetes version.
26
+
LTS intends to give you an extended period of time to plan and test for upgrades over a two-year period from the General Availability of the designated Kubernetes version.
27
27
28
28
|| Community support |Long-term support |
29
29
|---|---|---|
@@ -68,7 +68,7 @@ az aks update --resource-group myResourceGroup --name myAKSCluster --tier [free|
68
68
69
69
The AKS team currently tracks add-on versions where Kubernetes Community support exists. Once a version leaves Community support, we rely on open source projects for managed add-ons to continue that support. Due to various external factors, some add-ons and features may not support Kubernetes versions outside these upstream Community support windows.
70
70
71
-
See the following table for a list of add-ons and features that aren't supported and the reason why.
71
+
See the following table for a list of add-ons and features that aren't supported and the reason why.
72
72
73
73
| Add-on / Feature | Reason it's unsupported |
74
74
---|---|
@@ -83,7 +83,7 @@ See the following table for a list of add-ons and features that aren't supported
83
83
| AAD Pod Identity | Deprecated in place of Workload Identity |
84
84
85
85
> [!NOTE]
86
-
>You can't move your cluster to long-term support if any of these add-ons or features are enabled.
86
+
>You can't move your cluster to long-term support if any of these add-ons or features are enabled.
87
87
>Whilst these AKS managed add-ons aren't supported by Microsoft, you're able to install the Open Source versions of these on your cluster if you wish to use it past Community support.
88
88
89
89
## How we decide the next LTS version
@@ -128,6 +128,19 @@ To carry out an in-place upgrade to the latest LTS version, you need to specify
128
128
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.32.2
129
129
```
130
130
> [!NOTE]
131
-
> The next Long Term Support Version after 1.27 is to be determined. However Customers will get a minimum 6 months of overlap between 1.27 LTS and the next LTS version to plan upgrades.
131
+
> The next Long Term Support Version after 1.27 is to be determined. However Customers will get a minimum 6 months of overlap between 1.27 LTS and the next LTS version to plan upgrades.
132
132
> Kubernetes 1.32.2 is used as an example version in this article. Check the [AKS release tracker](release-tracker.md) for available Kubernetes releases.
133
133
134
+
## Frequently asked questions
135
+
136
+
### Community support for AKS 1.27 ends expires in July 2024. Can I create a new AKS cluster with version 1.27 after that date?
137
+
Yes, as long as LTS is enabled on the cluster, you can create a new AKS cluster with version 1.27 after the community support window has ended.
138
+
139
+
### Can I enable and disable LTS on AKS 1.27 after the end of community support?
140
+
You can enable the LTS support plan on AKS 1.27 after the end of community support. However, you can't disable LTS on AKS 1.27 after the end of community support.
141
+
142
+
### I have a cluster running on version 1.27. Does it mean it is automatically in LTS?
143
+
No, you need to explicitly enable LTS on the cluster to receive LTS support. Enabling LTS also requires being on the Premium tier.
144
+
145
+
### What is the pricing model for LTS?
146
+
LTS is available on the Premium tier, please refer to the [Premium tier pricing](https://azure.microsoft.com/pricing/details/kubernetes-service/) for more information.
0 commit comments