Chart values and customization in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Helm install with custom values

You run the command helm install myapp ./mychart -f custom-values.yaml. The custom-values.yaml contains replicaCount: 3. What will be the number of replicas in the deployed Kubernetes Deployment?

A 1

B 3

C 0

D The command will fail due to missing replicaCount

💡 Hint

The -f flag overrides default values in the chart.

The replicaCount value in custom-values.yaml overrides the default, so the Deployment will have 3 replicas.

🧠 Conceptual

intermediate

Purpose of Helm values.yaml file

What is the main purpose of the values.yaml file in a Helm chart?

A To store default configuration values for the chart templates

B To define Kubernetes resource manifests directly

C To execute Helm commands automatically

D To store Helm release history

💡 Hint

Think about where default settings for templates come from.

The values.yaml file holds default values that templates use to generate Kubernetes manifests.

❓ Troubleshoot

advanced

Troubleshooting Helm value override failure

You try to override the image tag by running helm install myapp ./mychart --set image.tag=2.0, but the deployed pod still uses the old tag. What is the most likely cause?

A Helm does not support overriding values with <code>--set</code>

B The <code>--set</code> flag syntax is incorrect

C The Kubernetes cluster caches old images and ignores new tags

D The chart template does not use the <code>image.tag</code> value correctly

💡 Hint

Check if the template references the value you are overriding.

If the template does not use the image.tag value, overriding it has no effect.

🔀 Workflow

advanced

Correct order to customize and deploy a Helm chart

Arrange the steps in the correct order to customize and deploy a Helm chart with your own values.

A 3,1,2,4

B 1,3,2,4

C 3,2,1,4

D 2,3,1,4

💡 Hint

Think about preparing the chart, customizing values, deploying, then checking.

First get the chart, then customize values, deploy with those values, and finally verify deployment.

✅ Best Practice

expert

Best practice for managing sensitive data in Helm values

Which is the best practice for managing sensitive data like passwords in Helm chart values?

A Store sensitive data directly in values.yaml and commit to version control

B Hardcode sensitive data in Kubernetes manifests inside the chart templates

C Use Helm secrets or external secret management tools to encrypt sensitive values

D Ignore sensitive data and rely on Kubernetes default security

💡 Hint

Think about security and version control safety.

Using Helm secrets or external tools encrypts sensitive data and avoids exposing it in plain text.

Practice

1. What is the main purpose of the values.yaml file in a Helm chart?

easy

A. To define Kubernetes cluster nodes

B. To store the application source code

C. To provide default configuration values for the chart

D. To list all installed Helm charts

Solution

1. Step 1: Understand the role of values.yaml

   The values.yaml file contains default settings that the Helm chart uses when installing an app.

2. Step 2: Compare other options

   Options B, C, and D describe unrelated tasks: source code, cluster nodes, and installed charts, which are not the purpose of values.yaml.

3. Final Answer:

   To provide default configuration values for the chart -> Option C

4. Quick Check:

   Default config = values.yaml [OK]

Hint: Remember: values.yaml holds default settings [OK]

Common Mistakes:

• Confusing values.yaml with application code
• Thinking values.yaml manages cluster nodes
• Assuming values.yaml lists installed charts

2. Which of the following is the correct way to override a Helm chart value from the command line?

easy

A. helm install myapp ./chart --set image.tag=1.2.3

B. helm install myapp ./chart -override image.tag=1.2.3

C. helm install myapp ./chart --config image.tag=1.2.3

D. helm install myapp ./chart --change image.tag=1.2.3

Solution

1. Step 1: Recall Helm syntax for setting values

   The correct flag to override values is --set, followed by the key=value pair.

2. Step 2: Check other options for correctness

   Options A, C, and D use invalid flags (-override, --config, --change) which Helm does not recognize.

3. Final Answer:

   helm install myapp ./chart --set image.tag=1.2.3 -> Option A

4. Quick Check:

   Override values with --set [OK]

Hint: Use --set key=value to override values [OK]

Common Mistakes:

• Using incorrect flags like --config or --change
• Forgetting to use --set for overrides
• Misplacing the key=value syntax

3. Given this snippet from values.yaml:

replicaCount: 2
image:
  repository: nginx
  tag: stable

What will be the replica count if you run:

helm install myapp ./chart --set replicaCount=5

medium

A. 2

B. 5

C. stable

D. nginx

Solution

1. Step 1: Understand default and override values

   The default replicaCount is 2 from values.yaml. The command line uses --set replicaCount=5 to override it.

2. Step 2: Determine final replica count

   Overrides from --set take priority, so replicaCount becomes 5.

3. Final Answer:

   5 -> Option B

4. Quick Check:

   Command line override changes replicaCount to 5 [OK]

Hint: Command line --set overrides values.yaml [OK]

Common Mistakes:

• Ignoring command line overrides
• Confusing image tag or repository with replicaCount
• Assuming default always applies

4. You tried to override a nested value with helm install myapp ./chart --set image.tag=1.0.0, but the deployment still uses the old tag. What is the most likely cause?

medium

A. The chart does not use the image.tag value in templates

B. You must use --set-string instead of --set

C. The values.yaml file is missing

D. You need to delete the release before installing

Solution

1. Step 1: Check if the chart templates use the overridden value

   If the chart templates do not reference image.tag, overriding it has no effect.

2. Step 2: Evaluate other options

   Using --set-string is only needed for forcing string types, not usually for tags. Missing values.yaml would cause defaults to fail, and deleting release is unrelated to value overrides.

3. Final Answer:

   The chart does not use the image.tag value in templates -> Option A

4. Quick Check:

   Override ignored if template doesn't use value [OK]

Hint: Ensure templates use the value you override [OK]

Common Mistakes:

• Assuming --set always works without template usage
• Confusing --set and --set-string flags
• Thinking release deletion is needed for overrides

5. You want to customize a Helm chart to deploy multiple instances of the same app with different configurations. Which approach best supports this?

hard

A. Install the chart once and manually edit Kubernetes resources

B. Edit the chart source code to hardcode different values

C. Use helm upgrade without changing values

D. Create separate values.yaml files for each instance and install with --values

Solution

1. Step 1: Understand multi-instance customization

   Using separate values.yaml files allows you to define different settings for each instance without changing the chart code.

2. Step 2: Evaluate other options

   Editing chart source is complex and error-prone. Using helm upgrade without changes won't customize. Manually editing resources breaks Helm management.

3. Final Answer:

   Create separate values.yaml files for each instance and install with --values -> Option D

4. Quick Check:

   Use multiple values files for multi-instance customization [OK]

Hint: Use different values files per instance with --values [OK]

Common Mistakes:

• Hardcoding values in chart source
• Ignoring Helm's value override features
• Manually editing deployed resources