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

Introduction

Sometimes you need to store small pieces of configuration data directly in Kubernetes without creating files. Creating ConfigMaps from literals lets you do this by typing the data right in the command line. This helps keep your app settings organized and easy to change.

When you want to quickly add a few configuration values to your app without making a file.

When you need to test different settings by changing values on the fly.

When you want to share simple environment variables with your pods.

When you want to keep configuration separate from your app code but don't want extra files.

When you want to update small config values without redeploying your app.

Commands

This command creates a ConfigMap named 'example-config' with two key-value pairs: APP_MODE set to 'production' and LOG_LEVEL set to 'info'. We use --from-literal to add each pair directly from the command line.

Terminal

kubectl create configmap example-config --from-literal=APP_MODE=production --from-literal=LOG_LEVEL=info

Expected Output

configmap/example-config created

→

--from-literal - Adds a key-value pair directly from the command line to the ConfigMap

This command shows the full details of the ConfigMap 'example-config' in YAML format so you can verify the keys and values were set correctly.

Terminal

kubectl get configmap example-config -o yaml

Expected Output

apiVersion: v1

kind: ConfigMap

metadata:

  name: example-config

data:

  APP_MODE: production

  LOG_LEVEL: info

→

-o yaml - Outputs the resource details in YAML format

This command gives a human-readable summary of the ConfigMap, showing the keys and their values clearly.

Terminal

kubectl describe configmap example-config

Expected Output

Name:         example-config

Namespace:    default

Labels:       <none>

Annotations:  <none>

Data

====

APP_MODE:

production

LOG_LEVEL:

info

Events:       <none>

Key Concept

If you remember nothing else from this pattern, remember: --from-literal lets you create ConfigMaps quickly by typing key-value pairs directly in the command line.

Common Mistakes

Using spaces around the equal sign in --from-literal like --from-literal=APP_MODE = production

The command treats spaces as separate arguments, causing errors or wrong key-value parsing.

Write the key and value without spaces: --from-literal=APP_MODE=production

Trying to create a ConfigMap with duplicate keys using multiple --from-literal flags

Kubernetes will only keep one value per key, so duplicates cause confusion or overwrite.

Use unique keys for each --from-literal flag.

Not verifying the ConfigMap after creation

You might think the ConfigMap was created correctly but it could have missing or wrong data.

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

Summary

Use 'kubectl create configmap NAME --from-literal=key=value' to create ConfigMaps from command line values.

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

Avoid spaces around equal signs and duplicate keys when using --from-literal.

Practice

1. What does the kubectl create configmap command with the --from-literal option do?

easy

A. Lists all ConfigMaps in the current namespace

B. Deletes an existing ConfigMap by specifying literal values

C. Updates a ConfigMap with values from a file

D. Creates a ConfigMap with key-value pairs directly from command line literals

Solution

1. Step 1: Understand the command purpose

   The kubectl create configmap command is used to create a new ConfigMap resource in Kubernetes.

2. Step 2: Role of --from-literal

   The --from-literal option allows adding key-value pairs directly from the command line as literals, without needing a file.

3. Final Answer:

   Creates a ConfigMap with key-value pairs directly from command line literals -> Option D

4. Quick Check:

   Creating ConfigMap from literals = Creates a ConfigMap with key-value pairs directly from command line literals [OK]

Hint: Remember: --from-literal adds key=value pairs directly [OK]

Common Mistakes:

• Confusing create with delete commands
• Thinking --from-literal reads from files
• Assuming it lists ConfigMaps

2. Which of the following is the correct syntax to create a ConfigMap named app-config with two literals: mode=production and debug=false?

easy

A. kubectl create configmap app-config --from-literal=mode=production --from-literal=debug=false

B. kubectl create configmap app-config --from-literal mode=production debug=false

C. kubectl create configmap app-config --from-literal mode=production --from-literal debug false

D. kubectl create configmap app-config --from-literal=mode production --from-literal=debug false

Solution

1. Step 1: Check correct option format for literals

   The correct syntax requires each literal to be passed with --from-literal=key=value format.

2. Step 2: Validate kubectl create configmap app-config --from-literal=mode=production --from-literal=debug=false

   kubectl create configmap app-config --from-literal=mode=production --from-literal=debug=false uses --from-literal=mode=production and --from-literal=debug=false, which is the correct syntax.

3. Final Answer:

   kubectl create configmap app-config --from-literal=mode=production --from-literal=debug=false -> Option A

4. Quick Check:

   Correct literal syntax uses '=' after --from-literal [OK]

Hint: Use '=' immediately after --from-literal for each key=value pair [OK]

Common Mistakes:

• Omitting '=' after --from-literal
• Passing multiple literals without repeating --from-literal
• Using spaces instead of '=' between key and value

3. What will be the output of the command?

kubectl create configmap test-config --from-literal=env=dev --from-literal=version=1.2

Then run:

kubectl get configmap test-config -o yaml

medium

A. A ConfigMap named 'test-config' with data keys 'env' and 'version' set to 'dev' and '1.2'

B. An error because multiple --from-literal options are not allowed

C. A ConfigMap with keys 'env=dev' and 'version=1.2' as single strings

D. Empty ConfigMap with no data

Solution

1. Step 1: Understand multiple literals usage

   The command uses two --from-literal options, which is valid to add multiple key-value pairs.

2. Step 2: Output of kubectl get configmap -o yaml

   The output YAML will show a ConfigMap named 'test-config' with a data section containing keys 'env' and 'version' with their respective values.

3. Final Answer:

   A ConfigMap named 'test-config' with data keys 'env' and 'version' set to 'dev' and '1.2' -> Option A

4. Quick Check:

   Multiple literals create multiple keys in ConfigMap data [OK]

Hint: Multiple --from-literal options add multiple keys [OK]

Common Mistakes:

• Thinking multiple literals cause errors
• Expecting keys to include '=' sign
• Assuming ConfigMap data is empty

4. You run this command:

kubectl create configmap my-config --from-literal=key1=value1 key2=value2

But it fails with an error. What is the likely cause?

medium

A. The command does not support any literals

B. Missing '=' after --from-literal for the second key-value pair

C. ConfigMap name 'my-config' is invalid

D. You must use --from-file instead of --from-literal

Solution

1. Step 1: Analyze command syntax

   The command uses --from-literal=key1=value1 correctly but then adds key2=value2 without --from-literal=.

2. Step 2: Understand correct usage

   Each literal must be preceded by its own --from-literal= option. Omitting it causes a syntax error.

3. Final Answer:

   Missing '=' after --from-literal for the second key-value pair -> Option B

4. Quick Check:

   Each literal needs its own --from-literal= [OK]

Hint: Repeat --from-literal= for each key=value pair [OK]

Common Mistakes:

• Passing multiple literals without repeating --from-literal
• Assuming one --from-literal can take multiple pairs
• Confusing --from-literal with --from-file

5. You want to create a ConfigMap named app-settings with these key-value pairs:
env=production, debug=false, and timeout=0. You run:

kubectl create configmap app-settings --from-literal=env=production --from-literal=debug=false --from-literal=timeout=0

Later, you mount this ConfigMap as environment variables in a Pod. What should you be careful about regarding the timeout value?

hard

A. The timeout key will be converted to boolean false automatically

B. The value '0' will be ignored because it is falsy

C. The value '0' is a string and will be passed as "0", not as a number zero

D. The ConfigMap will fail to create because '0' is invalid

Solution

1. Step 1: Understand ConfigMap data types

   ConfigMaps store all values as strings, so '0' is stored as the string "0".

2. Step 2: Effect when used as environment variable

   When mounted as environment variables, the value will be "0" (string), not a numeric zero or boolean false.

3. Final Answer:

   The value '0' is a string and will be passed as "0", not as a number zero -> Option C

4. Quick Check:

   ConfigMap values are strings, even '0' [OK]

Hint: ConfigMap values are always strings, watch for '0' as string [OK]

Common Mistakes:

• Assuming '0' is treated as false or ignored
• Expecting automatic type conversion
• Thinking ConfigMap creation fails with '0' value