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
It is unclear from AKS releases what version to expect to get for the Blob Storage CSI driver in AKS clusters 1.29. It was indicated in #4242 in a comment that upgrading to AKS 1.29 would resolve the issue, but that is not the case for all our clusters.
We have 3 AKS clusters in Norway East, all running AKS 1.29. One of the clusters has the Blob Storage CSI driver version 1.24.1 running, while the other two have the Blob Storage CSI driver version 1.23.4 running. It's the latter two clusters that are experiencing the issue.
To Reproduce
Have the private DNS zone privatelink.blob.core.windows.net already existing in the resource group of the AKS vnet.
Assign the AKS identity Contributor role in the resource group hosting the AKS vnet.
Have the blob storage CSI driver enabled: az aks update --enable-blob-driver
Deploy sc + pvc + deployment to AKS (see examples of our declarations under Additional context below)
Expected behavior
Storage account + blob is created
Private DNS zone is updated with a record for the blob
The AKS deployment provisions successfully
Screenshots
Not applicable.
Environment
AKS 1.29.4 (cluster kubernetesVersion and node pool orchestratorVersion, all 3 clusters)
Node image version AKSUbuntu-2204gen2containerd-202405.27.0 (all 3 clusters)
Azure Blob Storage CSI driver for Kubernetes version 1.23.4 (for clusters with issues)
v1.24.1 has a critical bug (token expire issue), we have released v1.23.5 to fix this issue: https://github.com/kubernetes-sigs/blob-csi-driver/releases/tag/v1.23.5, the rollout on aks would still take a few weeks, just email me your cluster fqdn, I could upgrade your cluster with v1.23.5 in advance if you cannot wait, thanks.
Describe the bug
We are still observing #4242 in our AKS
1.29
clusters in Norway East.The cause of the issue is a bug introduced in Azure Blob Storage CSI driver for Kubernetes version 1.23.4.
The bug is fixed in driver versions:
AKS releases shows that the Blob Storage CSI driver was bumped to
1.24.1
for AKS1.28
as part of AKS v20240428. The AKS Release tracker shows Norway East currently have v20240513 deployed.It is unclear from AKS releases what version to expect to get for the Blob Storage CSI driver in AKS clusters
1.29
. It was indicated in #4242 in a comment that upgrading to AKS1.29
would resolve the issue, but that is not the case for all our clusters.We have 3 AKS clusters in Norway East, all running AKS
1.29
. One of the clusters has the Blob Storage CSI driver version1.24.1
running, while the other two have the Blob Storage CSI driver version1.23.4
running. It's the latter two clusters that are experiencing the issue.To Reproduce
privatelink.blob.core.windows.net
already existing in the resource group of the AKS vnet.Contributor
role in the resource group hosting the AKS vnet.az aks update --enable-blob-driver
Expected behavior
Screenshots
Not applicable.
Environment
1.29.4
(clusterkubernetesVersion
and node poolorchestratorVersion
, all 3 clusters)AKSUbuntu-2204gen2containerd-202405.27.0
(all 3 clusters)1.23.4
(for clusters with issues)Additional context
custom StorageClass
PersistentVolumeClaim
Deployment (not a complete example, just the important parts)
The text was updated successfully, but these errors were encountered: