Using ConfigMaps as mounted volumes 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 helps separate configuration from container images, making apps easier to manage and update.

beginner

How do you use a ConfigMap as a mounted volume in a Pod?

You create a volume in the Pod spec that references the ConfigMap, then mount that volume into a container's file system at a specific path.

intermediate

What happens to the files inside a ConfigMap volume when the ConfigMap is updated?

The files inside the mounted ConfigMap volume are updated automatically within a few seconds, so the container sees the latest config without restarting.

intermediate

Can you mount only specific keys from a ConfigMap as files in a volume?

Yes, you can specify which keys to include or rename them as files using the 'items' field in the volume definition.

beginner

Show a simple YAML snippet to mount a ConfigMap named 'app-config' as a volume at '/etc/config'.

volumes: - name: config-volume configMap: name: app-config containers: - name: app volumeMounts: - name: config-volume mountPath: /etc/config

What is the main purpose of using ConfigMaps as mounted volumes in Kubernetes?

A To schedule Pods on nodes

B To store container images

C To manage network policies

D To provide configuration files inside containers

ConfigMaps provide configuration data as files or environment variables inside containers.

Which Kubernetes object do you reference to mount a ConfigMap as a volume?

A secret volume

B persistentVolumeClaim

C volume with configMap field

D serviceAccount

You define a volume with the configMap field pointing to the ConfigMap name.

If you update a ConfigMap, what happens to the mounted files in running Pods?

A They update automatically after a short delay

B They never update until Pod restart

C They update only after deleting the Pod

D They update only after deleting the ConfigMap

Mounted ConfigMap files refresh automatically within seconds without restarting the Pod.

How can you mount only specific keys from a ConfigMap as files?

A Create a new ConfigMap with only those keys

B Use the 'items' field in the volume config

C Use environment variables only

D Mount the entire ConfigMap always

The 'items' field lets you select and rename keys to mount as files.

Where do you specify the mount path for a ConfigMap volume inside a container?

A volumeMounts.mountPath

B volumes.path

C containers.image

D metadata.name

The mountPath is set under volumeMounts in the container spec.

Explain how to mount a ConfigMap as a volume in a Kubernetes Pod and why this is useful.

Think about separating config from code and how files appear inside containers.

Describe what happens when you update a ConfigMap that is mounted as a volume in a running Pod.

Consider how Kubernetes syncs ConfigMap data to the volume.

Practice

1. What is the main purpose of using a ConfigMap as a mounted volume in Kubernetes?

easy

A. To provide configuration data as files inside a container without rebuilding the image

B. To store container logs persistently

C. To increase container CPU limits dynamically

D. To manage container networking settings

Solution

1. Step 1: Understand ConfigMap role

   ConfigMaps hold configuration data separately from container images.

2. Step 2: Understand mounting as volume

   Mounting a ConfigMap as a volume makes its data available as files inside the container.

3. Final Answer:

   To provide configuration data as files inside a container without rebuilding the image -> Option A

4. Quick Check:

   ConfigMap volume = config files inside container [OK]

Hint: ConfigMaps as volumes = config files inside container [OK]

Common Mistakes:

• Confusing ConfigMaps with persistent storage for logs
• Thinking ConfigMaps control CPU or networking
• Assuming ConfigMaps require container rebuild

2. Which of the following is the correct YAML snippet to mount a ConfigMap named app-config as a volume in a pod?

easy

A. volumes:\n - name: config-volume\n emptyDir: {}

B. volumes:\n - name: config-volume\n secret:\n name: app-config

C. volumes:\n - name: config-volume\n persistentVolumeClaim:\n claimName: app-config

D. volumes:\n - name: config-volume\n configMap:\n name: app-config

Solution

1. Step 1: Identify volume type for ConfigMap

   ConfigMaps are mounted using the configMap field inside volumes.

2. Step 2: Match correct YAML structure

   volumes:\n - name: config-volume\n configMap:\n name: app-config correctly uses configMap: with the ConfigMap name.

3. Final Answer:

   volumes:\n - name: config-volume\n configMap:\n name: app-config -> Option D

4. Quick Check:

   ConfigMap volume uses configMap: name [OK]

Hint: ConfigMap volume uses 'configMap:' with name [OK]

Common Mistakes:

• Using secret instead of configMap for ConfigMap volumes
• Confusing persistentVolumeClaim with ConfigMap
• Using emptyDir which is an empty temp volume

3. Given this pod volume mount snippet, what file content will appear inside the container at /etc/config/app.properties if the ConfigMap app-config has a key app.properties with value mode=production?

volumes:
  - name: config-volume
    configMap:
      name: app-config
containers:
  - name: app
    image: myapp
    volumeMounts:
      - name: config-volume
        mountPath: /etc/config
        readOnly: true

medium

A. A directory named app.properties with no content

B. No file created because mountPath is a directory

C. A file named app.properties with content 'mode=production'

D. A file named app.properties with content 'mode=development'

Solution

1. Step 1: Understand ConfigMap key to file mapping

   Each key in ConfigMap becomes a file with that name and its value as content.

2. Step 2: Check mountPath and file presence

   Mounting at /etc/config creates files inside that directory, including app.properties with content mode=production.

3. Final Answer:

   A file named app.properties with content 'mode=production' -> Option C

4. Quick Check:

   ConfigMap key = filename, value = file content [OK]

Hint: ConfigMap keys become files with their values inside mountPath [OK]

Common Mistakes:

• Thinking mountPath must be a file, not directory
• Assuming file content changes without ConfigMap update
• Confusing file name with directory

4. You mounted a ConfigMap as a volume, but inside the container the files are missing. Which is the most likely cause?

medium

A. The ConfigMap name in the volume spec does not match any existing ConfigMap

B. The container image does not support volumes

C. The pod has no CPU resources assigned

D. The ConfigMap keys are empty strings

Solution

1. Step 1: Check ConfigMap reference correctness

   If the ConfigMap name in the volume spec is wrong, Kubernetes cannot mount it, so files won't appear.

2. Step 2: Eliminate unrelated causes

   Container images support volumes by default; CPU resources don't affect file mounting; keys cannot be empty strings in ConfigMaps.

3. Final Answer:

   The ConfigMap name in the volume spec does not match any existing ConfigMap -> Option A

4. Quick Check:

   Wrong ConfigMap name = no files mounted [OK]

Hint: Check ConfigMap name spelling in volume spec [OK]

Common Mistakes:

• Blaming container image for missing files
• Ignoring ConfigMap existence or name mismatch
• Assuming resource limits affect volume mounts

5. You want to mount only specific keys from a ConfigMap named app-config as files inside a container at /etc/config. Which volume configuration snippet achieves this?

hard

A. volumes:
- name: config-volume
configMap:
name: app-config
exclude:
- unused_key

B. volumes:
- name: config-volume
configMap:
name: app-config
items:
- key: database_url
path: db_url
- key: log_level
path: log_level

C. volumes:
- name: config-volume
secret:
name: app-config
items:
- key: database_url
path: db_url

D. volumes:
- name: config-volume
configMap:
name: app-config
keys:
- database_url
- log_level

Solution

1. Step 1: Understand selective key mounting

   Kubernetes allows selecting specific keys from a ConfigMap using the items field with key and path.

2. Step 2: Identify correct syntax

   volumes: - name: config-volume configMap: name: app-config items: - key: database_url path: db_url - key: log_level path: log_level correctly uses items with key-path pairs to mount only chosen keys as files.

3. Final Answer:

   volumes: - name: config-volume configMap: name: app-config items: - key: database_url path: db_url - key: log_level path: log_level -> Option B

4. Quick Check:

   Use items with key and path to select keys [OK]

Hint: Use 'items' with key and path to mount specific keys [OK]

Common Mistakes:

• Using 'keys' instead of 'items' for selection
• Confusing ConfigMap with Secret for this purpose
• Trying to exclude keys instead of selecting them