Helm doesn't wait for the installation to complete because it may take a while. The helm status command displays the latest information on a release in the same format as the output of the initial helm install command. In the output of the install command, you can see that the PersistentVolumeClaim had a PENDING status. Let's check it out now:

> helm status cranky-whippet | grep Persist -A 3
==> v1/PersistentVolumeClaim
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS  AGE
cranky-whippet-mariadbBoundpvc-9cb7e176-2a07-11e8-9bd6-080027c943848Gi             RWO                         standard                   5m  

Hooray! It is bound now, and there is a volume attached with 8 GB capacity.

Let's try to connect and verify that mariadb is indeed accessible. Let's modify the suggested commands a little bit from the notes to connect. Instead of running bash and then running mysql, we can directly run the mysql command on the container:

> kubectl run cranky-whippet-mariadb-client --rm --tty -i --image bitnami/mariadb --command -- mysql -h cranky-whippet-mariadb  

If you don't see a command prompt, try pressing Enter.

MariaDB [(none)]> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
+--------------------+
3 rows in set (0.00 sec)