liveBook · Manning

Configmap volume

As explained in Kubernetes for Developers

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

A ConfigMap volume exposes ConfigMap data to a container as read-only files. Store key-value settings or complete configuration files in one place, then mount them where an application expects them. section 9.1.1

Use a ConfigMap volume when you need to:

  • Provide files such as my.cnf, httpd.conf, or redis.conf without rebuilding the container image. section 9.1.1
  • Define configuration once and reference it from multiple Kubernetes objects. section 9.1.1
  • Mount configuration for an existing public image at the path where its application expects the file. section 9.1.1

How Kubernetes for Developers covers it

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.
How it connects
Connects ConfigMaps with Kubernetes volumes, containers, public container images, and application configuration files.

Also explained in

Compare how 2 books explain configmap volume →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kubernetes for Developers. The section links point to the parts of the book it draws on.