search

jfelten / gitea-helm-chart

MIT License
76 stars 66 forks source link

Duplicate persistent volumes created? #47

Closed nodesocket closed 4 years ago

nodesocket commented 4 years ago

Setting:

persistence:
  enabled: true
  giteaSize: 16Gi
  postgresSize: 10Gi
  accessMode: ReadWriteMany

Which seems to create two additional pods for the pvc's which is strange:

kubectl get pods
  gitea-gitea-6b4df7d759-d7gvq                 3/3     Running   0          3m59s
  pvc-50fd96b9-ae70-46cb-a609-a66ab28eb774-0   1/1     Running   0          3m59s
  pvc-70ef7171-af90-4c36-be49-c017cdabe7c6-0   1/1     Running   0          3m59s

Also duplicate pvc resources:

kubectl get pvc
  gitea-gitea                                Bound    pvc-50fd96b9-ae70-46cb-a609-a66ab28eb774   16Gi       RWX            fast           4m46s
  gitea-postgres                             Bound    pvc-70ef7171-af90-4c36-be49-c017cdabe7c6   10Gi       RWX            fast           4m46s
  pvc-50fd96b9-ae70-46cb-a609-a66ab28eb774   Bound    pvc-12d1a4f0-42e7-4495-a1bb-248916c5a27e   16Gi       RWO            fast           4m45s
  pvc-70ef7171-af90-4c36-be49-c017cdabe7c6   Bound    pvc-ca02e8c9-512c-4531-904f-589a3d0e7152   10Gi       RWO            fast           4m46s
jfelten commented 4 years ago

That is odd and I haven't seen that before mainly because I don't use PVCs. Maybe an artifact of your storage class?

nodesocket commented 4 years ago

Sorry, indeed this is caused by my storage backend StorageOS mounting as RWX — ReadWriteMany.