content_image/987913.jpg content_image/987914.jpg
that indicates downtime of the application. For this reason, Kubernetes documents these as Warnings , along with many other events. 

6. Check the PersistentVolumeClaims (storage) status. Blockchain is a persistent data base, so you must keep track of backing storage. To see the persistent volume claim for the helm release, click the name of the PersistentVolumeClaim item in the Persistent Volume Claim  section. In Figure 4-16 it is named blockchain-console-1 . The PersistentVolumeClaim details are displayed. 

<img src='content_image/987913.jpg'>

7. Click the Events tab to see the automated activities of the dynamic provisioner, as it creates the storage that is necessary for the blockchain console. The events are captured in Figure 4-17. 

<img src='content_image/987914.jpg'>

Often, a pod has a Pending status because it is waiting for storage provisioning. You can consult the events view in Figure 4-17 to see what is happening with this storage 

