Creating ConfigMaps from literals in Kubernetes - Quick Revision & Summary

Recall & Review

beginner

What is a ConfigMap in Kubernetes?

A ConfigMap is a Kubernetes object used to store non-confidential configuration data in key-value pairs. It helps separate configuration from container images, making apps easier to manage.

beginner

How do you create a ConfigMap from literals using kubectl?

Use the command:
kubectl create configmap <name> --from-literal=key1=value1 --from-literal=key2=value2
This creates a ConfigMap with keys and values directly from the command line.

beginner

Why use literals to create ConfigMaps instead of files?

Literals let you quickly create small ConfigMaps without needing separate files. It's like writing a quick note instead of printing a whole page.

beginner

What command shows the data inside a ConfigMap?

Use kubectl describe configmap <name> or kubectl get configmap <name> -o yaml to see the stored key-value pairs.

intermediate

Can you update a ConfigMap created from literals directly with kubectl?

No, you cannot update literals directly. You must delete and recreate the ConfigMap or use kubectl edit configmap <name> to modify it.

Which command creates a ConfigMap named 'app-config' with a key 'mode' set to 'production' using literals?

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

B kubectl create configmap app-config --from-file=mode=production

C kubectl apply configmap app-config --from-literal=mode=production

D kubectl configmap create app-config --literal=mode=production

The correct syntax to create a ConfigMap from literals is 'kubectl create configmap --from-literal=key=value'.

What does the command 'kubectl create configmap my-config --from-literal=env=dev --from-literal=debug=true' do?

A Creates a file named 'my-config' with environment variables

B Updates an existing ConfigMap named 'my-config'

C Creates a ConfigMap named 'my-config' with keys 'env' and 'debug' set to 'dev' and 'true'

D Deletes the ConfigMap named 'my-config'

This command creates a new ConfigMap with two key-value pairs from literals.

How can you view the contents of a ConfigMap named 'settings'?

A kubectl get configmap settings -o yaml

B kubectl create configmap settings

C kubectl delete configmap settings

D kubectl run configmap settings

The command 'kubectl get configmap -o yaml' shows the full details of the ConfigMap.

If you want to add a new key-value pair to an existing ConfigMap created from literals, what should you do?

A ConfigMaps cannot be changed once created

B Use 'kubectl create configmap' again with the new key

C Use 'kubectl add literal' command

D Delete and recreate the ConfigMap with all key-value pairs including the new one

ConfigMaps created from literals cannot be updated directly; you must recreate them with all desired data.

What is the main benefit of using ConfigMaps in Kubernetes?

A Runs containers faster

B Separates configuration from application code

C Stores sensitive passwords securely

D Manages network policies

ConfigMaps help keep configuration data separate from container images, making apps easier to manage and update.

Explain how to create a ConfigMap from literals and why you might choose this method.

Think about creating small config data directly from the command line.

Describe how to check the contents of a ConfigMap and how to update it if needed.

Viewing is easy, but updating literals requires a special approach.

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