Instructions on using PersistentVolume don't work in availability zone aware AKS clusters

Ecosystem & Integrations Orchestration & Kubernetes
, , ,
1

FYI: the instructions for using the azureDisk volume type [2] to attach manually created [1] managed disks in Azure for AKS clusters deployed across availability zones does not work.

  1. The az create disk command lacks a --zone parameter.
  2. Even then, the azureDisk volume type (provided by the azure storage CSI driver) does not dynamically create topology.disk.csi.azure.com/zone=eastus-1 style nodeSelector labels so the mount fails with non-matching zone errors.

However, using the dynamic storage provisioning mode does work [3]. The quickstart instructions should probably be updated to reflect that, or else the helm charts updated to allow setting a nodeSelector to match the volume's zone.

Thanks,
Brian

[1] https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-cluster/create-pv/
[2] Create Helm deployment values files - Operations Manual
[3] Volume mounts and persistent volumes with the Neo4j Helm chart - Operations Manual

2

Hi Brian,

Thanks for bringing this to our notice.

We are in process of adding nodeselector feature to our helm charts. Once the feature is ready we will be definitely updating the documentation with the same.

Thanks for reporting this to us. Appreciate your time and effort.

Thanks,
Harshit