Creating ConfigMaps from files in Kubernetes - Step-by-Step CLI Walkthrough

Introduction

Sometimes your application needs configuration data like settings or keys. Kubernetes ConfigMaps let you store this data separately from your app code. Creating ConfigMaps from files helps you keep configuration organized and easy to update.

When you want to provide environment-specific settings to your app without changing the app itself

When you have multiple configuration files that your app needs to read

When you want to update configuration without rebuilding your container image

When you want to share configuration data across multiple pods

When you want to keep sensitive data separate from your app code (non-secret data)

Commands

This command creates a ConfigMap named 'my-config' using the contents of the file 'app.properties'. Kubernetes stores the file content as key-value pairs inside the ConfigMap.

Terminal

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

Expected Output

configmap/my-config created

→

--from-file - Specifies the file to use as the source for the ConfigMap data

This command shows the details of the ConfigMap 'my-config' in YAML format so you can verify the data was stored correctly.

Terminal

kubectl get configmaps my-config -o yaml

Expected Output

apiVersion: v1

kind: ConfigMap

metadata:

  name: my-config

data:

  app.properties: |

    # content of app.properties file here

    key1=value1

    key2=value2

→

-o yaml - Outputs the ConfigMap details in YAML format

This command creates a ConfigMap named 'multi-config' from two files, 'config1.txt' and 'config2.txt'. Each file's content is stored under its filename as a key.

Terminal

kubectl create configmap multi-config --from-file=config1.txt --from-file=config2.txt

Expected Output

configmap/multi-config created

→

--from-file - Can be used multiple times to add multiple files to the ConfigMap

This command shows a summary of the 'multi-config' ConfigMap, including the keys (filenames) it contains and their sizes.

Terminal

kubectl describe configmap multi-config

Expected Output

Name:         multi-config

Namespace:    default

Labels:       <none>

Annotations:  <none>

Data

====

config1.txt:

  25 bytes

config2.txt:

  30 bytes

Events:       <none>

Key Concept

If you remember nothing else from this pattern, remember: ConfigMaps let you store configuration data from files so your app can use it without changing the app image.

Common Mistakes

Using a directory path instead of a file path with --from-file

The command expects a file, not a directory, so it will fail or create an empty ConfigMap

Specify the exact file path for each --from-file flag

Not verifying the ConfigMap content after creation

You might think the ConfigMap has the right data but it could be empty or incorrect

Always run 'kubectl get configmaps NAME -o yaml' or 'kubectl describe configmap NAME' to check

Using the same filename multiple times with --from-file

Keys in ConfigMaps must be unique; duplicate filenames will overwrite previous data silently

Ensure each file has a unique name or use --from-file=key=filepath to set custom keys

Summary

Use 'kubectl create configmap NAME --from-file=filename' to create a ConfigMap from a file.

Verify the ConfigMap content with 'kubectl get configmaps NAME -o yaml' or 'kubectl describe configmap NAME'.

You can add multiple files by repeating the --from-file flag for each file.

Practice

1. What is the main purpose of creating a ConfigMap from a file in Kubernetes?

easy

A. To deploy a new pod automatically

B. To create a new container image

C. To monitor resource usage of pods

D. To store configuration data separately from application code

Solution

1. Step 1: Understand ConfigMap role

   ConfigMaps hold configuration data separately from app code to keep apps flexible.

2. Step 2: Recognize file usage

   Creating ConfigMaps from files allows easy management of config data outside the container image.

3. Final Answer:

   To store configuration data separately from application code -> Option D

4. Quick Check:

   ConfigMap purpose = separate config storage [OK]

Hint: ConfigMaps separate config from code for flexibility [OK]

Common Mistakes:

• Confusing ConfigMaps with container images
• Thinking ConfigMaps deploy pods
• Assuming ConfigMaps monitor resources

2. Which of the following is the correct command to create a ConfigMap named app-config from a file called settings.conf?

easy

A. kubectl create configmap app-config --from-file=settings.conf

B. kubectl create configmap --name=app-config settings.conf

C. kubectl configmap create app-config settings.conf

D. kubectl create configmap app-config -f settings.conf

Solution

1. Step 1: Recall correct syntax for creating ConfigMap from file

   The correct syntax is kubectl create configmap [name] --from-file=[filename].

2. Step 2: Match command with syntax

   kubectl create configmap app-config --from-file=settings.conf matches the syntax exactly: kubectl create configmap app-config --from-file=settings.conf.

3. Final Answer:

   kubectl create configmap app-config --from-file=settings.conf -> Option A

4. Quick Check:

   Correct syntax uses --from-file=filename [OK]

Hint: Use --from-file=filename after configmap name [OK]

Common Mistakes:

• Using -f instead of --from-file
• Placing filename without --from-file flag
• Wrong command order or flags

3. Given the command kubectl create configmap my-config --from-file=app.properties, what will be the key name inside the ConfigMap if the file is named app.properties?

medium

A. app

B. my-config

C. app.properties

D. configmap

Solution

1. Step 1: Understand key naming in ConfigMaps from files

   When creating a ConfigMap from a file without specifying a key, the filename is used as the key.

2. Step 2: Apply to given filename

   Since the file is named app.properties, the key inside the ConfigMap will be app.properties.

3. Final Answer:

   app.properties -> Option C

4. Quick Check:

   Filename = key name in ConfigMap [OK]

Hint: Filename becomes key if no key specified [OK]

Common Mistakes:

• Assuming ConfigMap name is the key
• Using partial filename as key
• Confusing key with ConfigMap name

4. You run kubectl create configmap test-config --from-file=config.txt but get an error saying the file does not exist. What is the most likely cause?

medium

A. The ConfigMap name is invalid

B. The file config.txt is not in the current directory

C. You need to use --from-env-file instead

D. kubectl command does not support --from-file

Solution

1. Step 1: Check file existence requirement

   The --from-file flag requires the file to exist in the current directory or given path.

2. Step 2: Identify cause of error

   If the file is missing or path is wrong, kubectl will error that the file does not exist.

3. Final Answer:

   The file config.txt is not in the current directory -> Option B

4. Quick Check:

   File must exist where command runs [OK]

Hint: Check file path and existence before creating ConfigMap [OK]

Common Mistakes:

• Assuming ConfigMap name causes file error
• Using wrong flag instead of --from-file
• Ignoring file location or path

5. You have two config files: db.conf and app.conf. You want to create a single ConfigMap named multi-config containing both files as keys. Which command should you use?

hard

A. kubectl create configmap multi-config --from-file=db.conf --from-file=app.conf

B. kubectl create configmap multi-config --from-file=db.conf,app.conf

C. kubectl create configmap multi-config --from-file=./db.conf ./app.conf

D. kubectl create configmap multi-config -f db.conf -f app.conf

Solution

1. Step 1: Understand multiple file syntax

   To add multiple files, use multiple --from-file flags, one per file.

2. Step 2: Match correct command format

   kubectl create configmap multi-config --from-file=db.conf --from-file=app.conf uses two --from-file flags correctly: --from-file=db.conf --from-file=app.conf.

3. Final Answer:

   kubectl create configmap multi-config --from-file=db.conf --from-file=app.conf -> Option A

4. Quick Check:

   Multiple files = multiple --from-file flags [OK]

Hint: Use one --from-file per file to add multiple files [OK]

Common Mistakes:

• Trying to list files separated by commas
• Using -f flag which is for manifests
• Passing multiple files without repeating --from-file