Persistent Volume Binding Issue with Qdrant Helm Chart

[abhijith-zupaloop]

Description:

Hello friends,
I am new to qdrant helm setup for k8s. I am facing a persistent volume binding issue when deploying Qdrant using the Helm chart. The pod remains in the Pending state due to unbound Persistent Volume Claims (PVCs).

Steps to Reproduce:

1. Installed Qdrant using the Helm chart:

   helm repo add qdrant https://qdrant.to/helm
   helm install qdrant qdrant/qdrant --set persistence.storageClassName=local-storage -n qdrant
   

2. My storage class configuration Link :

   kubectl get storageclasses.storage.k8s.io
   NAME                      PROVISIONER                    RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
   local-storage (default)   kubernetes.io/no-provisioner   Delete          WaitForFirstConsumer   false                  23m

3. Checked the pod status:

   kubectl get pods -n qdrant
   NAME       READY   STATUS    RESTARTS   AGE
   qdrant-0   0/1     Pending   0          14m

4. PVC Status:

   kubectl get pvc -n qdrant
   NAME                      STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS    VOLUMEATTRIBUTESCLASS   AGE
   qdrant-storage-qdrant-0   Pending                                      local-storage   <unset>                 25m

5. Issue after describing the pod:

   2 node(s) didn't find available persistent volumes to bind.