Kubernetes mariadb galera single node

Posting this as Community Wiki to expand comment and above answer.

Generally MariaDB cannot be deployed as this setup require PersistentVolume which should be created using Dynamic Provisioning as OP is using cloud environment - DigitalOcean. As PersistentVolume was not created it couldn't bound with PersistentVolumeClaim, thus pod stuck in Pedning state.

As OP stated in the bottom of the question:

The issue above was I had too many existing storages open. I now deleted them and have redeployed.

Kubernetes is not able to create it due to DigitalOcean Limits. OP stated that is using one node and already had 10 storages.

• Unverified users can have up to 10 volumes per region and up to a total of 500 GB of disk space per region.
• By default, users can create up to 100 volumes and up to a total of 16 TiB of disk space per region. You can contact our support team to request an increase. You can attach a maximum of 7 volumes to any one node or Droplet, and this limit cannot be changed.

• Pod is in "Pending" state due to the fact that the PVC "data-galera-mariadb-galera-0" is in unbound state.Once the PVC comes to Bound state then the POD will come to running state.