From aa2f96c10eb85c93fd7939fe784d47b6f40e7c6c Mon Sep 17 00:00:00 2001 From: Jared Date: Tue, 5 Dec 2017 14:37:16 -0600 Subject: [PATCH 1/3] Volume glossary entry https://github.com/kubernetes/website/issues/5993 It's my first stab at a glossary entry. --- _data/glossary/volume.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 _data/glossary/volume.yaml diff --git a/_data/glossary/volume.yaml b/_data/glossary/volume.yaml new file mode 100644 index 0000000000..8ce523282e --- /dev/null +++ b/_data/glossary/volume.yaml @@ -0,0 +1,18 @@ +id: volume +name: Volume +full-link: kubernetes.io/docs/concepts/storage/volumes/ +related: +- pod +- container +- secret +tags: +- core-object +- fundamental +short-description: > + A volume is a directory containing data, which is accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. +long-description: > + A volume is a directory containing data, which is accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. + A Kubernetes volume lives as long as the {% glossary_tooltip text="pod" term_id="pod" %} that encloses it. + Consequently, a volume outlives any {% glossary_tooltip text="containers" term_id="container" %} that run within the + {% glossary_tooltip text="pod" term_id="pod" %}, and data is preserved across + {% glossary_tooltip text="container" term_id="container" %} restarts. From 9d6890889f2e66655df30d9f20e4a7ffed7d10d1 Mon Sep 17 00:00:00 2001 From: Jared Date: Tue, 5 Dec 2017 14:41:38 -0600 Subject: [PATCH 2/3] Update volume.yaml --- _data/glossary/volume.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/_data/glossary/volume.yaml b/_data/glossary/volume.yaml index 8ce523282e..9a5cef7063 100644 --- a/_data/glossary/volume.yaml +++ b/_data/glossary/volume.yaml @@ -11,7 +11,6 @@ tags: short-description: > A volume is a directory containing data, which is accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. long-description: > - A volume is a directory containing data, which is accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. A Kubernetes volume lives as long as the {% glossary_tooltip text="pod" term_id="pod" %} that encloses it. Consequently, a volume outlives any {% glossary_tooltip text="containers" term_id="container" %} that run within the {% glossary_tooltip text="pod" term_id="pod" %}, and data is preserved across From d11c533bbd6366c595a461301189a2b3e1ac3fc2 Mon Sep 17 00:00:00 2001 From: Jared Date: Tue, 5 Dec 2017 14:48:26 -0600 Subject: [PATCH 3/3] Update volume.yaml --- _data/glossary/volume.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_data/glossary/volume.yaml b/_data/glossary/volume.yaml index 9a5cef7063..60d0fe231e 100644 --- a/_data/glossary/volume.yaml +++ b/_data/glossary/volume.yaml @@ -9,7 +9,7 @@ tags: - core-object - fundamental short-description: > - A volume is a directory containing data, which is accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. + A directory containing data, accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. long-description: > A Kubernetes volume lives as long as the {% glossary_tooltip text="pod" term_id="pod" %} that encloses it. Consequently, a volume outlives any {% glossary_tooltip text="containers" term_id="container" %} that run within the