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

Recall & Review

beginner

What is a Kubernetes Secret?

A Kubernetes Secret is a way to store and manage sensitive information, like passwords or tokens, separately from application code.

beginner

How do you use a Secret as an environment variable in a Pod?

You define an environment variable in the Pod spec that references the Secret's key using env: with valueFrom.secretKeyRef.

intermediate

Example YAML snippet to set environment variable from Secret key 'password' named 'mysecret'.

env:
  - name: DB_PASSWORD
    valueFrom:
      secretKeyRef:
        name: mysecret
        key: password

beginner

Why should you use Secrets instead of plain environment variables for sensitive data?

Secrets keep sensitive data separate from code and can be encrypted, reducing risk of accidental exposure and improving security.

beginner

What command creates a Secret from literal values?

Use kubectl create secret generic mysecret --from-literal=password=mypassword to create a Secret named 'mysecret' with a password.

How do you reference a Secret key as an environment variable in a Pod spec?

A Using <code>valueFrom.secretKeyRef</code>

B Using <code>configMapKeyRef</code>

C Using <code>envFrom.secretRef</code>

D Using <code>volumeMounts</code>

The correct way is to use valueFrom.secretKeyRef to map a Secret key to an environment variable.

Which command creates a Secret from a literal value?

A kubectl create secret generic mysecret --from-literal=password=mypassword

B kubectl create configmap mysecret --from-literal=password=mypassword

C kubectl apply -f secret.yaml

D kubectl get secret mysecret

The kubectl create secret generic command with --from-literal creates a Secret from literal values.

Why use Secrets instead of plain environment variables for sensitive data?

A Secrets use less memory

B Secrets are faster to load

C Secrets are encrypted and safer

D Secrets are easier to debug

Secrets provide encryption and better security for sensitive data compared to plain environment variables.

What is the default encoding for data stored in Kubernetes Secrets?

A UTF-8

B Base64

C Hexadecimal

D Plain text

Kubernetes stores Secret data encoded in Base64 format.

Which Kubernetes object is best for storing sensitive environment variables?

A Pod

B ConfigMap

C Service

D Secret

Secrets are designed specifically to store sensitive data like passwords or tokens.

Explain how to use a Kubernetes Secret as an environment variable in a Pod.

Think about how environment variables are set in the Pod YAML.

Describe why using Secrets is important for managing sensitive data in Kubernetes.

Consider the risks of putting passwords directly in code or config.

Practice

1. What is the main purpose of using Kubernetes Secrets as environment variables in a Pod?

easy

A. To keep sensitive data like passwords out of the container image and code

B. To speed up container startup time

C. To increase the size of the container image

D. To make the container logs more detailed

Solution

1. Step 1: Understand what Secrets store

   Kubernetes Secrets store sensitive data such as passwords or tokens securely.

2. Step 2: Understand environment variables usage

   Using Secrets as environment variables keeps sensitive data out of code and container images, improving security.

3. Final Answer:

   To keep sensitive data like passwords out of the container image and code -> Option A

4. Quick Check:

   Secrets protect sensitive data = A [OK]

Hint: Secrets keep sensitive data safe outside code [OK]

Common Mistakes:

• Thinking Secrets speed up container startup
• Believing Secrets increase container size
• Assuming Secrets add logging details

2. Which of the following is the correct syntax to use a Kubernetes Secret named mysecret as an environment variable API_KEY in a Pod spec?

easy

A. "env": [{"secretKeyRef": {"name": "mysecret", "key": "api_key"}}]

B. "env": [{"name": "API_KEY", "value": "mysecret"}]

C. "env": [{"name": "API_KEY", "valueFrom": {"secretKeyRef": {"name": "mysecret", "key": "api_key"}}}]

D. "env": [{"name": "API_KEY", "secretRef": {"name": "mysecret"}}]

Solution

1. Step 1: Identify correct env var syntax for Secrets

   The correct syntax uses valueFrom.secretKeyRef with name and key fields.

2. Step 2: Match syntax to options

   "env": [{"name": "API_KEY", "valueFrom": {"secretKeyRef": {"name": "mysecret", "key": "api_key"}}}] matches the correct structure exactly, specifying the secret name and key.

3. Final Answer:

   "env": [{"name": "API_KEY", "valueFrom": {"secretKeyRef": {"name": "mysecret", "key": "api_key"}}}] -> Option C

4. Quick Check:

   Use valueFrom.secretKeyRef with name and key = D [OK]

Hint: Use valueFrom.secretKeyRef with secret name and key [OK]

Common Mistakes:

• Using value instead of valueFrom
• Missing the key field inside secretKeyRef
• Using secretRef instead of secretKeyRef

3. Given this Pod spec snippet, what will be the value of environment variable DB_PASSWORD inside the container?

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

Assuming the Secret db-secret has the key password with value supersecret123.

medium

A. db-secret

B. DB_PASSWORD

C. password

D. supersecret123

Solution

1. Step 1: Understand valueFrom.secretKeyRef usage

   The environment variable gets its value from the Secret named db-secret and key password.

2. Step 2: Check Secret key value

   The Secret key password holds the value supersecret123, so that is assigned to DB_PASSWORD.

3. Final Answer:

   supersecret123 -> Option D

4. Quick Check:

   Env var gets Secret key's value = B [OK]

Hint: Env var equals Secret's key value, not name or key name [OK]

Common Mistakes:

• Using Secret name as value
• Using key name as value
• Confusing env var name with Secret key

4. You created a Secret named app-secret with key token. You try to use it in a Pod environment variable but get an error: secret "app-secret" not found. What is the most likely cause?

medium

A. The Secret was created in a different namespace than the Pod

B. The Secret key name is misspelled in the Pod spec

C. The Pod spec uses value instead of valueFrom

D. The container image does not support environment variables

Solution

1. Step 1: Understand Secret scope in Kubernetes

   Secrets are namespace-scoped. If the Pod is in a different namespace, it cannot access the Secret.

2. Step 2: Analyze error message

   The error secret "app-secret" not found usually means the Secret does not exist in the Pod's namespace.

3. Final Answer:

   The Secret was created in a different namespace than the Pod -> Option A

4. Quick Check:

   Secret must be in same namespace as Pod = C [OK]

Hint: Check Secret and Pod namespaces match [OK]

Common Mistakes:

• Ignoring namespace differences
• Assuming key name typo causes 'not found' error
• Blaming container image for env var errors

5. You want to mount multiple keys from a Secret named config-secret as environment variables in a Pod. Which is the best way to do this efficiently?

hard

A. Mount the Secret as a volume and read files inside the container

B. List each key separately under env with individual valueFrom.secretKeyRef entries

C. Create multiple Secrets, one per key, and reference each in env

D. Encode all keys into one string and store as a single Secret key

Solution

1. Step 1: Understand environment variable mapping from Secrets

   You can map each Secret key to an environment variable by listing them separately under env with valueFrom.secretKeyRef.

2. Step 2: Compare alternatives

   Mounting as volume is valid but not environment variables. Multiple Secrets or encoding keys complicate management.

3. Final Answer:

   List each key separately under env with individual valueFrom.secretKeyRef entries -> Option B

4. Quick Check:

   Map each key to env var individually = A [OK]

Hint: Map each Secret key individually in env list [OK]

Common Mistakes:

• Mounting Secret as volume when env vars needed
• Creating many Secrets instead of one
• Combining keys into one encoded string