January 2019
Intermediate to advanced
484 pages
11h 48m
English
Directly specifying a persistent volume in a configuration file makes a tight couple with a particular infrastructure. For the preceding example (tomcat-log volume), pdName is gce-pd-1 and Volume type is gcePersistentDisk. From a container management point of view, the pod definition shouldn't be locked into the specific environment because the infrastructure could be different based on the environment. The ideal pod definition should be flexible or abstract the actual infrastructure and specify only volume name and mount point.
Consequently, Kubernetes provides an abstraction layer that associates the pod with the persistent volume, which is called the Persistent Volume Claim ( ...
Read now
Unlock full access