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

Update downward-api-volume-expose-pod-information.md (#7771)

Browse Source 
* Update downward-api-volume-expose-pod-information.md

The pod spec puts the downward api files into /etc/podinfo, not directly in /etc. Updated docs to reflect this fact.

* Update downward-api-volume-expose-pod-information.md

One more spot needed fixing.

* Update downward-api-volume-expose-pod-information.md

Yet another fix, in the container example.
This commit is contained in:
Paul Rogers
2018-03-19 23:07:00 -07:00
committed by k8s-ci-robot
parent 86a525dc07
commit 35d3460679
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md
+9 -9
View File
@@ -37,7 +37,7 @@ Here is the configuration file for the Pod:
{% include code.html language="yaml" file="dapi-volume.yaml" ghlink="/docs/tasks/inject-data-application/dapi-volume.yaml" %} {% include code.html language="yaml" file="dapi-volume.yaml" ghlink="/docs/tasks/inject-data-application/dapi-volume.yaml" %}
In the configuration file, you can see that the Pod has a `downwardAPI` Volume, In the configuration file, you can see that the Pod has a `downwardAPI` Volume,
and the Container mounts the Volume at `/etc`. and the Container mounts the Volume at `/etc/podinfo`.
Look at the `items` array under `downwardAPI`. Each element of the array is a Look at the `items` array under `downwardAPI`. Each element of the array is a
[DownwardAPIVolumeFile](/docs/api-reference/{{page.version}}/#downwardapivolumefile-v1-core). [DownwardAPIVolumeFile](/docs/api-reference/{{page.version}}/#downwardapivolumefile-v1-core).
@@ -88,7 +88,7 @@ kubectl exec -it kubernetes-downwardapi-volume-example -- sh
In your shell, view the `labels` file: In your shell, view the `labels` file:
```shell ```shell
/# cat /etc/labels /# cat /etc/podinfo/labels
``` ```
The output shows that all of the Pod's labels have been written The output shows that all of the Pod's labels have been written
@@ -103,19 +103,19 @@ zone="us-est-coast"
Similarly, view the `annotations` file: Similarly, view the `annotations` file:
```shell ```shell
/# cat /etc/annotations /# cat /etc/podinfo/annotations
``` ```
View the files in the `/etc` directory: View the files in the `/etc/podinfo` directory:
```shell ```shell
/# ls -laR /etc /# ls -laR /etc/podinfo
``` ```
In the output, you can see that the `labels` and `annotations` files In the output, you can see that the `labels` and `annotations` files
are in a temporary subdirectory: in this example, are in a temporary subdirectory: in this example,
`..2982_06_02_21_47_53.299460680`. In the `/etc` directory, `..data` is `..2982_06_02_21_47_53.299460680`. In the `/etc/podinfo` directory, `..data` is
a symbolic link to the temporary subdirectory. Also in the `/etc` directory, a symbolic link to the temporary subdirectory. Also in the `/etc/podinfo` directory,
`labels` and `annotations` are symbolic links. `labels` and `annotations` are symbolic links.
``` ```
@@ -155,7 +155,7 @@ file for a Pod that has one Container:
{% include code.html language="yaml" file="dapi-volume-resources.yaml" ghlink="/docs/tasks/inject-data-application/dapi-volume-resources.yaml" %} {% include code.html language="yaml" file="dapi-volume-resources.yaml" ghlink="/docs/tasks/inject-data-application/dapi-volume-resources.yaml" %}
In the configuration file, you can see that the Pod has a `downwardAPI` Volume, In the configuration file, you can see that the Pod has a `downwardAPI` Volume,
and the Container mounts the Volume at `/etc`. and the Container mounts the Volume at `/etc/podinfo`.
Look at the `items` array under `downwardAPI`. Each element of the array is a Look at the `items` array under `downwardAPI`. Each element of the array is a
DownwardAPIVolumeFile. DownwardAPIVolumeFile.
@@ -179,7 +179,7 @@ kubectl exec -it kubernetes-downwardapi-volume-example-2 -- sh
In your shell, view the `cpu_limit` file: In your shell, view the `cpu_limit` file:
```shell ```shell
/# cat /etc/cpu_limit /# cat /etc/podinfo/cpu_limit
``` ```
You can use similar commands to view the `cpu_request`, `mem_limit` and You can use similar commands to view the `cpu_request`, `mem_limit` and
`mem_request` files. `mem_request` files.