block-storage | Block storage test suite based on SNIA 's Solid State | Runtime Evironment library

I have a persistent volume defined as

I'm trying to create a PostgreSQL database in a Kubernetes cluster on Digital Ocean. To do so, I've created a StatefulSet and a Service. And to set up a volume in order to persist data, I took a look at the Add Block Storage Volumes tutorial. My k8s configurations for the StatefulSet and Service are down below.

I simply used a volumeClaimTemplates . The storage class do-block-storage exists in the cluster (volumeBindingMode is set as Immediate). The pv and the pvc are successfully created.

A volumeClaimTemplates that is responsible for locating the block storage volume by name csi-pvc. If a volume by that name does not exist, one will be created.

But my pod falls in a CrashLoopBackOff. I'm getting:0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims. Back-off restarting failed container

It is also worth saying that my cluster only has one node.

Can any please help me understand why? Thanks

Cloud platforms like Linode.com often provide hot-pluggable storage volumes that you can easily attach and detach from a Linux virtual machine without restarting it.

I am looking for a way to install Postgres so that its data and configuration ends up on a volume that I have mounted to the virtual machine. The end result should allow me to shut down the machine, detach the volume, spin up another machine with an identical version of Postgres already installed, attach the volume and have Postgres work just like it did on the old machine with all the data, file system permissions and server-wide configuration intact.

Is such a thing possible? Is there a reliable way to move installations (i.e databases and configuration, not the actual binaries) of Postgres across machines?

CLARIFICATION: the virtual machine has two disks:

• the "built-in" one which is created when the VM is created and mounted to /. That's where Postgres gets installed to and you can't move this disk.
• the hot-pluggable disk which you can easily attach and detach from a running VM. This is where I want Postgres data and configuration to be so I can just detach the disk (after shutting down the VM to prevent data loss/corruption) and attach it to another VM when I want my data to move so it behaves like it did on the old VM (i.e. no failures to start Postgres, no errors about permissions or missing files, etc).

Currently, I use this IBM Cli command to get list of volumes sanctioned:

I have a PersistentVolume with volumeModeas Block. It is defined as:

I have a yml file where I create a pvc on my provider (digital ocean)

I have a pvc on my cluster.

I can expand it on my provider (digital ocean)

but then on the cluster do I need to somehow let it know that it expanded?

here is my file that I deployed to enable the creation of the pvc

I am trying to install galera mariadb on my cluster. I only have one node, but plan to scale in the future. It seems to install fine.

When deployed it says:

On my kubernetes cluster, I mapped persistenet volumn but some how my cluster get restarted, and rabbitmq is failing to start, So I try to delete the PVC using

kubectl delete pvc pvc-475317d7-5c92-4aec-9187-5760424a2c02 comamnd,

but it stucked in Lost status, now My deployment Pod is failing with error