As you can check you didn't indicate any StorageClass on your PVC. You need to indicate the StorageClass you used to create the PV (more info at official documentation). See the paragraph below from the official docs:
A claim can request a particular class by specifying the name of a StorageClass using the attribute storageClassName. Only PVs of the requested class, ones with the same storageClassName as the PVC, can be bound to the PVC.
Yes, you can specify the StorageClass to use on a Helm Chart. For instance, if you're using the WordPress Chart. You could specify the StorageClass by running the command below (please note that you need to replace the placeholder XXXX with the name of the StorageClass):
helm install stable/wordpress --set persistence.storageClass="XXXX" --name my-release
The parameter to modify using the --set argument depends on the "values.yaml" of the chart. On the WordPress example, you can find the whole table of parameters that you can modify on this README.md file.
On the other hand, it seems tha the PV you created it's already "bounded" by other PVC called "pv0003". Please note that one a PV is bounded with a PVC cannot be reused by another, therefore, you won't be able to use that one on your phpfpm-mariadb PVC.
Was my answer helpful? Click on