From 9b7af968806fe3898dcbabf6b56cef40c99bbb32 Mon Sep 17 00:00:00 2001 From: Hu Shuai Date: Wed, 10 Aug 2022 10:43:21 +0800 Subject: [PATCH] Fix broken link -- downward-api Signed-off-by: Hu Shuai --- content/en/docs/concepts/workloads/pods/downward-api.md | 4 ++-- .../downward-api-volume-expose-pod-information.md | 2 +- .../en/docs/tasks/job/indexed-parallel-processing-static.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/downward-api.md b/content/en/docs/concepts/workloads/pods/downward-api.md index fcee383c45f..c8242d8187c 100644 --- a/content/en/docs/concepts/workloads/pods/downward-api.md +++ b/content/en/docs/concepts/workloads/pods/downward-api.md @@ -22,7 +22,7 @@ inject the Pod's name into the well-known environment variable. In Kubernetes, there are two ways to expose Pod and container fields to a running container: -* as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#the-downward-api) +* as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) * as [files in a `downwardAPI` volume](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) Together, these two ways of exposing Pod and container fields are called the @@ -127,5 +127,5 @@ calculation. You can read about [`downwardAPI` volumes](/docs/concepts/storage/volumes/#downwardapi). You can try using the downward API to expose container- or Pod-level information: -* as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#the-downward-api) +* as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) * as [files in `downwardAPI` volume](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) diff --git a/content/en/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md b/content/en/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md index 42302467c1f..0062c1ccf39 100644 --- a/content/en/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md +++ b/content/en/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md @@ -13,7 +13,7 @@ A `downwardAPI` volume can expose Pod fields and container fields. In Kubernetes, there are two ways to expose Pod and container fields to a running container: -* [Environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#the-downward-api) +* [Environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) * Volume files, as explained in this task Together, these two ways of exposing Pod and container fields are called the diff --git a/content/en/docs/tasks/job/indexed-parallel-processing-static.md b/content/en/docs/tasks/job/indexed-parallel-processing-static.md index dfa222145c7..096fe5a9bea 100644 --- a/content/en/docs/tasks/job/indexed-parallel-processing-static.md +++ b/content/en/docs/tasks/job/indexed-parallel-processing-static.md @@ -19,7 +19,7 @@ to identify which part of the overall task to work on. The pod index is available in the {{< glossary_tooltip text="annotation" term_id="annotation" >}} `batch.kubernetes.io/job-completion-index` as a string representing its decimal value. In order for the containerized task process to obtain this index, -you can publish the value of the annotation using the [downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/#the-downward-api) +you can publish the value of the annotation using the [downward API](/docs/concepts/workloads/pods/downward-api/) mechanism. For convenience, the control plane automatically sets the downward API to expose the index in the `JOB_COMPLETION_INDEX` environment variable.