Hands-On Microservices with Kubernetes

Creating and managing ConfigMaps

Kubernetes gives you multiple ways to create ConfigMaps:

• From command-line values
• From one or more files
• From a whole directory
• By directly creating a ConfigMap YAML manifest

In the end, all ConfigMaps are a set of key–value pairs. What the keys and values are depends on the method of creating the ConfigMap. When playing with ConfigMaps, I find it useful to use the --dry-run flag so that I can see what ConfigMap will be created before committing to actually creating it. Let's look at some examples. Here is how to create a ConfigMap from command-line arguments:

$ kubectl create configmap test --dry-run --from-literal=a=1 --from-literal=b=2 -o yamlapiVersion: v1data:  a: "1"  b: "2"kind: ConfigMapmetadata: