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

Downward API concept made Correct

Browse Source
This commit is contained in:
Nitish Kumar
2022-06-20 17:58:50 +05:30
parent 88210db4b6
commit bf59d416b4
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/downward-api.md
+3 -3
View File
@@ -16,7 +16,7 @@ or API server.
An example is an existing application that assumes a particular well-known An example is an existing application that assumes a particular well-known
environment variable holds a unique identifier. One possibility is to wrap the environment variable holds a unique identifier. One possibility is to wrap the
application, but that is tedious and error prone, and it violates the goal of low application, but that is tedious and error-prone, and it violates the goal of low
coupling. A better option would be to use the Pod's name as an identifier, and coupling. A better option would be to use the Pod's name as an identifier, and
inject the Pod's name into the well-known environment variable. inject the Pod's name into the well-known environment variable.
@@ -119,8 +119,8 @@ for resources such as CPU and memory.
If CPU and memory limits are not specified for a container, and you use the If CPU and memory limits are not specified for a container, and you use the
downward API to try to expose that information, then the downward API to try to expose that information, then the
kubelet defaults to exposing the maximum allocatable value for CPU and memory kubelet defaults to exposing the maximum allocatable value for CPU and memory
(based on the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) based on the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)
calculation). calculation.
## {{% heading "whatsnext" %}} ## {{% heading "whatsnext" %}}