Skip to content

Commit 93ee017

Browse files
committed
update
1 parent 9a16a8e commit 93ee017

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

docs/topics/azure-stack.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -298,6 +298,7 @@ In this section, please follow the example commands to deploy a StatefulSet appl
298298
DRIVER_VERSION=v1.26.5 # if using k8s v1.26
299299
DRIVER_VERSION=v1.28.3 # if using k8s v1.27
300300
DRIVER_VERSION=v1.29.12 # if using k8s >= v1.28
301+
-DRIVER_VERSION=v1.31.5 # if using k8s >= v1.30
301302
helm repo add azuredisk-csi-driver https://raw.githubusercontent.com/kubernetes-sigs/azuredisk-csi-driver/master/charts
302303
helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver \
303304
--namespace kube-system \
@@ -347,9 +348,9 @@ The list below includes the addons currently unsupported on Azure Stack Hub:
347348
* SMB Flex Volume
348349
* Azure Monitor for containers
349350

350-
### Azure Disk CSI Driver 1.30+ not supported on Azure Stack Hub
351+
### Azure Disk CSI Driver 1.30 not supported on Azure Stack Hub
351352

352-
Azure Disk CSI Driver version 1.30 and later are not supported on Azure Stack Hub due to a dependency on a library that is not currently available on Azure Stack Hub. A fix is in progress and will be provided in a future AKS Engine release.
353+
Azure Disk CSI Driver version 1.30 and later are not supported on Azure Stack Hub. A fix is in progress and will be provided in a future AKS Engine release.
353354

354355
**Current Recommendation:** Use the compatible Azure Disk CSI Driver version specified in the [Azure Disk CSI driver version mapping table](#azure-disk-csi-driver-version-mapping) that corresponds to your cluster's Kubernetes version.
355356

@@ -365,7 +366,7 @@ Azure Disk CSI Driver version 1.30 and later are not supported on Azure Stack Hu
365366

366367
* **If installed via AKS Engine addon:**
367368
1. First, backup the deployment file: Copy the `azuredisk-csi-driver-deployment.yaml` file from `/etc/kubernetes/addons/` on the master node to a different location (either another directory on the master node or transfer it to a jump server/bastion host that can manage the cluster)
368-
2. Delete the `azuredisk-csi-driver-deployment.yaml` file from the `/etc/kubernetes/addons` directory on each master node to prevent auto-recreation by the Kubernetes addon manager
369+
2. Delete the `azuredisk-csi-driver-deployment.yaml` file from the `/etc/kubernetes/addons` directory on each master node to prevent recreation by the Kubernetes addon manager
369370
3. Remove the currently deployed driver: `kubectl delete -f azuredisk-csi-driver-deployment.yaml` (use the backup file from step 1)
370371
4. Install the correct version using the Helm approach described in the [Azure Disk CSI Driver examples section](#azure-disk-csi-driver-examples)
371372

0 commit comments

Comments
 (0)