Kubernetes ConfigMap Generator - Create K8s Config YAML

Generate Kubernetes ConfigMaps from key-value pairs or files. Create configuration for apps without rebuilding images. Browser-based tool.

ConfigMap Name

Namespace

Key-Value Pairs

Labels (optional)

Generated YAML

Usage Examples

# As environment variables
envFrom:
  - configMapRef:
      name: app-config

# As volume mount
volumes:
  - name: config
    configMap:
      name: app-config
volumeMounts:
  - name: config
    mountPath: /etc/config

# Single key as env var
env:
  - name: APP_ENV
    valueFrom:
      configMapKeyRef:
        name: app-config
        key: APP_ENV

Kubernetes CronJob Generator - Scheduled…

Kubernetes HPA Generator - Horizontal Po…

Kubernetes Secret Generator - Create K8s…

Kubernetes Service Generator - Create Se…

View all Kubernetes configurators →

Frequently Asked Questions

A ConfigMap stores non-sensitive configuration data as key-value pairs. Pods can consume ConfigMaps as environment variables, command-line arguments, or configuration files in a volume.

Use ConfigMap for non-sensitive data like config files, feature flags, and URLs. Use Secrets for sensitive data like passwords, API keys, and certificates.

Use volumes: volumes: [{name: config, configMap: {name: my-config}}] and volumeMounts: [{name: config, mountPath: /etc/config}]. Each key becomes a file.

Volume-mounted ConfigMaps update automatically (kubelet sync period, ~1 min). Environment variables require pod restart. Use subPath mounts for atomic updates.

ConfigMaps are limited to 1MB total size. For larger configs, consider mounting files from PersistentVolumes or using init containers.

Use envFrom: [{configMapRef: {name: my-config}}] to load all keys, or env with configMapKeyRef to select specific keys.

Yes, use binaryData field for binary content. Data is base64-encoded. Regular data field is for UTF-8 text.

kubectl create configmap my-config --from-file=config.yaml. This tool generates equivalent YAML. The filename becomes the key, file content the value.

Pod fails to start with error. Use optional: true in configMapRef to make it optional, or ensure ConfigMap is created before pods.

No, ConfigMaps are namespace-scoped. Create the ConfigMap in the same namespace as the pods that use it, or use tools to sync across namespaces.

Related Tools