persistent-volume-claims

问题 there, According to the doc: ReadWriteOnce – the volume can be mounted as read-write by a single node I created a PV based on nfs: apiVersion: v1 kind: PersistentVolume metadata: name: tspv01 spec: capacity: storage: 15Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Recycle nfs: path: /gpfs/fs01/shared/prod/democluster01/dashdb/gamestop/spv01 server: 169.55.11.79 a PVC for this PV: kind: PersistentVolumeClaim apiVersion: v1 metadata: name: sclaim spec: accessModes: -

问题 Using kubeadm to create a cluster, I have a master and work node. Now I want to share a persistentVolume in the work node, which will be bound with Postgres pod. Expecting the code will create persistentVolume in the path /postgres of work node, but it seems the hostPath will not work in a cluster, how should I assign this property to the specific node? kind: PersistentVolume apiVersion: v1 metadata: name: pv-postgres labels: type: local spec: capacity: storage: 2Gi accessModes: -

问题 The use case is like this: So we have several pods using the same persistentVolumeClaim with the accessMode set to ReadWriteOnce (because the storage class of the PersistentVolume only support ReadWriteOnce ). From https://kubernetes.io/docs/concepts/storage/persistent-volumes/, ReadWriteOnce -- the volume can be mounted as read-write by a single node So these pods should be deployed on the same node in order to access the PVC (otherwise they will fail). I would like to ask if there are any

问题 I am using a PVC with ReadWriteOnce access mode, which is used by a logstash Deployment which will run a stateful application and use this PVC.Each pod in the deployment will try to bind to the same persistent volume claim. In case of replicas > 1, it will fail (as it supports ReadWriteOnce, only the first one will be able to bind successfully). How do I specify that each pod is to be bound to a separate PV. I don't want to define 3 separate yamls for each logstash replica / instance

问题 I have a persistent volume running in the correct namespace: apiVersion: v1 kind: PersistentVolume metadata: name: raw-data spec: accessModes: - ReadWriteOnce capacity: storage: 2Gi hostPath: path: /data storageClassName: storage and would like to run a workflow that contains a volume claim template: ... volumeClaimTemplates: - metadata: name: raw-data spec: accessModes: ["ReadWriteOnce"] resources: requests: storage: 2Gi I believe my configuration is consistent with that described here https

来源： https://stackoverflow.com/questions/61187909/how-do-i-change-the-storage-class-of-existing-persistent-volumes

来源： https://stackoverflow.com/questions/62309755/how-can-i-mount-the-same-persistent-volume-on-multiple-pods

来源： https://stackoverflow.com/questions/62309755/how-can-i-mount-the-same-persistent-volume-on-multiple-pods

问题 I'm new to kubernetes and I'm trying to add a PVC in my statefulset . PV and PVC are shown here: NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE neo4j-backups 5Gi RWO Retain Bound default/backups-claim manual 1h NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE backups-claim Bound neo4j-backups 5Gi RWO manual 51m Basically I want all pods of the statefulset to see the contents of that volume as backup files are stored there. Statefulset used can be found

问题 Use case: I have a NFS directory available and I want to use it to persist data for multiple deployments & pods. I have created a PersistentVolume : apiVersion: v1 kind: PersistentVolume metadata: name: nfs-pv spec: capacity: storage: 10Gi accessModes: - ReadWriteMany nfs: server: http://mynfs.com path: /server/mount/point I want multiple deployments to be able to use this PersistentVolume , so my understanding of what is needed is that I need to create multiple PersistentVolumeClaims which