Installing charts in Kubernetes - Visual Walkthrough

Process Flow - Installing charts

Start: Have Helm installed

↓

Add Helm repo

↓

Update repo to get latest charts

↓

Search for chart

↓

Install chart with helm install

↓

Verify installation

↓

Done

This flow shows the steps to install a Helm chart: add repo, update, search, install, and verify.

Execution Sample

Kubernetes

helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo update
helm search repo bitnami/nginx
helm install my-nginx bitnami/nginx
kubectl get pods

This sequence adds a repo, updates it, searches for nginx chart, installs it, and checks pods.

Process Table

Step	Command	Action	Result/Output
1	helm repo add bitnami https://charts.bitnami.com/bitnami	Add bitnami repo	Repository "bitnami" has been added
2	helm repo update	Update repo info	Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "bitnami" chart repository
3	helm search repo bitnami/nginx	Search for nginx chart	NAME CHART VERSION APP VERSION DESCRIPTION bitnami/nginx 13.2.24 1.24.0 Chart for the nginx web server
4	helm install my-nginx bitnami/nginx	Install nginx chart	NAME: my-nginx LAST DEPLOYED: <timestamp> NAMESPACE: default STATUS: deployed ...
5	kubectl get pods	Check pods status	NAME READY STATUS RESTARTS AGE my-nginx-xxxxxxxxxx-xxxxx 1/1 Running 0 1m
6			Installation complete, nginx pod is running

💡 Installation stops after verifying pod is running successfully

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	After Step 5	Final
Helm Repos	[]	[bitnami]	[bitnami]	[bitnami]	[bitnami]	[bitnami]
Chart Info	None	None	Latest bitnami/nginx info	Installed my-nginx	my-nginx pod running	my-nginx pod running

Key Moments - 3 Insights

Why do we run 'helm repo update' after adding a repo?

Because adding a repo only registers it locally; 'helm repo update' fetches the latest charts from that repo, as shown in step 2 of the execution_table.

What does 'helm install my-nginx bitnami/nginx' do exactly?

It downloads the nginx chart from the bitnami repo and deploys it to Kubernetes with the release name 'my-nginx', as seen in step 4 where the status is 'deployed'.

How do we know the chart installed successfully?

By running 'kubectl get pods' and seeing the pod status as 'Running' in step 5, confirming the app is up.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output of 'helm repo add' command?

A NAME: my-nginx LAST DEPLOYED: <timestamp>

B Successfully got an update from the "bitnami" chart repository

C Repository "bitnami" has been added

D NAME CHART VERSION APP VERSION DESCRIPTION

💡 Hint

Check step 1 in the execution_table under Result/Output column

At which step does the nginx pod become Running?

A Step 3

B Step 5

C Step 4

D Step 2

💡 Hint

Look at the 'kubectl get pods' command output in step 5

If you skip 'helm repo update', what will likely happen when you run 'helm search repo'?

A You might see outdated or no chart info

B You get an error saying repo not found

C You get the latest chart info

D The chart installs automatically

💡 Hint

Refer to step 2 and 3 in execution_table showing update then search

Concept Snapshot

Installing Helm charts:
1. Add repo: helm repo add <name> <url>
2. Update repo: helm repo update
3. Search charts: helm search repo <chart>
4. Install chart: helm install <release> <chart>
5. Verify with kubectl get pods
Always update repo before searching or installing.

Full Transcript

To install a Helm chart, first add the chart repository using 'helm repo add'. Then update your local repo info with 'helm repo update' to get the latest charts. Search for the desired chart using 'helm search repo'. Install the chart with 'helm install' giving it a release name. Finally, verify the installation by checking pod status with 'kubectl get pods'. This ensures your app is running correctly.

Practice

1. What is the primary purpose of using helm install in Kubernetes?

easy

A. To deploy an application packaged as a Helm chart

B. To delete a Kubernetes namespace

C. To update the Kubernetes cluster version

D. To create a new Kubernetes node

Solution

1. Step 1: Understand Helm's role

   Helm packages Kubernetes apps into charts for easy deployment.

2. Step 2: Purpose of helm install

   This command deploys the packaged app (chart) into the cluster.

3. Final Answer:

   To deploy an application packaged as a Helm chart -> Option A

4. Quick Check:

   Helm install = deploy app [OK]

Hint: Helm install means deploy app from chart [OK]

Common Mistakes:

• Confusing install with delete or update commands
• Thinking helm install creates nodes
• Assuming helm install manages cluster versions

2. Which of the following is the correct syntax to install a Helm chart named nginx with release name myweb?

easy

A. helm install nginx myweb

B. helm create myweb nginx

C. helm install myweb nginx

D. helm deploy myweb nginx

Solution

1. Step 1: Recall Helm install syntax

   The correct syntax is helm install [release-name] [chart-name].

2. Step 2: Match syntax to options

   helm install myweb nginx uses helm install myweb nginx, which matches the syntax.

3. Final Answer:

   helm install myweb nginx -> Option C

4. Quick Check:

   helm install release chart = helm install myweb nginx [OK]

Hint: Remember: helm install release-name chart-name [OK]

Common Mistakes:

• Swapping release name and chart name order
• Using helm create or helm deploy instead of install
• Omitting release name

3. What will be the output of the command helm install myapp bitnami/nginx --namespace web if the namespace web does not exist?

medium

A. Helm will prompt to create the namespace interactively

B. Helm will create the namespace web and install the chart

C. Helm will install the chart in the default namespace

D. Installation will fail with an error about missing namespace

Solution

1. Step 1: Understand namespace behavior

   Helm does not create namespaces automatically during install.

2. Step 2: Effect of missing namespace

   If the specified namespace web does not exist, Helm will error out.

3. Final Answer:

   Installation will fail with an error about missing namespace -> Option D

4. Quick Check:

   Missing namespace causes install error [OK]

Hint: Helm won't create namespaces automatically [OK]

Common Mistakes:

• Assuming Helm auto-creates namespaces
• Expecting install to default namespace silently
• Thinking Helm prompts for namespace creation

4. You run helm install myapp nginx --set replicaCount=3 but the app still runs with 1 replica. What is the likely cause?

medium

A. You must specify the namespace with --namespace

B. The chart does not support the replicaCount parameter

C. The --set flag syntax is incorrect

D. The Helm client version is outdated

Solution

1. Step 1: Check parameter support

   Not all charts support all parameters; replicaCount must be defined in the chart's values.

2. Step 2: Effect of unsupported parameter

   If unsupported, setting replicaCount has no effect, so default 1 replica remains.

3. Final Answer:

   The chart does not support the replicaCount parameter -> Option B

4. Quick Check:

   Unsupported param means no effect [OK]

Hint: Check if chart supports your --set keys [OK]

Common Mistakes:

• Assuming all charts accept replicaCount
• Thinking namespace affects replica count
• Believing --set syntax is always wrong
• Blaming Helm version without checking chart

5. You want to install a Helm chart myapp with a custom image tag v2.0 and in namespace production. Which command correctly does this in one step?

hard

A. helm install myapp ./myapp-chart --set image.tag=v2.0 --namespace production

B. helm install ./myapp-chart myapp --set image.tag=v2.0 --namespace production

C. helm install myapp ./myapp-chart --image.tag=v2.0 --namespace production

D. helm install myapp ./myapp-chart --set image=v2.0 --namespace production

Solution

1. Step 1: Confirm Helm install syntax

   The syntax is helm install [release-name] [chart-path] [flags].

2. Step 2: Correct use of --set and namespace

   Use --set image.tag=v2.0 to override image tag and --namespace production to specify namespace.

3. Final Answer:

   helm install myapp ./myapp-chart --set image.tag=v2.0 --namespace production -> Option A

4. Quick Check:

   Release, chart, --set key=value, --namespace [OK]

Hint: Use --set key=value and --namespace together [OK]

Common Mistakes:

• Swapping release name and chart path
• Using --image.tag instead of --set
• Setting wrong key like image=v2.0
• Omitting namespace flag