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

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Pod Environment Variable from Secret

Given the following Kubernetes Pod YAML snippet, what will be the output of the command echo $API_KEY inside the container?

Pod YAML snippet:

apiVersion: v1
kind: Pod
metadata:
  name: secret-env-pod
spec:
  containers:
  - name: test-container
    image: busybox
    command: ["sh", "-c", "echo $API_KEY && sleep 3600"]
    env:
    - name: API_KEY
      valueFrom:
        secretKeyRef:
          name: mysecret
          key: api_key

A The value of 'api_key' stored in the 'mysecret' Secret

B An empty string because environment variables cannot come from Secrets

C The literal string '$API_KEY'

D A runtime error because the Secret is not mounted as a volume

💡 Hint

Secrets can be referenced as environment variables using valueFrom.secretKeyRef.

Kubernetes allows you to inject Secret values as environment variables using valueFrom.secretKeyRef. The container will have the environment variable API_KEY set to the Secret's 'api_key' value.

❓ Configuration

intermediate

Correct Secret Reference in Pod Spec

Which of the following environment variable configurations correctly injects the Secret key password from Secret db-secret into the container environment variable DB_PASS?

A

env:
- name: DB_PASS
  secretKeyRef:
    name: db-secret
    key: password

B

env:
- name: DB_PASS
  valueFrom:
    configMapKeyRef:
      name: db-secret
      key: password

C

env:
- name: DB_PASS
  value: db-secret:password

D

env:
- name: DB_PASS
  valueFrom:
    secretKeyRef:
      name: db-secret
      key: password

💡 Hint

Use valueFrom.secretKeyRef to reference Secrets in environment variables.

Option D correctly uses valueFrom.secretKeyRef with the Secret name and key. Option D is invalid syntax. Option D treats the Secret as a string literal. Option D incorrectly uses configMapKeyRef instead of secretKeyRef.

❓ Troubleshoot

advanced

Why is the Secret environment variable empty?

A developer created a Secret named app-secret with key token. The Pod YAML references it as an environment variable APP_TOKEN using valueFrom.secretKeyRef. However, inside the container, echo $APP_TOKEN prints an empty line. What is the most likely cause?

A The Secret <code>app-secret</code> does not exist in the same namespace as the Pod

B The container image does not support environment variables

C The Pod spec must mount the Secret as a volume to use it as an environment variable

D The key <code>token</code> is misspelled in the Secret data

💡 Hint

Secrets are namespace-scoped and must be in the same namespace as the Pod.

If the Secret is missing or in a different namespace, Kubernetes cannot inject its value, resulting in an empty environment variable. The container image supports env vars by default. Mounting as a volume is not required for env vars. Misspelling the key would cause a different error or empty value but the most common cause is namespace mismatch.

🔀 Workflow

advanced

Steps to Update a Secret Used as Environment Variable

You updated the value of a Kubernetes Secret api-keys used as an environment variable in a running Pod. What is the correct workflow to apply the new Secret value so the Pod sees the updated environment variable?

A Update the Secret, then patch the Pod to reload environment variables automatically

B Update the Secret, then delete the Pod to let the controller recreate it with the new Secret value

C Update the Secret, then exec into the Pod and export the new environment variable manually

D Update the Secret, then restart the container inside the Pod without deleting the Pod

💡 Hint

Pods do not automatically reload environment variables from updated Secrets.

Kubernetes does not update environment variables in running containers when Secrets change. The common practice is to update the Secret and then delete the Pod so the controller recreates it with the new Secret values. Manually exporting env vars or patching the Pod does not work. Restarting containers inside a Pod is not supported.

✅ Best Practice

expert

Secure Handling of Secrets as Environment Variables

Which practice is the most secure when using Kubernetes Secrets as environment variables in Pods?

A Embed Secrets directly in Pod YAML files to avoid external dependencies

B Store Secrets in plain text ConfigMaps and reference them as environment variables

C Use Secrets for sensitive data and restrict RBAC permissions to limit Secret access

D Use environment variables for Secrets only in development, and hardcode them in production containers

💡 Hint

Kubernetes Secrets are designed for sensitive data and access control is important.

Option C follows best security practices by using Secrets and controlling access via RBAC. Option C is insecure because ConfigMaps are not encrypted. Option C exposes Secrets in YAML files which can be checked into source control. Option C is insecure and not recommended.