Immutable ConfigMaps in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use immutable ConfigMaps in Kubernetes?

What is the main benefit of marking a ConfigMap as immutable in Kubernetes?

A It prevents accidental or unauthorized changes to the ConfigMap after creation.

B It automatically updates all pods using the ConfigMap when the data changes.

C It allows ConfigMaps to be shared across multiple namespaces without duplication.

D It compresses the ConfigMap data to save storage space in etcd.

💡 Hint

Think about what 'immutable' means in everyday life and how it applies to configuration safety.

Immutable ConfigMaps cannot be changed after creation, which helps avoid accidental updates that could break applications.

💻 Command Output

intermediate

Output of creating an immutable ConfigMap

What is the output when you run this command to create an immutable ConfigMap?

Kubernetes

kubectl create configmap my-config --from-literal=key1=value1 --immutable=true

A configmap/my-config created

B error: unknown flag: --immutable=true

C configmap/my-config created (immutable)

D Warning: --immutable flag is deprecated

💡 Hint

Check the official kubectl create configmap command flags for immutable support.

The --immutable flag is not supported by `kubectl create configmap`, resulting in 'error: unknown flag: --immutable=true'. Use a YAML manifest with `immutable: true` to create an immutable ConfigMap.

❓ Configuration

advanced

Correct YAML for an immutable ConfigMap

Which YAML snippet correctly defines an immutable ConfigMap?

A

apiVersion: v1
kind: ConfigMap
metadata:
  name: my-config
spec:
  immutable: true
data:
  key1: value1

B

apiVersion: v1
kind: ConfigMap
metadata:
  name: my-config
  immutable: true
data:
  key1: value1

C

apiVersion: v1
kind: ConfigMap
metadata:
  name: my-config
immutable: true
data:
  key1: value1

D

apiVersion: v1
kind: ConfigMap
metadata:
  name: my-config
data:
  key1: value1
immutable: true

💡 Hint

Remember where the 'immutable' field belongs in a ConfigMap manifest.

The 'immutable' field is a top-level field in the ConfigMap manifest, at the same level as 'metadata' and 'data'. It is not nested under 'metadata' or 'spec'.

❓ Troubleshoot

advanced

Error when updating an immutable ConfigMap

You try to update an existing ConfigMap marked as immutable and get this error: configmaps "my-config" is immutable and cannot be updated. What is the best way to update the configuration?

A Use the kubectl patch command to modify the ConfigMap in place.

B Change the immutable field to false and then update the ConfigMap.

C Edit the ConfigMap directly with kubectl edit and save changes.

D Delete the existing ConfigMap and create a new one with the updated data.

💡 Hint

Immutable means no changes allowed after creation. Think about how to replace it safely.

Immutable ConfigMaps cannot be changed. To update, you must delete and recreate them with new data.

✅ Best Practice

expert

Best practice for managing immutable ConfigMaps in CI/CD pipelines

In a CI/CD pipeline, what is the best practice to handle updates to immutable ConfigMaps to ensure smooth application rollouts?

A Create a new ConfigMap with a unique name or version label and update deployments to use it.

B Patch the existing ConfigMap to add new keys without changing existing ones.

C Disable immutability temporarily during deployment and re-enable it afterward.

D Use the same ConfigMap name and rely on Kubernetes to detect changes automatically.

💡 Hint

Think about how immutable resources require new versions to be created for updates.

Since immutable ConfigMaps cannot be changed, creating new versions with unique names and updating deployments to reference them avoids downtime and ensures clear version control.

Practice

1. What is the main purpose of setting immutable: true in a Kubernetes ConfigMap?

easy

A. To delete the ConfigMap automatically after use

B. To allow automatic updates to the ConfigMap

C. To encrypt the ConfigMap data

D. To prevent any changes to the ConfigMap after creation

Solution

1. Step 1: Understand the role of immutable: true

   This setting makes the ConfigMap read-only after creation, preventing accidental or unauthorized changes.

2. Step 2: Compare with other options

   Options A, B, and D describe behaviors unrelated to immutability: automatic deletion, updates, or encryption are not controlled by this flag.

3. Final Answer:

   To prevent any changes to the ConfigMap after creation -> Option D

4. Quick Check:

   Immutable ConfigMap = No changes allowed [OK]

Hint: Immutable means no changes allowed after creation [OK]

Common Mistakes:

• Thinking immutable allows updates
• Confusing immutability with encryption
• Assuming immutable deletes the ConfigMap

2. Which of the following is the correct syntax to create an immutable ConfigMap in Kubernetes YAML?

easy

A. apiVersion: v1
kind: ConfigMap
metadata:
name: my-config
spec:
immutable: true
data:
key: value

B. apiVersion: v1
kind: ConfigMap
metadata:
name: my-config
immutable: true
data:
key: value

C. immutable: true
metadata:
name: my-config
data:
key: value

D. spec:
immutable: true
data:
key: value

Solution

1. Step 1: Identify correct placement of immutable: true

   In Kubernetes, immutable is a top-level field for ConfigMaps, at the same level as metadata and data.

2. Step 2: Validate YAML structure

   apiVersion: v1 kind: ConfigMap metadata: name: my-config immutable: true data: key: value correctly places immutable: true at top-level with proper indentation and includes required fields like apiVersion, kind, and metadata.

3. Final Answer:

   apiVersion: v1 kind: ConfigMap metadata: name: my-config immutable: true data: key: value -> Option B

4. Quick Check:

   Immutable at top-level with metadata and data [OK]

Hint: Immutable: true at top-level after metadata [OK]

Common Mistakes:

• Adding unnecessary spec section
• Putting immutable under metadata
• Missing apiVersion or kind fields

3. Given this YAML snippet for a ConfigMap with immutable: true:

apiVersion: v1
kind: ConfigMap
metadata:
  name: example-config
immutable: true
data:
  setting: old_value

What happens if you try to update setting to new_value using kubectl apply?

medium

A. The update fails with an error about immutable field

B. The update succeeds and the ConfigMap changes to new_value

C. The ConfigMap is deleted and recreated with new_value

D. The update is ignored silently, keeping old_value

Solution

1. Step 1: Understand immutable ConfigMap behavior on update

   When immutable: true is set, Kubernetes rejects any update to the ConfigMap data.

2. Step 2: Predict kubectl apply result

   Trying to change setting triggers an error indicating the ConfigMap is immutable and cannot be modified.

3. Final Answer:

   The update fails with an error about immutable field -> Option A

4. Quick Check:

   Immutable ConfigMap update = error [OK]

Hint: Immutable ConfigMaps reject updates with error [OK]

Common Mistakes:

• Expecting updates to succeed
• Thinking ConfigMap auto-recreates on update
• Assuming silent ignore of changes

4. You tried to update an immutable ConfigMap but got an error. What is the best way to apply new configuration changes?

medium

A. Edit the existing ConfigMap directly with kubectl edit

B. Delete the existing ConfigMap and create a new one with updated data

C. Create a new ConfigMap with a different name and update workloads to use it

D. Remove the immutable flag and then update the ConfigMap

Solution

1. Step 1: Understand immutable ConfigMap update restrictions

   Immutable ConfigMaps cannot be changed. Editing or removing the flag is not allowed on existing objects.

2. Step 2: Choose best practice for updates

   Creating a new ConfigMap with a new name and updating workloads to reference it ensures stability and traceability.

3. Final Answer:

   Create a new ConfigMap with a different name and update workloads to use it -> Option C

4. Quick Check:

   Immutable update = new ConfigMap + workload update [OK]

Hint: Create new ConfigMap and update pods to use it [OK]

Common Mistakes:

• Trying to edit immutable ConfigMap directly
• Deleting ConfigMap without updating workloads
• Removing immutable flag on existing ConfigMap

5. You have a deployment using an immutable ConfigMap named app-config-v1. You need to update configuration safely without downtime. What is the best approach?

hard

A. Create app-config-v2 ConfigMap with new data, update deployment to use it, then rollout pods gradually

B. Update app-config-v1 directly and restart pods immediately

C. Delete app-config-v1 and create a new ConfigMap with the same name and updated data

D. Patch the deployment to ignore ConfigMap changes and keep using old config

Solution

1. Step 1: Recognize immutable ConfigMap update constraints

   Direct updates to app-config-v1 are not possible due to immutability, so options B and C are invalid.

2. Step 2: Apply best practice for zero downtime updates

   Create a new ConfigMap app-config-v2 with updated data, update the deployment to use it, and rollout pods gradually to avoid downtime.

3. Final Answer:

   Create app-config-v2 ConfigMap, update deployment, rollout gradually -> Option A

4. Quick Check:

   Immutable update = new ConfigMap + gradual rollout [OK]

Hint: Use new ConfigMap and gradual rollout for zero downtime [OK]

Common Mistakes:

• Trying to update immutable ConfigMap directly
• Deleting ConfigMap without updating deployment
• Ignoring config changes in deployment