|
| 1 | +--- |
| 2 | +title: Release notes for Azure Container Storage |
| 3 | +description: Release notes for Azure Container Storage |
| 4 | +services: storage |
| 5 | +author: denisacatalinastan |
| 6 | +ms.service: azure-container-storage |
| 7 | +ms.topic: conceptual |
| 8 | +ms.date: 09/15/2024 |
| 9 | +ms.author: dstan |
| 10 | +--- |
| 11 | +# Release notes for Azure Container Storage |
| 12 | +This article provides the release notes for Azure Container Storage. It's important to note that minor releases introduce new functionalities in a backward-compatible manner (for example, 1.1.0 GA). Patch releases focus on bug fixes, security updates, and smaller improvements (for example, 1.1.1). |
| 13 | + |
| 14 | +## Supported versions |
| 15 | + |
| 16 | +The following Azure Container Storage versions are supported: |
| 17 | + |
| 18 | +| Milestone | Status | |
| 19 | +|----|----------------| |
| 20 | +|1.1.1- Hotfix | Supported | |
| 21 | +|1.1.0- General Availability| Supported | |
| 22 | + |
| 23 | +## Unsupported versions |
| 24 | +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. Please refer to the section “Upgrade a preview installation to GA” for upgrading guidance. |
| 25 | + |
| 26 | +## Minor vs. patch versions |
| 27 | +Minor versions introduce small improvements, performance enhancements, or minor new features without breaking existing functionality. For example, version 1.1.0 would move to 1.2.0. Patch versions are released more frequently than minor versions. They focus solely on bug fixes and security updates. For example, version 1.1.1 would be updated to 1.1.2. |
| 28 | + |
| 29 | +## Version 1.1.1 |
| 30 | + |
| 31 | +### Improvements and issues that are fixed |
| 32 | +- This hotfix release addresses specific issues that some customers experienced during the creation of Azure Elastic SAN storage pools. It resolves exceptions that were causing disruptions in the setup process, ensuring smoother and more reliable storage pool creation. |
| 33 | +- We've also made improvements to cluster restart scenarios. Previously, some corner-case situations caused cluster restarts to fail. This update ensures that cluster restarts are more reliable and resilient. |
| 34 | + |
| 35 | +## Version 1.1.0 |
| 36 | + |
| 37 | +### Improvements and issues that are fixed |
| 38 | +- **Security Enhancements**: This update addresses vulnerabilities in container environments, enhancing security enforcement to better protect workloads. |
| 39 | +- **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. |
| 40 | +- **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. |
| 41 | + |
| 42 | +## Upgrade a preview installation to GA |
| 43 | + |
| 44 | +If you already have a preview instance of Azure Container Storage running on your cluster, we recommend updating to the latest generally available (GA) version by running the following command: |
| 45 | +```azurecli-interactive |
| 46 | +az k8s-extension update --cluster-type managedClusters --cluster-name <cluster-name> --resource-group <resource-group> --name azurecontainerstorage --version <version> --release-train stable |
| 47 | +``` |
| 48 | + |
| 49 | +Remember to replace `<cluster-name>` and `<resource-group>` with your own values and `<version>` with the desired supported version. |
| 50 | + |
| 51 | +Please note that preview versions are no longer supported, and customers should promptly upgrade to the GA versions to ensure continued stability and access to the latest features and fixes. If you're installing Azure Container Storage for the first time on the cluster, proceed instead to [Install Azure Container Storage and create a storage pool](container-storage-aks-quickstart.md#install-azure-container-storage-and-create-a-storage-pool). You can also [Install Azure Container Storage on specific node pools](container-storage-aks-quickstart.md#install-azure-container-storage-on-specific-node-pools). |
| 52 | + |
| 53 | +## Auto-upgrade policy |
| 54 | + |
| 55 | +To receive the latest features and fixes for Azure Container Storage in future versions, you can enable auto-upgrade. However, please note that this may result in a brief interruption in the I/O operations of applications using PVs with Azure Container Storage during the upgrade process. To minimize potential impact, we recommend setting the auto-upgrade window to a time period with low activity or traffic, ensuring that upgrades occur during less critical times. |
| 56 | + |
| 57 | +To enable auto-upgrade, run the following command: |
| 58 | +```azurecli-interactive |
| 59 | +az k8s-extension update --cluster-name <cluster name> --resource-group <resource-group> --cluster-type managedClusters --auto-upgrade-minor-version true -n azurecontainerstorage |
| 60 | +``` |
| 61 | + |
| 62 | +If you would like to disable auto-upgrades, run the following command: |
| 63 | +```azurecli-interactive |
| 64 | +az k8s-extension update --cluster-name <cluster name> --resource-group <resource-group> --cluster-type managedClusters --auto-upgrade-minor-version false -n azurecontainerstorage |
| 65 | +``` |
0 commit comments