Скачать или смотреть Kubernetes Volumes explained | Persistent Volume, Persistent Volume Claim & Storage Class

Kubernetes Volumes explained | Persistent Volume, Persistent Volume Claim & Storage Class

On-disk files in a container are ephemeral, which presents some problems for non-trivial applications when running in containers. One problem is the loss of files when a container crashes. The kubelet restarts the container but with a clean state. A second problem occurs when sharing files between containers running together in a Pod. The Kubernetes volume abstraction solves both of these problems. Familiarity with Pods is suggested.

Types of Volumes
Kubernetes supports several types of volumes.

awsElasticBlockStore
An awsElasticBlockStore volume mounts an Amazon Web Services (AWS) EBS volume into your pod. Unlike emptyDir, which is erased when a pod is removed, the contents of an EBS volume are persisted and the volume is unmounted. This means that an EBS volume can be pre-populated with data, and that data can be shared between pods.

Note: You must create an EBS volume by using aws ec2 create-volume or the AWS API before you can use it.
There are some restrictions when using an awsElasticBlockStore volume:

the nodes on which pods are running must be AWS EC2 instances
those instances need to be in the same region and availability zone as the EBS volume
EBS only supports a single EC2 instance mounting a volume

🚩 Connect with me on social:
🔖 Visit Website - https://www.maddysworld.net/
🔖 Blog - https://www.maddysworld.co.in/
🔖 Instagram -   / maddy_sworld  
🔖 Facebook Page -   / maddy.w.313  
🔖 Linkedin -   / maddy-s-world-0637371a9  

🔔 Subscribe to my YouTube channel
   / maddysworld  

Join this channel to get access to perks:
   / @maddysworld  

🎬 Want to watch again? Navigate back to my YouTube channel quickly
   / maddysworld