Creating ConfigMaps from files in Kubernetes - Visual Walkthrough

Process Flow - Creating ConfigMaps from files

Prepare file(s) with config data

↓

Run kubectl create configmap with --from-file

↓

Kubernetes reads file content

↓

ConfigMap object created with file data as key-value

↓

ConfigMap stored in cluster

↓

Use ConfigMap in pods or deployments

This flow shows how Kubernetes reads files to create a ConfigMap, storing the file content as key-value pairs for use in pods.

Execution Sample

Kubernetes

kubectl create configmap my-config --from-file=app.properties
kubectl get configmap my-config -o yaml

Creates a ConfigMap named 'my-config' from the file 'app.properties' and then displays its content.

Process Table

Step	Command/Action	Evaluation	Result
1	Prepare file 'app.properties' with content	File exists with key=value pairs	File ready for ConfigMap creation
2	kubectl create configmap my-config --from-file=app.properties	Reads file content	ConfigMap 'my-config' created with key 'app.properties' and file content as value
3	kubectl get configmap my-config -o yaml	Fetch ConfigMap data	Displays ConfigMap YAML with data from 'app.properties' file
4	Use ConfigMap in pod spec	Pod references ConfigMap keys	Pod can access config data as environment variables or files
5	Exit	No more commands	Process complete

💡 ConfigMap created and verified; ready for use in pods

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
app.properties content	key=value	Stored in ConfigMap under key 'app.properties'	Retrieved from ConfigMap	Available for pods
ConfigMap 'my-config'	None	Created with file data	Displayed in YAML	Used by pods

Key Moments - 2 Insights

Why does the ConfigMap key have the filename 'app.properties' instead of just the content?

Because when using --from-file, Kubernetes uses the filename as the key and the file content as the value, as shown in execution_table step 2.

What happens if the file does not exist when running the create command?

The command fails immediately because Kubernetes cannot read the file, so no ConfigMap is created (not shown in table but implied before step 2).

Visual Quiz - 3 Questions

Look at the execution table, what is the key used in the ConfigMap after step 2?

A 'app.properties'

B 'my-config'

C 'configmap'

D 'file-content'

💡 Hint

Check the 'Result' column in step 2 of the execution_table

At which step is the ConfigMap content displayed in YAML format?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for the command 'kubectl get configmap' in the execution_table

If you add multiple files with --from-file, how would the ConfigMap keys change?

A Only the first file name is used as key

B Each file name becomes a separate key

C All files are merged into one key

D Keys are numeric indexes

💡 Hint

Based on the pattern in step 2, each file name is used as a key

Concept Snapshot

kubectl create configmap <name> --from-file=<filename>
- Reads file content and stores it under the filename key
- ConfigMap can hold multiple files as keys
- Use kubectl get configmap <name> -o yaml to view
- ConfigMaps provide config data to pods easily

Full Transcript

Creating a ConfigMap from files involves preparing one or more files with configuration data. You run 'kubectl create configmap' with the --from-file option pointing to your file. Kubernetes reads the file content and creates a ConfigMap object where each file's name is the key and its content is the value. You can verify the ConfigMap by fetching it with 'kubectl get configmap' and viewing the YAML output. This ConfigMap can then be used in pod specifications to provide configuration data as environment variables or mounted files. If the file does not exist, the creation command fails. When multiple files are provided, each file name becomes a separate key in the ConfigMap.