Rewrite links for environment-variable-expose-pod-information to new location (#10209)
We have a redirect, so these links aren't broken, but we shouldn't rely on the redirect - that ends up with long chains of complicated redirects and makes validating the markdown harder.
This commit is contained in:
committed by
k8s-ci-robot
parent
24c8ed25da
commit
f39bc10631
+1
-1
@@ -113,7 +113,7 @@ Upon creation, the command `echo Warm greetings to The Most Honorable Kubernetes
|
||||
|
||||
{{% capture whatsnext %}}
|
||||
|
||||
* Learn more about [environment variables](/docs/tasks/configure-pod-container/environment-variable-expose-pod-information/).
|
||||
* Learn more about [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/).
|
||||
* Learn about [using secrets as environment variables](/docs/user-guide/secrets/#using-secrets-as-environment-variables).
|
||||
* See [EnvVarSource](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#envvarsource-v1-core).
|
||||
|
||||
|
||||
+1
-1
@@ -25,7 +25,7 @@ Pod fields and Container fields.
|
||||
|
||||
There are two ways to expose Pod and Container fields to a running Container:
|
||||
|
||||
* [Environment variables](/docs/tasks/configure-pod-container/environment-variable-expose-pod-information/)
|
||||
* [Environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/)
|
||||
* DownwardAPIVolumeFiles
|
||||
|
||||
Together, these two ways of exposing Pod and Container fields are called the
|
||||
|
||||
Reference in New Issue
Block a user