From 9fdc419652b6a9614a554cede6db98c08619356a Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Wed, 29 Mar 2017 21:52:18 +0800 Subject: [PATCH] update links update links --- ...ronment-variable-expose-pod-information.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/tasks/configure-pod-container/environment-variable-expose-pod-information.md b/docs/tasks/configure-pod-container/environment-variable-expose-pod-information.md index 10ac238c5e..71d05d2299 100644 --- a/docs/tasks/configure-pod-container/environment-variable-expose-pod-information.md +++ b/docs/tasks/configure-pod-container/environment-variable-expose-pod-information.md @@ -10,7 +10,7 @@ Pod fields and Container fields. There are two ways to expose Pod and Container fields to a running Container: environment variables and -[DownwardAPIVolumeFiles](/docs/resources-reference/v1.5/#downwardapivolumefile-v1). +[DownwardAPIVolumeFiles](/docs/resources-reference/v1.6/#downwardapivolumefile-v1-core). Together, these two ways of exposing Pod and Container fields are called the *Downward API*. @@ -31,7 +31,7 @@ Together, these two ways of exposing Pod and Container fields are called the There are two ways to expose Pod and Container fields to a running Container: * Environment variables -* [DownwardAPIVolumeFiles](/docs/resources-reference/v1.5/#downwardapivolumefile-v1) +* [DownwardAPIVolumeFiles](/docs/resources-reference/v1.6/#downwardapivolumefile-v1-core) Together, these two ways of exposing Pod and Container fields are called the *Downward API*. @@ -46,7 +46,7 @@ configuration file for the Pod: In the configuration file, you can see five environment variables. The `env` field is an array of -[EnvVars](/docs/resources-reference/v1.5/#envvar-v1). +[EnvVars](/docs/resources-reference/v1.6/#envvar-v1-core). The first element in the array specifies that the `MY_NODE_NAME` environment variable gets its value from the Pod's `spec.nodeName` field. Similarly, the other environment variables get their names from Pod fields. @@ -123,7 +123,7 @@ container: In the configuration file, you can see four environment variables. The `env` field is an array of -[EnvVars](/docs/resources-reference/v1.5/#envvar-v1). +[EnvVars](/docs/resources-reference/v1.6/#envvar-v1-core). The first element in the array specifies that the `MY_CPU_REQUEST` environment variable gets its value from the `requests.cpu` field of a Container named `test-container`. Similarly, the other environment variables get their values @@ -161,12 +161,12 @@ The output shows the values of selected environment variables: {% capture whatsnext %} * [Defining Environment Variables for a Container](/docs/tasks/configure-pod-container/define-environment-variable-container/) -* [PodSpec](/docs/resources-reference/v1.5/#podspec-v1) -* [Container](/docs/resources-reference/v1.5/#container-v1) -* [EnvVar](/docs/resources-reference/v1.5/#envvar-v1) -* [EnvVarSource](/docs/resources-reference/v1.5/#envvarsource-v1) -* [ObjectFieldSelector](/docs/resources-reference/v1.5/#objectfieldselector-v1) -* [ResourceFieldSelector](/docs/resources-reference/v1.5/#resourcefieldselector-v1) +* [PodSpec](/docs/resources-reference/v1.6/#podspec-v1-core) +* [Container](/docs/resources-reference/v1.6/#container-v1-core) +* [EnvVar](/docs/resources-reference/v1.6/#envvar-v1-core) +* [EnvVarSource](/docs/resources-reference/v1.6/#envvarsource-v1-core) +* [ObjectFieldSelector](/docs/resources-reference/v1.6/#objectfieldselector-v1-core) +* [ResourceFieldSelector](/docs/resources-reference/v1.6/#resourcefieldselector-v1-core) {% endcapture %}