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

Update configure-pod-configmap.md (#9846)

Browse Source 
* Update configure-pod-configmap.md

i think environmental variables belong to container level, not pod level

* Lower case "container"
This commit is contained in:
fqsghostcloud
2018-08-21 03:38:43 +08:00
committed by k8s-ci-robot
parent d480a54d81
commit daff9bdaf6
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
+5 -5
View File
@@ -293,9 +293,9 @@ metadata:
``` ```
## Define Pod environment variables using ConfigMap data ## Define container environment variables using ConfigMap data
### Define a Pod environment variable with data from a single ConfigMap ### Define a container environment variable with data from a single ConfigMap
1. Define an environment variable as a key-value pair in a ConfigMap: 1. Define an environment variable as a key-value pair in a ConfigMap:
@@ -333,7 +333,7 @@ metadata:
1. Save the changes to the Pod specification. Now, the Pod's output includes `SPECIAL_LEVEL_KEY=very`. 1. Save the changes to the Pod specification. Now, the Pod's output includes `SPECIAL_LEVEL_KEY=very`.
### Define Pod environment variables with data from multiple ConfigMaps ### Define container environment variables with data from multiple ConfigMaps
1. As with the previous example, create the ConfigMaps first. 1. As with the previous example, create the ConfigMaps first.
@@ -385,7 +385,7 @@ metadata:
1. Save the changes to the Pod specification. Now, the Pod's output includes `SPECIAL_LEVEL_KEY=very` and `LOG_LEVEL=info`. 1. Save the changes to the Pod specification. Now, the Pod's output includes `SPECIAL_LEVEL_KEY=very` and `LOG_LEVEL=info`.
## Configure all key-value pairs in a ConfigMap as Pod environment variables ## Configure all key-value pairs in a ConfigMap as container environment variables
{{< note >}} {{< note >}}
**Note:** This functionality is available to users running Kubernetes v1.6 and later. **Note:** This functionality is available to users running Kubernetes v1.6 and later.
@@ -404,7 +404,7 @@ metadata:
SPECIAL_TYPE: charm SPECIAL_TYPE: charm
``` ```
1. Use `envFrom` to define all of the ConfigMap's data as Pod environment variables. The key from the ConfigMap becomes the environment variable name in the Pod. 1. Use `envFrom` to define all of the ConfigMap's data as container environment variables. The key from the ConfigMap becomes the environment variable name in the Pod.
```yaml ```yaml
apiVersion: v1 apiVersion: v1