Rewriting the description in the background section of how the volume behaves when a pod ceases to exist.

Signed-off-by: Jailton Lopes <jailton@gmail.com>
This commit is contained in:
Jailton Lopes 2021-03-13 23:03:21 -03:00
parent 49a6df0dbc
commit 3f6343225d
No known key found for this signature in database
GPG Key ID: 263A4918DE916A62
1 changed files with 3 additions and 2 deletions

View File

@ -34,8 +34,9 @@ Kubernetes supports many types of volumes. A {{< glossary_tooltip term_id="pod"
can use any number of volume types simultaneously.
Ephemeral volume types have a lifetime of a pod, but persistent volumes exist beyond
the lifetime of a pod. Consequently, a volume outlives any containers
that run within the pod, and data is preserved across container restarts. When a
pod ceases to exist, the volume is destroyed.
that run within the pod, and data is preserved across container restarts. When a pod
ceases to exist, Kubernetes destroys ephemeral volumes; however, Kubernetes does not
destroy persistent volumes.
At its core, a volume is just a directory, possibly with some data in it, which
is accessible to the containers in a pod. How that directory comes to be, the