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
@@ -26,25 +26,25 @@ The following Azure Container Storage versions are supported:
26
26
27
27
The following Azure Container Storage versions are no longer supported: 1.0.6-preview, 1.0.3-preview, 1.0.2-preview, 1.0.1-preview, 1.0.0-preview. See [Upgrade a preview installation to GA](#upgrade-a-preview-installation-to-ga) for upgrading guidance.
28
28
29
-
## Major vs Minor vs. Patch releases
29
+
## Major vs. minor vs. patch releases
30
30
31
31
A **major release** introduces significant changes, often including new features, architectural updates, or breaking changes; for example, moving from version 1.1.0 to 2.0.0. A **minor release** adds enhancements or new functionality that are backward-compatible, such as moving from version 1.1.0 to 1.2.0. Lastly, a **patch release** focuses on resolving critical bugs, security issues, or minor optimizations while maintaining backward compatibility, such as moving from version 1.1.1 to 1.1.2, and is intended to ensure stability and reliability without introducing new features.
32
32
33
33
## Version 1.2.0
34
34
35
-
### Improvements and issues that are fixed
36
-
-**Bug fixes and performance improvements**: General stability improvements have been made to address key recovery issues, especially during upgrade scenarios. These updates are designed to ensure more reliable recovery processes and prevent unexpected service interruptions, delivering a smoother and more consistent experience.
37
-
-**Ephemeral Disk Performance Enhancements**: We improved overall performance for Azure Container Storage with ephemeral NVMe disks as the backing storage option, delivering up to a 100% increase in write IOPS in setups with replication enabled. For more details, read about ephemeral disk performance [using local NVMe](/azure/storage/container-storage/use-container-storage-with-local-disk#optimize-performance-when-using-local-nvme) and [using local NVMe with replication](/azure/storage/container-storage/use-container-storage-with-local-nvme-replication#optimize-performance-when-using-local-nvme).
35
+
### Improvements and issues that are fixed
38
36
37
+
-**Bug fixes and performance improvements**: We've made general stability improvements to address key recovery issues, especially during upgrade scenarios. These updates are designed to ensure more reliable recovery processes and prevent unexpected service interruptions, delivering a smoother and more consistent experience.
38
+
-**Ephemeral Disk Performance Enhancements**: We improved overall performance for Azure Container Storage with ephemeral NVMe disks as the backing storage option, delivering up to a 100% increase in write IOPS in setups with replication enabled. For more details, read about ephemeral disk performance [using local NVMe](/azure/storage/container-storage/use-container-storage-with-local-disk#optimize-performance-when-using-local-nvme) and [using local NVMe with replication](/azure/storage/container-storage/use-container-storage-with-local-nvme-replication#optimize-performance-when-using-local-nvme).
39
39
40
40
## Version 1.1.2
41
41
42
-
### Improvements and issues that are fixed
42
+
### Improvements and issues that are fixed
43
+
43
44
-**Bug fixes and performance improvements**: We improved the overall system stability by fixing general bugs and optimizing performance.
44
45
-**Security Enhancements**: This release improves security by updating package dependencies and Microsoft container images and improving container image builds to reduce dependencies.
45
46
-**Volume attachment fixes**: We also resolved an issue where volumes remained in a published state on nodes that were no longer present in the cluster, causing volume mounts to fail. This fix ensures that volumes are properly detached and reattached, allowing workloads to continue without interruptions.
46
47
47
-
48
48
## Version 1.1.1
49
49
50
50
### Improvements and issues that are fixed
@@ -60,12 +60,14 @@ A **major release** introduces significant changes, often including new features
60
60
-**Data plane stability**: We've also improved the stability of data-plane components, ensuring more reliable access to Azure Container Storage volumes and storage pools. This also enhances the management of data replication between storage nodes.
61
61
-**Volume management improvements**: The update resolves issues with volume detachment during node drain scenarios, ensuring that volumes are safely and correctly detached, and allowing workloads to migrate smoothly without interruptions or data access issues.
62
62
63
-
## Azure Container Storage Support Policy
63
+
## Azure Container Storage support policy
64
+
64
65
Azure Container Storage follows a transparent and predictable support lifecycle which is aligned with the overall AKS extension guidance on product lifecycle and support plan. In this way, we ensure you can plan your deployments and upgrades effectively. This section outlines the lifecycle, support commitment, and Kubernetes version compatibility for each Azure Container Storage release.
65
66
66
-
### Lifecycle and Patch Support
67
-
-**Major/Minor Releases**: Supported for 12 months from the release date.
68
-
-**Patch Releases**: Have the same end of life as the subsequent major/minor release.
67
+
### Lifecycle and patch support
68
+
69
+
-**Major/minor releases**: Supported for 12 months from the release date.
70
+
-**Patch releases**: Have the same end of life as the subsequent major/minor release.
69
71
70
72
| Release version | Release Date | End of Life | Supported Kubernetes Versions |
71
73
|----|----------------| ------------| -------- |
@@ -74,19 +76,22 @@ Azure Container Storage follows a transparent and predictable support lifecycle
Azure Container Storage aligns with AKS support for Kubernetes versions using the N-2 practice. For each release:
79
+
### Kubernetes version compatibility
80
+
81
+
Azure Container Storage aligns with AKS support for Kubernetes versions using the N-2 practice. When releasing a major or minor version, Azure Container Storage validates the latest three available Kubernetes versions in AKS and updates the supported Kubernetes versions accordingly. For each release:
82
+
79
83
- It supports the latest Kubernetes version generally available with AKS and the two prior versions.
80
-
- If compatibility is not possible due to deprecation or breaking API changes, the release notes will explicitly call out these exceptions.
84
+
- If compatibility isn't possible due to deprecation or breaking API changes, the release notes will explicitly call out these exceptions.
81
85
82
-
### Important Guidance for Version Synchronization
86
+
Before upgrading the Kubernetes version in your AKS cluster, we recommend checking if the version is included in the Azure Container Storage version support list. If the latest Azure Container Storage version doesn't yet support it, consider deferring the upgrade. As a general best practice, validate your workloads with the new version of Kubernetes or the new version of dependent components in a staging environment before upgrading in the production environment.
83
87
84
-
To maintain compatibility and avoid unvalidated combinations of Azure Container Storage and AKS:
88
+
### Important guidance for version synchronization
85
89
86
-
- All patch releases within a minor version (e.g., 1.1.x) will support the same Kubernetes versions as the initial minor release (e.g., 1.1.0).
90
+
To maintain compatibility and avoid unvalidated combinations of Azure Container Storage and AKS:
87
91
88
-
-New minor releases (e.g., 1.2.0 and subsequent 1.2.x) will support a sliding window of Kubernetes versions, advancing to the next version with each new minor release (e.g., 1.2.0 supports 1.28, 1.29, 1.30).
92
+
-All patch releases within a minor version (for example, 1.1.x) will support the same Kubernetes versions as the initial minor release (for example, 1.1.0).
89
93
94
+
- New minor releases (for example, 1.2.0 and subsequent 1.2.x) will support a sliding window of Kubernetes versions, advancing to the next version with each new minor release (for example, 1.2.0 supports 1.28, 1.29, and 1.30).
90
95
91
96
## Upgrade a preview installation to GA
92
97
@@ -115,7 +120,3 @@ If you would like to disable auto-upgrades, run the following command:
- How should I ensure Azure Container Storage is compatible with the latest Kubernetes version?
120
-
121
-
When releasing a major or minor version, Azure Container Storage validates the latest three available Kubernetes versions in AKS and updates the supported Kubernetes versions accordingly. Before upgrading the Kubernetes version in your AKS cluster, it is recommended to check if the version is included in the Azure Container Storage version support list. If the latest Azure Container Storage version does not yet support it, consider deferring the upgrade. As a general best practice, validate your workloads with the new version of Kubernetes or the new version of dependent components in a staging environment before upgrading in the production environment.
0 commit comments