Storage providers are required when you start to use volume in Kubernetes, except for emptyDir, which will be erased when the Pod is removed. For other storage providers, folders, servers, or clusters have to be built before using them in the Pod definition. Dynamic provisioning was promoted to stable in Kubernetes version 1.6, which allows you to provision storage based on the supported cloud provider.

In this section, we'll walk through the details of emptyDir, hostPath, nfs, glusterfs, downwardAPI, and gitRepo. Secret, which is used to store credentials, will be introduced in the next section. Projected, on the other hand, is a way one could group other volume resources under one single mount point. As it only supports secret, downwardAPI, and configMap, we'll be introducing this in the Secret section, as well. The rest of the volume types have similar Kubernetes syntax, just with different backend volume implementations.