persistent-volumes

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

来源： https://stackoverflow.com/questions/55619425/hostpath-persistentvolume-and-spec-capacity-storage-attribute

来源： 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

问题 Accidentally tried to delete all PV's in cluster but thankfully they still have PVC's that are bound to them so all PV's are stuck in Status: Terminating. How can I get the PV's out of the "terminating" status and back to a healthy state where it is "bound" to the pvc and is fully working? The key here is that I don't want to lose any data and I want to make sure the volumes are functional and not at risk of being terminated if claim goes away. Here are some details from a kubectl describe on

问题 Let's say I have a StatefulSet definition apiVersion: v1 kind: StatefulSet metadata: name: web spec: ... volumeClaimTemplates: — metadata: name: www spec: resources: requests: storage: 1Gi This will create me a PersistentVolumeClaim (PVC) with a PersistentVolume (PV) of 1 GiB for each pod. How can I write something like this apiVersion: v1 kind: PersistentVolumeClaim metadata: name: www spec: ... resources: requests: storage: 1Gi ... and connect it with the StatefulSet in a way that it still

问题 The problem seems to have been solved a long time ago, as the answer and the comments does not provide real solutions, I would like to get some help from experienced users The error is the following (when describing the pod, which keeps on the ContainerCreating state) : Multi-Attach error for volume "pvc-xxx" Volume is already exclusively attached to one node and can't be attached to another This all run on GKE. I had a previous cluster, and the problem never occured. I have reused the same

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql