liveBook · Manning

Configmap volume

A ConfigMap volume is a read-only Kubernetes volume that exposes ConfigMap data to containers as mounted files.

How 2 Manning books explain it

Kubernetes in Action, Second Edition

A ConfigMap volume is a Kubernetes volume that exposes data from a ConfigMap as files mounted in a container.

How it is used
Exposes large or multiline application configuration as container files instead of environment variables.
How deep it goes
Explains manifests, selected entries, hidden directory contents, subPath, missing references, and atomic symbolic-link updates.
Examples
Uses an Envoy configuration pod, mounted envoy.yaml and status-message files, selected items, and kubectl inspection commands.
What you can do after
Operate/configure pods with mounted ConfigMap files and diagnose startup, masking, selection, and update behavior.

Read how Kubernetes in Action, Second Edition explains configmap volume →

Kubernetes for Developers

A ConfigMap volume is a read-only Kubernetes volume that exposes ConfigMap data to containers as files.

How it is used
Provides application configuration files without extending the container image.
How deep it goes
Defines the volume’s purpose, contents, and read-only behavior, but defers manifest syntax and mounting steps.
Examples
Uses MariaDB, Apache, and Redis configuration files as examples of data mounted through ConfigMap volumes.
What you can do after
Apply it to supply configuration to an existing public container image without building a custom image.

Read how Kubernetes for Developers explains configmap volume →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.