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

Reword environment variable task

Browse Source 
- Use style guide convention for running commands
  Don't include the prompt, even for commands run inside a container
- Call a manifest a manifest
- tweak some wording
This commit is contained in:
Tim Bannister
2020-05-24 12:03:02 +01:00
parent 8c6478f327
commit 9b3e181f5a
1 changed files with 14 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/inject-data-application/define-environment-variable-container.md
+14 -6
View File
@@ -29,12 +29,12 @@ that run in the Pod. To set environment variables, include the `env` or
In this exercise, you create a Pod that runs one container. The configuration In this exercise, you create a Pod that runs one container. The configuration
file for the Pod defines an environment variable with name `DEMO_GREETING` and file for the Pod defines an environment variable with name `DEMO_GREETING` and
value `"Hello from the environment"`. Here is the configuration file for the value `"Hello from the environment"`. Here is the configuration manifest for the
Pod: Pod:
{{< codenew file="pods/inject/envars.yaml" >}} {{< codenew file="pods/inject/envars.yaml" >}}
1. Create a Pod based on the YAML configuration file: 1. Create a Pod based on that manifest:
```shell ```shell
kubectl apply -f https://k8s.io/examples/pods/inject/envars.yaml kubectl apply -f https://k8s.io/examples/pods/inject/envars.yaml
@@ -46,7 +46,7 @@ Pod:
kubectl get pods -l purpose=demonstrate-envars kubectl get pods -l purpose=demonstrate-envars
``` ```
The output is similar to this: The output is similar to:
``` ```
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
@@ -62,7 +62,8 @@ Pod:
1. In your shell, run the `printenv` command to list the environment variables. 1. In your shell, run the `printenv` command to list the environment variables.
```shell ```shell
root@envar-demo:/# printenv # Run this in the shell inside the container
printenv
``` ```
The output is similar to this: The output is similar to this:
@@ -80,12 +81,19 @@ Pod:
{{< note >}} {{< note >}}
The environment variables set using the `env` or `envFrom` field The environment variables set using the `env` or `envFrom` field
will override any environment variables specified in the container image. override any environment variables specified in the container image.
{{< /note >}} {{< /note >}}
## Using environment variables inside of your config ## Using environment variables inside of your config
Environment variables that you define in a Pod's configuration can be used elsewhere in the configuration, for example in commands and arguments that you set for the Pod's containers. In the example configuration below, the `GREETING`, `HONORIFIC`, and `NAME` environment variables are set to `Warm greetings to`, `The Most Honorable`, and `Kubernetes`, respectively. Those environment variables are then used in the CLI arguments passed to the `env-print-demo` container. Environment variables that you define in a Pod's configuration can be used
elsewhere in the configuration, for example in commands and arguments that
you set for the Pod's containers.
In the example configuration below, the `GREETING`, `HONORIFIC`, and
`NAME` environment variables are set to `Warm greetings to`, `The Most
Honorable`, and `Kubernetes`, respectively. Those environment variables
are then used in the CLI arguments passed to the `env-print-demo`
container.
```yaml ```yaml
apiVersion: v1 apiVersion: v1