whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tidy & reword “Configure a Pod to Use a Projected Volume for Storage” (#14539)

Browse Source 
* Reference glossary entry for Secret

* Fix code block format code

* Tidying & rewording
This commit is contained in:
Tim Bannister
2019-05-27 03:21:49 +01:00
committed by Kubernetes Prow Robot
parent 1213d41cdf
commit 81dd45f6cb
1 changed files with 5 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-projected-volume-storage.md
+5 -7
View File
@@ -8,7 +8,7 @@ weight: 70
--- ---
{{% capture overview %}} {{% capture overview %}}
This page shows how to use a [`projected`](/docs/concepts/storage/volumes/#projected) volume to mount This page shows how to use a [`projected`](/docs/concepts/storage/volumes/#projected) Volume to mount
several existing volume sources into the same directory. Currently, `secret`, `configMap`, `downwardAPI`, several existing volume sources into the same directory. Currently, `secret`, `configMap`, `downwardAPI`,
and `serviceAccountToken` volumes can be projected. and `serviceAccountToken` volumes can be projected.
@@ -24,7 +24,7 @@ and `serviceAccountToken` volumes can be projected.
{{% capture steps %}} {{% capture steps %}}
## Configure a projected volume for a pod ## Configure a projected volume for a pod
In this exercise, you create username and password Secrets from local files. You then create a Pod that runs one Container, using a [`projected`](/docs/concepts/storage/volumes/#projected) Volume to mount the Secrets into the same shared directory. In this exercise, you create username and password {{< glossary_tooltip text="Secrets" term_id="secret" >}} from local files. You then create a Pod that runs one container, using a [`projected`](/docs/concepts/storage/volumes/#projected) Volume to mount the Secrets into the same shared directory.
Here is the configuration file for the Pod: Here is the configuration file for the Pod:
@@ -46,18 +46,18 @@ Here is the configuration file for the Pod:
```shell ```shell
kubectl apply -f https://k8s.io/examples/pods/storage/projected.yaml kubectl apply -f https://k8s.io/examples/pods/storage/projected.yaml
``` ```
1. Verify that the Pod's Container is running, and then watch for changes to 1. Verify that the Pod's container is running, and then watch for changes to
the Pod: the Pod:
```shell ```shell
kubectl get --watch pod test-projected-volume kubectl get --watch pod test-projected-volume
``` ```
The output looks like this: The output looks like this:
```shell ```
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
test-projected-volume 1/1 Running 0 14s test-projected-volume 1/1 Running 0 14s
``` ```
1. In another terminal, get a shell to the running Container: 1. In another terminal, get a shell to the running container:
```shell ```shell
kubectl exec -it test-projected-volume -- /bin/sh kubectl exec -it test-projected-volume -- /bin/sh
@@ -73,5 +73,3 @@ the Pod:
* Learn more about [`projected`](/docs/concepts/storage/volumes/#projected) volumes. * Learn more about [`projected`](/docs/concepts/storage/volumes/#projected) volumes.
* Read the [all-in-one volume](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/design-proposals/node/all-in-one-volume.md) design document. * Read the [all-in-one volume](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/design-proposals/node/all-in-one-volume.md) design document.
{{% /capture %}} {{% /capture %}}