Overview/Description
Kubernetes manages Volumes and Containers by defining a low-level representation of a StorageVolume using PersistentVolume object and binding Pod and PersistentVolume using PersistentVolumeClaim. In this course, you'll explore the applicable Reclaim policies and features of PersistentVolume, the concept of Node Affinity, the various phases of a Volume, the maximum number of volumes that can be attached to a Node, and how to configure custom limits. Additionally, you'll create a storage device using AWS EBS and a PersistentVolume that uses the EBS, a PersistentVolumeClaim to use the PersistentVolume of an AWS EBS storage device, and a PersistentVolume with an EBS via AWS API and mount it to an AWS EC2 instance. You'll also create a Pod that uses Dynamic PersistentVolumeClaim, delete PersistentVolume and PersistentVolumeClaim, change the Reclaim policy from Retain to Delete for PersistentVolume, and create a PersistentVolume using an existing Compute Engine persistent disk. Finally, you'll create a Pod with two containers to exchange data, a deployment that uses a PersistentVolumeClaim to mount it as a Volume, and a Pod to mount the NFS Volume in a Docker container to the master node. This course is part of a series that aligns with the Certified Kubernetes Administrator exam's objectives and can be used in its preparation.
describe the use of StorageClass in Kubernetes and list the fields used to dynamically provision the PersistentVolume of a class
use kubectl commands to list StorageClass and various volume types
use the kubectl command to copy local files to Pods and transfer Pod files to local storage
recognize the features of Kubernetes Volume and list the different types of volumes supported by Kubernetes
list the types of Volumes that support Volume Expansion along with the Volume Binding modes of StorageClass
create a configuration file that can be used to create a Pod with one container and configure a volume for the Pod
create a configuration file that can be used to create a hostPath PersistentVolume that can use a file or directory on the Node to emulate network-attached storage
create a configuration file that can be used to create a PersistentVolumeClaim that can request a volume of at least four gibibytes and can provide read-write access for at least one Node
create a manifest file and configure it to create a Pod that is configured to use PersistentVolumeClaim as a Volume
describe the lifecycle of a Volume and Claim that reflects the interaction between PersistentVolume and PersistentVolumeClaim
recall the concept of VolumeSnapshot along with the role of VolumeSnapshotContent and VolumeSnapshot API resources in creating VolumeSnapshots for users and administrators
describe the concept and approaches of cloning existing CSI Volumes in Kubernetes