Creating ConfigMaps from literals in Kubernetes - Practice Exercises

Challenge - 5 Problems

💻 Command Output

intermediate

Output of creating ConfigMap with literals

What is the output of the following command when creating a ConfigMap from literals?

Kubernetes

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

A configmap/app-config configured

B configmap/app-config created

C error: missing required flag

D error: unknown flag: --from-literal

💡 Hint

Check the standard success message for kubectl create commands.

The command creates a ConfigMap named 'app-config' with two key-value pairs. The success message is 'configmap/app-config created'.

🧠 Conceptual

intermediate

Purpose of --from-literal flag in ConfigMap creation

What does the --from-literal flag do when creating a ConfigMap in Kubernetes?

A It creates a ConfigMap from key-value pairs provided directly in the command line

B It imports data from a file into the ConfigMap

C It deletes existing ConfigMaps with matching keys

D It updates the ConfigMap with values from environment variables

💡 Hint

Think about how you can provide data without using files.

The --from-literal flag allows you to specify key-value pairs directly in the command line to create a ConfigMap without needing external files.

❓ Troubleshoot

advanced

Error when creating ConfigMap with duplicate keys

What error will occur if you run this command? kubectl create configmap test-config --from-literal=key1=value1 --from-literal=key1=value2

A error: duplicate key 'key1' found

B configmap/test-config created with last key1 value

C error: unknown flag --from-literal

D configmap/test-config created with both key1 values

💡 Hint

Keys in ConfigMaps must be unique.

Using the same key twice with --from-literal causes an error because keys must be unique in a ConfigMap.

🔀 Workflow

advanced

Correct sequence to update a ConfigMap from literals

What is the correct sequence of commands to update an existing ConfigMap named 'app-config' with new literals?

A 4,3,2,1

B 2,1

C 1,2

D 3,4,1,2

💡 Hint

Use dry-run and apply to update ConfigMaps safely.

To update a ConfigMap from literals, generate the YAML with dry-run, then apply it. Direct create will fail if ConfigMap exists.

✅ Best Practice

expert

Why prefer --from-literal over manual YAML for small ConfigMaps?

Which is the best reason to use --from-literal when creating small ConfigMaps instead of writing YAML files manually?

A It automatically encrypts the ConfigMap data

B It allows storing binary data safely in ConfigMaps

C It enables version control integration automatically

D It reduces manual errors and speeds up creation for simple key-value pairs

💡 Hint

Think about convenience and error reduction.

Using --from-literal is quick and less error-prone for small ConfigMaps compared to writing YAML by hand.

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