<p>I'm in the process of learning helm and trying to deploy the mariadb on my k8s cluster running on the DigitalOcean with 1 master and 2 worker nodes with the following command:</p>
<pre><code>helm install my-mariadb bitnami/mariadb --version 12.2.2
</code></pre>
<p>This in turn created multiple resources on the cluster including the PersistenVolumeClaim, which failed to spin up and gets stuck in the Pending state with the following error: <code>no persistent volumes available for this claim and no storage class is set</code>. This error in turn keeps all the pods being in the Pending state as well.</p>
<p>Why does this resource even gets created? After looking into the templates of this helm chart <a href="https://artifacthub.io/packages/helm/bitnami/mariadb" rel="nofollow noreferrer">here</a> I can't even find the definition of it there.</p>
<p>If that's actually fine that I can't see it, then why there's no StorageClass or PersistentVolume in deployed resources? Doesn't seem right to create them manually.</p>

Konstantin
<p>So, turns out that this problem arise only on the k8s cluster that's set up with kubeadm. I've fixed this issue by creating my own PersistentVolume and PersistentVolumeClaim as described in the link provided in the comments, but then faced another problems: the mariadb pod's container crashes as it can't create <code>/bitnami/mariadb/data</code> folder due to permission error.</p>
<p>I was able to make this work on the local single-node k8s cluster without any additional steps and decided to abandon to try to resolve this issue on initial cluster, as I do this only for studying.</p>
