ConfigMap & Secret

Code

# configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: api-config
data:
  LOG_LEVEL: "info"
  config.yaml: |
    server:
      port: 8080
      timeout: 30s

---
# secret.yaml (values must be base64-encoded)
apiVersion: v1
kind: Secret
metadata:
  name: api-secret
type: Opaque
data:
  DB_PASSWORD: c2VjcmV0   # echo -n secret | base64

---
# Pod consuming them
spec:
  containers:
    - name: api
      envFrom:
        - configMapRef: { name: api-config }
        - secretRef:    { name: api-secret }
      volumeMounts:
        - name: cfg
          mountPath: /etc/app

Explanation

ConfigMaps store non-sensitive configuration as key-value pairs or files, while Secrets hold base64-encoded sensitive data. envFrom injects all keys as environment variables, and volumes can mount ConfigMap entries as files. Secrets are not encrypted by default; enable encryption at rest in etcd for production.

More Kubernetes Snippets