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.