Cannot bind to existing PVC

Support
1

For testing purposes, I’m trying to deploy weaviate onto a docker desktop instance of kubernetes

I’ve set up a PVC to be used, and confirmed that it works with other pods, before resetting my cluster and trying again.

The PV file (with the directory edited)

apiVersion: v1
kind: PersistentVolume
metadata:
  name: task-pv-volume
  labels:
    type: local
spec:
  storageClassName: hostpath
  capacity:
    storage: 32Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: /run/desktop/mnt/host/.../weaviate_pv

the PVC

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: task-pv-claim
spec:
  storageClassName: hostpath
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 32Gi

and the storage section in values.yaml

storage:
  fullnameOverride: task-pv-claim

I’ve trying deploying the PV and the PVC to both the default namespace and the weaviate namespace, but I can’t seem to get weaviate to use the PVC as opposed to creating a new claim.

EDIT:

these are the standard commands I use to get things going:

kubectl create namespace weaviate
kubectl apply -f pv.yaml --namespace "weaviate"
kubectl apply -f pvc.yaml --namespace "weaviate"
helm upgrade --install "weaviate" weaviate/weaviate --namespace "weaviate" --values ./values.yaml

also running kubectl get pvc --namespace "weaviate" gives me:

NAME                       STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
task-pv-claim              Bound    task-pv-volume                             32Gi       RWO            hostpath       2s
weaviate-data-weaviate-0   Bound    pvc-d5690f50-9822-4369-a4b0-eb584140a7f6   32Gi       RWO            hostpath       2s
2

Hi @chirag-phlo !

Sorry for the delay here. Missed this one :frowning:

Were you able to solve this? This seems more a K8s question instead of a Weaviate one.

I am no K8s expert (still learning it) but I may be able to proxy this to some more experienced colleagues.

Thanks!