How Do You Mount ConfigMaps as Volumes?

Detailed Answer

Mounting ConfigMaps as volumes is the preferred way to inject configuration files into containers. Each key in the ConfigMap becomes a file, and each value becomes the file content.

Basic Volume Mount

apiVersion: v1
kind: ConfigMap
metadata:
  name: nginx-config
data:
  nginx.conf: |
    server {
        listen 80;
        server_name localhost;
        location / {
            root /usr/share/nginx/html;
            index index.html;
        }
        location /api {
            proxy_pass http://api-service:8080;
        }
    }
  mime.types: |
    text/html html;
    text/css css;
    application/json json;
---
apiVersion: v1
kind: Pod
metadata:
  name: nginx
spec:
  containers:
    - name: nginx
      image: nginx:1.27
      volumeMounts:
        - name: config
          mountPath: /etc/nginx/conf.d
          readOnly: true
      resources:
        requests:
          cpu: "100m"
          memory: "128Mi"
  volumes:
    - name: config
      configMap:
        name: nginx-config

This creates two files in the container:

• /etc/nginx/conf.d/nginx.conf
• /etc/nginx/conf.d/mime.types

Selecting Specific Keys

Mount only specific keys from the ConfigMap:

volumes:
  - name: config
    configMap:
      name: nginx-config
      items:
        - key: nginx.conf
          path: default.conf    # Rename the file

This creates only /etc/nginx/conf.d/default.conf from the nginx.conf key.

SubPath: Mounting a Single File

Without subPath, mounting a ConfigMap to a directory replaces all existing files. To add a single file without overwriting:

apiVersion: v1
kind: Pod
metadata:
  name: app
spec:
  containers:
    - name: app
      image: myapp:v2
      volumeMounts:
        - name: config
          mountPath: /app/config/settings.yaml
          subPath: settings.yaml
      resources:
        requests:
          cpu: "250m"
          memory: "256Mi"
  volumes:
    - name: config
      configMap:
        name: app-config

Important caveat: SubPath mounts do not receive automatic updates when the ConfigMap changes. If you need auto-updates, use a directory mount instead.

File Permissions

Set file permissions with defaultMode:

volumes:
  - name: config
    configMap:
      name: app-config
      defaultMode: 0644    # rw-r--r--

Per-file permissions:

volumes:
  - name: config
    configMap:
      name: app-config
      items:
        - key: script.sh
          path: script.sh
          mode: 0755    # rwxr-xr-x (executable)
        - key: config.yaml
          path: config.yaml
          mode: 0644

Automatic Update Mechanism

When a ConfigMap is updated, mounted volumes are updated via a symlink-based mechanism:

/etc/app/config/                    # Mount point
  ├── ..data -> ..2026_03_19_...    # Symlink to latest version
  ├── ..2026_03_19_...              # Timestamped directory
  │   ├── nginx.conf
  │   └── mime.types
  ├── nginx.conf -> ..data/nginx.conf
  └── mime.types -> ..data/mime.types

When the ConfigMap changes:

1. A new timestamped directory is created with the updated files
2. The ..data symlink is atomically swapped to point to the new directory
3. The old directory is removed

This ensures the update is atomic — your application never sees a partially updated state.

Triggering Application Reload

Most applications do not watch for file changes automatically. Common patterns for reloading:

# Nginx can reload via signal
lifecycle:
  postStart:
    exec:
      command: ["/bin/sh", "-c", "nginx -s reload"]

# Or use a sidecar that watches for changes
containers:
  - name: config-reloader
    image: jimmidyson/configmap-reload:v0.9.0
    args:
      - --volume-dir=/etc/config
      - --webhook-url=http://localhost:8080/-/reload
    volumeMounts:
      - name: config
        mountPath: /etc/config

Volume Mount vs Environment Variable

| Aspect | Volume Mount | Environment Variable | |---|---|---| | Auto-updates | Yes (except subPath) | No | | Supports multiline | Yes (files) | Awkward | | Memory usage | Disk-backed | In process memory | | Application access | Read file from disk | Read env var | | Best for | Config files (YAML, TOML, properties) | Simple key-value settings |