3

I'm currently creating a kubernetes deployment, in this deployment I have replicas value set at X and I want to create X volume that are not empty when the corresponding pod is restarted. I'm not using any cloud provider infrastructures then please avoid command using cloud services.

I've been searching answer in kubernetes doc, and my first try was to create one huge persistent volume and one persistant volume claim per pod that are bind to the pv but it's seem's to not work...

My expectations are to have X volumes that are not shared between pods and that are not dying when pod is killed because of a liveness probe. I'm aware of any possibilities that can do the trick!

yatsukino
  • 379
  • 1
  • 4
  • 13
  • 1
    If you do not use cloud provides you can use analogs for bare-metal, like `glusterfs` or `ceph`. – Arslanbekov Denis Apr 23 '19 at 08:36
  • I've heard about glusterfs but it's seem's to be very greedy resource and not that easy to deploy, I'm searching for a ligthweight if it exist... Ceph seem easier, I will try to learn about it ;) – yatsukino Apr 23 '19 at 08:45

1 Answers1

9

Deployment replicas all use the same volume. There is no possibility currently to create independent volumes per replica.

StatefulSets can define volumeClaimTemplates which means one or more independent volumes per replica. For that to work StorageClass must be capable of dynamic volume provisioning.

Vasili Angapov
  • 8,061
  • 15
  • 31