Using ConfigMaps as environment variables in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a ConfigMap in Kubernetes?

A ConfigMap is a Kubernetes object that stores configuration data as key-value pairs. It allows you to separate configuration from container images, making apps easier to manage and update.

beginner

How do you use a ConfigMap as environment variables in a Pod?

You reference the ConfigMap in the Pod's container spec under envFrom or env. This injects the ConfigMap's keys as environment variables inside the container.

intermediate

What is the difference between envFrom and env when using ConfigMaps?

envFrom imports all keys from a ConfigMap as environment variables. env lets you specify individual keys from the ConfigMap as environment variables with custom names.

beginner

Show a simple YAML snippet to use a ConfigMap named app-config as environment variables in a Pod.

apiVersion: v1 kind: Pod metadata: name: example-pod spec: containers: - name: example-container image: nginx envFrom: - configMapRef: name: app-config

beginner

Why is it useful to use ConfigMaps for environment variables instead of hardcoding values in container images?

Using ConfigMaps lets you change configuration without rebuilding images. It keeps your containers portable and your configuration flexible, like changing settings without opening the app.

What Kubernetes object stores key-value pairs for configuration?

A Service

B Pod

C Deployment

D ConfigMap

ConfigMap is the Kubernetes object designed to hold configuration data as key-value pairs.

Which field in a Pod spec imports all ConfigMap keys as environment variables?

A envFrom

B volumes

C env

D configMapRef

envFrom imports all keys from a ConfigMap as environment variables.

How do you specify a single ConfigMap key as an environment variable with a custom name?

A Use <code>envFrom</code>

B Use <code>env</code> with <code>valueFrom.configMapKeyRef</code>

C Use <code>volumes</code>

D Use <code>configMapRef</code> in <code>volumes</code>

You use env with valueFrom.configMapKeyRef to map a single key to an environment variable.

What happens if you update a ConfigMap used as environment variables in a running Pod?

A The Pod environment variables do NOT update automatically

B The Pod environment variables update immediately

C The Pod restarts automatically

D The ConfigMap cannot be updated

Environment variables are set when the container starts. Updating a ConfigMap does not change running Pod environment variables automatically.

Why use ConfigMaps instead of hardcoding config in container images?

A To make images larger

B To increase container startup time

C To separate config from code and update config without rebuilding images

D To avoid using environment variables

ConfigMaps separate configuration from container images, allowing config changes without rebuilding or redeploying images.

Explain how to use a ConfigMap to provide environment variables to a Kubernetes Pod.

Think about how environment variables are set inside containers.

Describe the benefits of using ConfigMaps for environment variables instead of hardcoding values in container images.

Consider how changing settings without changing the app helps.

Practice

1. What is the main purpose of using a ConfigMap in Kubernetes when setting environment variables for a pod?

easy

A. To separate configuration data from application code for easier updates

B. To store container images for pods

C. To manage network policies between pods

D. To define resource limits for containers

Solution

1. Step 1: Understand ConfigMap role

   ConfigMaps hold configuration data separately from app code, allowing updates without rebuilding images.

2. Step 2: Identify correct purpose

   Among options, only separating config data matches ConfigMap's main use for environment variables.

3. Final Answer:

   To separate configuration data from application code for easier updates -> Option A

4. Quick Check:

   ConfigMap purpose = separate config data [OK]

Hint: ConfigMaps separate config from code for flexible env vars [OK]

Common Mistakes:

• Confusing ConfigMaps with container images
• Thinking ConfigMaps manage network or resources
• Using ConfigMaps to store secrets (use Secrets instead)

2. Which of the following is the correct syntax to load all keys from a ConfigMap named app-config as environment variables in a pod spec?

easy

A. envFrom:
- configMapRef:
name: app-config

B. env:
- name: app-config
valueFrom:
configMapKeyRef:
name: app-config

C. configMap:
name: app-config

D. envFrom:
- secretRef:
name: app-config

Solution

1. Step 1: Identify correct envFrom usage

   To load all keys as env vars, use envFrom with configMapRef and the ConfigMap name.

2. Step 2: Check options for syntax correctness

   envFrom: - configMapRef: name: app-config correctly uses envFrom with configMapRef. Others misuse keys or use secretRef incorrectly.

3. Final Answer:

   envFrom: - configMapRef: name: app-config -> Option A

4. Quick Check:

   Use envFrom + configMapRef for all keys [OK]

Hint: Use envFrom with configMapRef to load all keys [OK]

Common Mistakes:

• Using env instead of envFrom for all keys
• Confusing configMapRef with secretRef
• Missing indentation or wrong key names

3. Given this pod spec snippet, what environment variables will be available inside the container?

envFrom:
  - configMapRef:
      name: my-config

And the ConfigMap my-config contains keys: API_URL=https://api.example.com and TIMEOUT=30.

medium

A. Only API_URL=https://api.example.com

B. API_URL=https://api.example.com and TIMEOUT=30

C. Only TIMEOUT=30

D. No environment variables will be set

Solution

1. Step 1: Understand envFrom with configMapRef

   Using envFrom with configMapRef loads all keys from the ConfigMap as environment variables.

2. Step 2: Check ConfigMap keys

   The ConfigMap has two keys: API_URL and TIMEOUT, so both become env vars.

3. Final Answer:

   API_URL=https://api.example.com and TIMEOUT=30 -> Option B

4. Quick Check:

   envFrom loads all keys as env vars [OK]

Hint: envFrom loads all ConfigMap keys as env vars [OK]

Common Mistakes:

• Assuming only one key loads at a time
• Confusing envFrom with env and missing keys
• Thinking ConfigMap keys are not environment variables

4. You applied this pod spec to use a ConfigMap as environment variables, but the container does not see the variables. What is wrong?

envFrom:
  - configMapRef:
      name: wrong-config-name

The ConfigMap you created is named app-config.

medium

A. The pod spec must use secretRef instead of configMapRef

B. envFrom cannot be used to load ConfigMaps

C. ConfigMaps cannot be used as environment variables

D. The ConfigMap name in the pod spec does not match the actual ConfigMap name

Solution

1. Step 1: Compare ConfigMap names

   The pod spec references wrong-config-name, but the actual ConfigMap is app-config.

2. Step 2: Understand impact of name mismatch

   If names don't match, Kubernetes cannot find the ConfigMap, so env vars won't be set.

3. Final Answer:

   The ConfigMap name in the pod spec does not match the actual ConfigMap name -> Option D

4. Quick Check:

   ConfigMap name must match exactly [OK]

Hint: Check ConfigMap name spelling matches pod spec [OK]

Common Mistakes:

• Using secretRef instead of configMapRef incorrectly
• Assuming envFrom can't load ConfigMaps
• Ignoring case sensitivity in names

5. You want to update environment variables in a running pod without rebuilding the container image. Which approach using ConfigMaps is correct?

hard

A. Use a Secret instead of ConfigMap for environment variables

B. Modify the container image to include new environment variables

C. Create or update a ConfigMap and reference it with envFrom in the pod spec, then restart the pod

D. Edit the pod spec to add environment variables directly and redeploy the image

Solution

1. Step 1: Understand ConfigMap update workflow

   ConfigMaps allow updating config data separately; updating the ConfigMap and restarting the pod applies new env vars without rebuilding images.

2. Step 2: Evaluate options for best practice

   Create or update a ConfigMap and reference it with envFrom in the pod spec, then restart the pod correctly uses ConfigMap with envFrom and pod restart. Others require image rebuild or confuse Secrets with ConfigMaps.

3. Final Answer:

   Create or update a ConfigMap and reference it with envFrom in the pod spec, then restart the pod -> Option C

4. Quick Check:

   Update ConfigMap + restart pod for new env vars [OK]

Hint: Update ConfigMap and restart pod, no image rebuild needed [OK]

Common Mistakes:

• Rebuilding container image unnecessarily
• Confusing Secrets with ConfigMaps for non-sensitive data
• Editing pod spec without restarting pod