What is a Kubernetes ConfigMap?

A ConfigMap is an API object that stores non-confidential configuration as key-value pairs. Pods consume it as environment variables, command-line arguments, or files mounted from a volume, keeping configuration separate from container images.

When should I use a ConfigMap instead of a Secret?

Use a ConfigMap for non-sensitive data like log levels, feature flags, hostnames, and config files. Use a Secret for passwords, tokens, and keys. ConfigMap data is stored in plaintext in etcd and is not meant to hold credentials.

How do file entries differ from key-value pairs?

Key-value pairs are single-line scalars, ideal for env vars. File entries are emitted as YAML block scalars so the full multi-line content is preserved. When mounted as a volume, each file entry becomes a file named after its key.

What does the immutable flag do?

Setting immutable: true prevents the ConfigMap from being changed after creation. This protects against accidental updates and lets the kubelet skip watching it, reducing API server load. To change it you must delete and recreate it.

How do I mount this ConfigMap into a pod?

Reference it in a Deployment under volumes as a configMap source, then mount that volume into the container, or use envFrom with configMapRef to load all keys as environment variables.

Kubernetes ConfigMap Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Build Kubernetes ConfigMaps without YAML mistakes

A ConfigMap decouples configuration from your container image so the same image can run in dev, staging, and production with different settings. This builder lets you assemble both simple environment-style key-value pairs and full multi-line config files, then emits a valid v1 ConfigMap manifest you can apply directly with kubectl.

How it works

ConfigMaps store all data under a data: map. Simple values become single-line YAML scalars, while a multi-line file (such as an nginx.conf or application.properties) must be written as a YAML block scalar so newlines are preserved. The builder uses the | block scalar indicator and indents every line, which is exactly how kubectl create configmap --from-file renders it.

Keys and values are quoted automatically when they could be misread by a YAML parser — for example a value of true, a number like 8080, or a string starting with a special character. This avoids the classic bug where enabled: true is parsed as a boolean instead of the string Kubernetes expects.

Tips and notes

Keys consumed as environment variables must be valid env-var names (letters, digits, underscores). File-style keys may contain dots, like app.properties.
To load every key as an env var, use envFrom with a configMapRef instead of listing each valueFrom individually.
Set immutable: true for config that never changes after deployment — it improves cluster performance and prevents accidental edits.
ConfigMaps are namespaced, so the name only needs to be unique within its namespace.