Using ConfigMaps as environment variables in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Pod Environment Variables from ConfigMap

Given a ConfigMap named app-config with key-value pairs, and a Pod manifest that uses this ConfigMap as environment variables, what will be the output of printenv inside the Pod?

Kubernetes

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
data:
  LOG_LEVEL: DEBUG
  MAX_RETRIES: "5"
---
apiVersion: v1
kind: Pod
metadata:
  name: test-pod
spec:
  containers:
  - name: test-container
    image: busybox
    command: ["sh", "-c", "printenv"]
    envFrom:
    - configMapRef:
        name: app-config

A LOG_LEVEL=DEBUG\nMAX_RETRIES=5 (without quotes)\n... (other default env vars)

B LOG_LEVEL=DEBUG\nMAX_RETRIES=5\n... (other default env vars)

C No environment variables from ConfigMap are set

D LOG_LEVEL=DEBUG\nMAX_RETRIES="5"\n... (other default env vars)

💡 Hint

Remember that ConfigMap values are strings and environment variables are strings without quotes.

ConfigMap values are injected as strings without quotes in environment variables. The value "5" is interpreted as the string 5 without quotes in the environment.

❓ Configuration

intermediate

Correct ConfigMap Reference in Pod Spec

Which of the following Pod specs correctly injects environment variables from a ConfigMap named my-config?

A

envFrom:
- configMapRef:
    name: my-config

B

env:
- name: my-config
  valueFrom:
    configMapKeyRef:
      name: my-config
      key: my-config

C

envFrom:
- secretRef:
    name: my-config

D

env:
- name: my-config
  value: my-config

💡 Hint

Check the correct field name for referencing ConfigMaps in envFrom.

The correct way to inject all keys from a ConfigMap as environment variables is using envFrom with configMapRef and the ConfigMap name.

❓ Troubleshoot

advanced

Why Are ConfigMap Environment Variables Missing in Pod?

A Pod references a ConfigMap named settings using envFrom, but the environment variables are not available inside the container. What is the most likely cause?

A The container image does not support environment variables

B The Pod spec uses <code>envFrom: secretRef</code> instead of <code>configMapRef</code>

C The ConfigMap <code>settings</code> does not exist in the same namespace as the Pod

D The ConfigMap keys are empty strings

💡 Hint

ConfigMaps are namespace-scoped resources.

ConfigMaps must exist in the same namespace as the Pod to be referenced. If missing, environment variables won't be injected.

🔀 Workflow

advanced

Order of Steps to Update ConfigMap Environment Variables in Running Pod

What is the correct order of steps to update environment variables from a ConfigMap in a running Pod?

A 4,2,1,3

B 4,1,2,3

C 1,2,4,3

D 1,4,2,3

💡 Hint

Remember to apply changes before deleting the Pod to pick up new config.

First update the ConfigMap locally, then apply it to the cluster, delete the Pod to recreate it with new env vars, then verify.

✅ Best Practice

expert

Best Practice for Managing Sensitive Data with ConfigMaps as Environment Variables

Which approach is best practice when using ConfigMaps for environment variables that include sensitive data like passwords?

A Store sensitive data in Secrets and reference them separately from ConfigMaps

B Store sensitive data in ConfigMaps and use RBAC to restrict access

C Encode sensitive data in base64 and store in ConfigMaps

D Store sensitive data directly in Pod specs as environment variables

💡 Hint

Consider Kubernetes resource types designed for sensitive data.

Kubernetes Secrets are designed for sensitive data and provide better security than ConfigMaps.