Why Chart templates and values.yaml in Kubernetes? - Purpose & Use Cases

The Big Idea

What if you could deploy many app versions by changing just one small file instead of dozens?

The Scenario

Imagine you need to deploy the same app many times with small differences, like different colors or names, and you write a new config file each time by hand.

The Problem

Manually copying and changing config files is slow and easy to mess up. One wrong value can break the whole app, and updating many files takes forever.

The Solution

Chart templates with values.yaml let you write one flexible template and supply different settings in values.yaml files. This way, you reuse the same template safely and quickly for many deployments.

Before vs After

✗ Before

apiVersion: v1
kind: Pod
metadata:
  name: myapp-blue
spec:
  containers:
  - name: app
    image: myimage:latest
    env:
    - name: COLOR
      value: blue

✓ After

apiVersion: v1
kind: Pod
metadata:
  name: {{ .Values.name }}
spec:
  containers:
  - name: app
    image: {{ .Values.image }}
    env:
    - name: COLOR
      value: "{{ .Values.color }}"

What It Enables

You can deploy many app versions easily by just changing values.yaml, without touching the template code.

Real Life Example

A team deploys the same web app to test, staging, and production with different settings by using one Helm chart and separate values.yaml files for each environment.

Key Takeaways

Manual config copying is slow and error-prone.

Chart templates with values.yaml separate code from settings.

This makes deploying many app versions fast and safe.