Expand Volume

  1. Create AKS cluster with 3 nodes and install Longhorn.

  2. Create deployment and write some data to it.

  3. In Longhorn, set replica-replenishment-wait-interval to 0.

  4. Add a new node-pool. Later Longhorn components will be automatically deployed on the nodes in this pool.

    AKS_NODEPOOL_NAME_NEW=<new-nodepool-name>
AKS_RESOURCE_GROUP=<aks-resource-group>
AKS_CLUSTER_NAME=<aks-cluster-name>
AKS_DISK_SIZE_NEW=<new-disk-size-in-gb>
AKS_NODE_NUM=<number-of-nodes>
AKS_K8S_VERSION=<kubernetes-version>
az aks nodepool add \
  --resource-group ${AKS_RESOURCE_GROUP} \
  --cluster-name ${AKS_CLUSTER_NAME} \
  --name ${AKS_NODEPOOL_NAME_NEW} \
  --node-count ${AKS_NODE_NUM} \
  --node-osdisk-size ${AKS_DISK_SIZE_NEW} \
  --kubernetes-version ${AKS_K8S_VERSION} \
  --mode System

  5. Using Longhorn UI to disable the disk scheduling and request eviction for nodes in the old node-pool.

  6. Cordon and drain Kubernetes nodes in the old node-pool.

    AKS_NODEPOOL_NAME_OLD=<old-nodepool-name>
for n in `kubectl get nodes | grep ${AKS_NODEPOOL_NAME_OLD}- | awk '{print $1}'`; do
  kubectl cordon $n && \
  kubectl drain $n --ignore-daemonsets --pod-selector='app!=csi-attacher,app!=csi-provisioner' --delete-emptydir-data
done

  7. Delete old node-pool.

    az aks nodepool delete \
  --cluster-name ${AKS_CLUSTER_NAME} \
  --name ${AKS_NODEPOOL_NAME_OLD} \
  --resource-group ${AKS_RESOURCE_GROUP}

  8. Check the deployment in step 2 still running and data exist, and check volume expanded as expected through Longhorn UI.

[Edit]