Skip to content

Commit 3f63432

Browse files
committed
Rewriting the description in the background section of how the volume behaves when a pod ceases to exist.
Signed-off-by: Jailton Lopes <[email protected]>
1 parent 49a6df0 commit 3f63432

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

content/en/docs/concepts/storage/volumes.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,9 @@ Kubernetes supports many types of volumes. A {{< glossary_tooltip term_id="pod"
3434
can use any number of volume types simultaneously.
3535
Ephemeral volume types have a lifetime of a pod, but persistent volumes exist beyond
3636
the lifetime of a pod. Consequently, a volume outlives any containers
37-
that run within the pod, and data is preserved across container restarts. When a
38-
pod ceases to exist, the volume is destroyed.
37+
that run within the pod, and data is preserved across container restarts. When a pod
38+
ceases to exist, Kubernetes destroys ephemeral volumes; however, Kubernetes does not
39+
destroy persistent volumes.
3940

4041
At its core, a volume is just a directory, possibly with some data in it, which
4142
is accessible to the containers in a pod. How that directory comes to be, the

0 commit comments

Comments
 (0)