http://thenewstack.io/strategies-running-stateful-applications-kubernetes-persistent-volumes-claims/
"storage pools"
blog-post-running-stateful-application-in-kubernetes#persistent-volumes-no-association"Unlike volumes, persistent volumes are not associated with any specific pod or containers when they are created" blog-post-running-stateful-application-in-kubernetes#persistent-volumes-no-association
"Once persistence volumes (PersistentVolume) are provisioned by administrators, developers create a claim (PersistentVolumeClaim) to start consuming the storage resources exposed as persistent volumes."
blog-post-running-stateful-application-in-kubernetes#claim-same-namespace-as-podClaims must exist in the same namespace as the pod using the claim blog-post-running-stateful-application-in-kubernetes#claim-same-namespace-as-pod
blog-post-running-stateful-application-in-kubernetes#persistent-volume-definitionnetworked storage resource of the cluster that has been provisioned by an administrator. It is a resource in the cluster just like a node is a cluster resource. Are volume plugins like Volumes, but they have a distinct lifecycle that is independent of any individual pod that consumes the PV. blog-post-running-stateful-application-in-kubernetes#persistent-volume-definition
blog-post-running-stateful-application-in-kubernetes#persistent-volume-claim-definitionA PersistentVolumeClaim (PVC) is a request for storage by a developer. It is similar to a pod. Pods consume node resources and PVCs consume PV resources. Pods can request specific levels of resources (CPU and Memory). Claims can request specific storage size and access modes such as read and read-write. blog-post-running-stateful-application-in-kubernetes#persistent-volume-claim-definition
PVCs and PVs can be matched through the concept of labels and selectors. During the creation of a PV, administrators can create labels with attributes. PVCs can use selectors to ensure that they are always bound to the matching PVs with matching labels.
blog-post-running-stateful-application-in-kubernetes#persistent-volume-typesAre implemented as plugins. Kubernetes supports popular backends and distributed file systems including Amazon EBS, GCE Persistent Disks, Cinder, Azure File System, NFS, iSCSI, Gluster, and Ceph among other types. blog-post-running-stateful-application-in-kubernetes#persistent-volume-types
blog-post-running-stateful-application-in-kubernetes#storage-classEnables administrators to create multiple tiers or classes of storage they offer. Different classes map to different levels of quality-of-service, backup policies, and arbitrary policies as defined by the administrators. blog-post-running-stateful-application-in-kubernetes#storage-class
blog-post-running-stateful-application-in-kubernetes#pet-setsPet Sets, an evolving concept in Kubernetes for running highly available stateful workloads. blog-post-running-stateful-application-in-kubernetes#pet-sets