ConfigMaps and Secrets
ConfigMaps
Store non-confidential configuration data in key-value pairs.
Creating ConfigMaps
apiVersion: v1
kind: ConfigMap
metadata:
name: app-config
data:
database_url: "mongodb://localhost:27017"
debug_mode: "true"
max_connections: "100"
Using ConfigMaps in Pods
apiVersion: v1
kind: Pod
metadata:
name: configmap-pod
spec:
containers:
- name: app
image: nginx
env:
- name: DATABASE_URL
valueFrom:
configMapKeyRef:
name: app-config
key: database_url
volumeMounts:
- name: config-volume
mountPath: /etc/config
volumes:
- name: config-volume
configMap:
name: app-config
Secrets
Store sensitive data like passwords, tokens, and keys.
Creating Secrets
apiVersion: v1
kind: Secret
metadata:
name: app-secret
type: Opaque
data:
username: YWRtaW4= # base64 encoded 'admin'
password: MWYyZDFlMmU2N2Rm # base64 encoded password
Using Secrets in Pods
apiVersion: v1
kind: Pod
metadata:
name: secret-pod
spec:
containers:
- name: app
image: nginx
env:
- name: DB_USERNAME
valueFrom:
secretKeyRef:
name: app-secret
key: username
- name: DB_PASSWORD
valueFrom:
secretKeyRef:
name: app-secret
key: password
Commands for ConfigMaps and Secrets
# Create ConfigMap from literal
kubectl create configmap app-config --from-literal=key1=value1
# Create ConfigMap from file
kubectl create configmap app-config --from-file=config.properties
# Create Secret from literal
kubectl create secret generic app-secret --from-literal=username=admin
# Create Secret from file
kubectl create secret generic app-secret --from-file=credentials.txt
# View ConfigMap/Secret
kubectl get configmap app-config -o yaml
kubectl get secret app-secret -o yaml
Next Steps
Learn about Volumes and Storage to persist data in your applications.