Depending on how often you need to do this you might look at the df-pv plugin for kubectl https://github.com/yashbhutwala/kubectl-df-pv It does exactly what you are asking across all the pvs in a namespace or cluster. Once you’ve got it installed, just run kubectl df-pv and you are set.
Using EFS without automatic provisioning The EFS provisioner may be beta, but EFS itself is not. Since EFS volumes can be mounted via NFS, you can simply create a PersistentVolume with a NFS volume source manually — assuming that automatic provisioning is not a hard requirement on your side: apiVersion: v1 kind: PersistentVolume metadata: name: … Read more
The app is waiting for the Pod, while the Pod is waiting for a PersistentVolume by a PersistentVolumeClaim. However, the PersistentVolume should be prepared by the user before using. My previous YAMLs are lack of a PersistentVolume like this: kind: PersistentVolume apiVersion: v1 metadata: name: postgres-data labels: type: local spec: storageClassName: local-storage capacity: storage: 1Gi … Read more
A CronJob uses a PodTemplate as everything else based on Pods and can use Volumes. You placed your Volume specification directly in the CronJobSpec instead of the PodSpec, use it like this: apiVersion: batch/v1beta1 kind: CronJob metadata: name: update-db spec: schedule: “*/1 * * * *” jobTemplate: spec: template: spec: containers: – name: update-fingerprints image: … Read more
I think DavidO’s answer is wrong. As per Kubernetes docs on Access Modes: The access modes are: ReadWriteOnce — the volume can be mounted as read-write by a single node ReadOnlyMany — the volume can be mounted read-only by many nodes ReadWriteMany — the volume can be mounted as read-write by many nodes So AccessModes … Read more
You should use ReadWriteX when you plan to have Pods that will need to write to the volume, and not only read data from the volume. You should use XMany when you want the ability for Pods to access the given volume while those workloads are running on different nodes in the Kubernetes cluster. These … Read more
So what’s the way to correctly mount a postgresql volume using Aws EBS You are on a right path… Error you get is because you want to use root folder of mounted volume / as postgresql Data dir and postgresql complains that it is not best practice to do so since it is not empty … Read more
Basically you can’t do what you want, as the relationship PVC <–> PV is one-on-one. If NFS is the only storage you have available and would like multiple PV/PVC on one nfs export, use Dynamic Provisioning and a default storage class. It’s not in official K8s yet, but this one is in the incubator and … Read more
I can think about two options to fulfill your needs: Create a pod with the PV attached to it and use kubectl cp to copy the contents wherever you need. You could for example use a PodSpec similar to the following: apiVersion: v1 kind: Pod metadata: name: dataaccess spec: containers: – name: alpine image: alpine:latest … Read more
It is not recommended to delete pv it should be handled by cloud provisioner. If you need to remove pv just delete pod bounded to claim and then pvc. After that cloud provisioner should also remove pv as well. kubectl delete pvc –all It sometimes could take some time so be patient.