Why configuration separation matters in Kubernetes - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a ConfigMap named 'app-config'.

Kubernetes

kubectl create configmap [1] --from-literal=key=value

Drag options to blanks, or click blank then click option'

Aconfig-app

Bapp-config

Cappconfig

Dconfigmap-app

Attempts:

3 left

💡 Hint

Common Mistakes

Using a name without a dash or incorrect order.

The ConfigMap name should be 'app-config' as specified.

2fill in blank

medium

Complete the command to apply a ConfigMap from a file named 'config.yaml'.

Kubernetes

kubectl apply -f [1]

Drag options to blanks, or click blank then click option'

Aconfig.yaml

Bconfigmap.yaml

Cconfigmap.yml

Dconfig.yml

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing '.yml' with '.yaml' or adding 'configmap' prefix.

The file to apply is 'config.yaml' as given in the instruction.

3fill in blank

hard

Fix the error in the command to create a secret named 'db-secret' with a literal password.

Kubernetes

kubectl create secret generic [1] --from-literal=password=pass123

Drag options to blanks, or click blank then click option'

Adbsecret

Bdb.secret

Cdb-secret

Ddb_secret

Attempts:

3 left

💡 Hint

Common Mistakes

Using underscores or dots instead of dashes in names.

The secret name should use dashes, so 'db-secret' is correct.

4fill in blank

hard

Fill both blanks to mount the ConfigMap 'app-config' as a volume named 'config-volume' in a pod spec.

Kubernetes

- name: [1]
  configMap:
    name: [2]

Drag options to blanks, or click blank then click option'

Aconfig-volume

Bapp-volume

Capp-config

Dconfigmap

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up volume name and ConfigMap name.

The volume name is 'config-volume' and the ConfigMap name is 'app-config'.

5fill in blank

hard

Fill both blanks to define environment variables from a ConfigMap named 'app-config' in a container spec.

Kubernetes

envFrom:
  - [1]:
    name: [2]

Drag options to blanks, or click blank then click option'

AconfigMapRef

BsecretRef

Capp-config

DconfigRef

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'secretRef' instead of 'configMapRef'.

Wrong field names.

Use 'configMapRef' to refer to ConfigMap, 'name' is the ConfigMap name 'app-config'. 'secretRef' is incorrect here.

Practice

1. Why is it important to separate configuration from application code in Kubernetes?

easy

A. It allows changing settings without modifying the application code.

B. It makes the application run faster.

C. It reduces the size of the application container.

D. It automatically fixes bugs in the application.

Solution

1. Step 1: Understand configuration separation

   Separating configuration means keeping settings outside the app code so they can be changed independently.

2. Step 2: Benefits in Kubernetes context

   This allows updates to settings without rebuilding or redeploying the app container.

3. Final Answer:

   It allows changing settings without modifying the application code. -> Option A

4. Quick Check:

   Configuration separation = Change settings without code change [OK]

Hint: Think: Can I change settings without touching app code? [OK]

Common Mistakes:

• Confusing configuration separation with performance improvements
• Thinking it reduces container size
• Assuming it fixes bugs automatically

2. Which Kubernetes resource is used to store non-sensitive configuration data separately from application code?

easy

A. ConfigMap

B. Deployment

C. Pod

D. Secret

Solution

1. Step 1: Identify resource types

   ConfigMap stores non-sensitive configuration data; Secret stores sensitive data.

2. Step 2: Match resource to question

   The question asks for non-sensitive data storage, which is ConfigMap.

3. Final Answer:

   ConfigMap -> Option A

4. Quick Check:

   Non-sensitive config = ConfigMap [OK]

Hint: ConfigMap = non-sensitive config, Secret = sensitive data [OK]

Common Mistakes:

• Choosing Secret for non-sensitive data
• Confusing Pod or Deployment as config storage
• Mixing up ConfigMap and Secret

3. Given this Kubernetes Pod spec snippet using a ConfigMap:

envFrom:
  - configMapRef:
      name: app-config

What happens if you update the ConfigMap 'app-config' while the Pod is running?

medium

A. The Pod crashes immediately.

B. The Pod automatically reloads the new configuration without restart.

C. The Pod continues using the old configuration until restarted.

D. The Pod deletes the ConfigMap.

Solution

1. Step 1: Understand envFrom with ConfigMap

   Using envFrom loads ConfigMap data as environment variables at Pod start.

2. Step 2: Effect of ConfigMap update on running Pod

   Environment variables do not update dynamically; Pod must restart to see changes.

3. Final Answer:

   The Pod continues using the old configuration until restarted. -> Option C

4. Quick Check:

   Env vars from ConfigMap update only after Pod restart [OK]

Hint: Env vars from ConfigMap update only after Pod restart [OK]

Common Mistakes:

• Assuming automatic reload without restart
• Thinking Pod crashes on ConfigMap change
• Believing ConfigMap is deleted by Pod

4. You created a Secret in Kubernetes but your Pod fails to access the secret data. Which is the most likely cause?

medium

A. Secrets cannot be used with Pods.

B. The Secret was not mounted or referenced correctly in the Pod spec.

C. The Secret data is stored in plain text and rejected.

D. The Pod must be restarted twice to access Secrets.

Solution

1. Step 1: Check how Secrets are used in Pods

   Secrets must be explicitly mounted as volumes or environment variables in Pod spec.

2. Step 2: Identify common error

   Failing to reference or mount the Secret correctly causes Pod to not see the data.

3. Final Answer:

   The Secret was not mounted or referenced correctly in the Pod spec. -> Option B

4. Quick Check:

   Secret access requires correct Pod spec reference [OK]

Hint: Always verify Secret is mounted or env referenced in Pod spec [OK]

Common Mistakes:

• Believing Secrets can't be used with Pods
• Thinking Secret data must be plain text
• Assuming multiple restarts fix Secret access

5. You want to deploy the same application to development and production environments with different database URLs. How does separating configuration help achieve this in Kubernetes?

hard

A. By embedding the URLs directly in the Pod spec containers' command lines.

B. By building separate container images for each environment with hardcoded URLs.

C. By manually editing the application code before each deployment.

D. By using different ConfigMaps or Secrets for each environment without changing the app code.

Solution

1. Step 1: Understand environment-specific configuration

   Different environments need different settings like database URLs.

2. Step 2: Use Kubernetes configuration separation

   Using ConfigMaps or Secrets per environment allows changing settings without code changes.

3. Step 3: Avoid rebuilding or editing code

   This approach avoids building multiple images or manual code edits.

4. Final Answer:

   By using different ConfigMaps or Secrets for each environment without changing the app code. -> Option D

5. Quick Check:

   Separate config per environment = different ConfigMaps/Secrets [OK]

Hint: Use separate ConfigMaps/Secrets per environment, no code change needed [OK]

Common Mistakes:

• Building separate images for each environment
• Hardcoding URLs in Pod commands
• Editing app code manually for each deploy