Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Merged
merged 3 commits into from
Mar 20, 2018
Merged

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

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c6fe167
Update downward-api-volume-expose-pod-information.md
paul-rogers Mar 18, 2018
2d0c40f
Update downward-api-volume-expose-pod-information.md
paul-rogers Mar 18, 2018
f453615
Update downward-api-volume-expose-pod-information.md
paul-rogers Mar 18, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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" %}

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
[DownwardAPIVolumeFile](/docs/api-reference/{{page.version}}/#downwardapivolumefile-v1-core).
Expand Down Expand Up @@ -88,7 +88,7 @@ kubectl exec -it kubernetes-downwardapi-volume-example -- sh
In your shell, view the `labels` file:

```shell
/# cat /etc/labels
/# cat /etc/podinfo/labels
```

The output shows that all of the Pod's labels have been written
Expand All @@ -103,19 +103,19 @@ zone="us-est-coast"
Similarly, view the `annotations` file:

```shell
/# cat /etc/annotations
/# cat /etc/podinfo/annotations
```

View the files in the `/etc` directory:
View the files in the `/etc/podinfo` directory:

```shell
/# ls -laR /etc
/# ls -laR /etc/podinfo
```

In the output, you can see that the `labels` and `annotations` files
are in a temporary subdirectory: in this example,
`..2982_06_02_21_47_53.299460680`. In the `/etc` directory, `..data` is
a symbolic link to the temporary subdirectory. Also in the `/etc` directory,
`..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/podinfo` directory,
`labels` and `annotations` are symbolic links.

```
Expand Down Expand Up @@ -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" %}

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
DownwardAPIVolumeFile.
Expand All @@ -179,7 +179,7 @@ kubectl exec -it kubernetes-downwardapi-volume-example-2 -- sh
In your shell, view the `cpu_limit` file:

```shell
/# cat /etc/cpu_limit
/# cat /etc/podinfo/cpu_limit
```
You can use similar commands to view the `cpu_request`, `mem_limit` and
`mem_request` files.
Expand Down