← All insightsConcepts

Helm: core concepts and configuration explained

CodeWizard Academy · 3 September 2026 · 3 min read · Beginner

The package manager for Kubernetes - template, version and release your manifests as charts. This walkthrough covers the mental model and the configuration you will actually touch.

Helm packages Kubernetes manifests into versioned, parameterized 'charts' so you can install, upgrade and roll back an entire application with a single command and a values file.

The configuration that matters

A templated Deployment snippet plus its values.yaml.

yaml
# templates/deployment.yaml
spec:
  replicas: {{ .Values.replicaCount }}
  template:
    spec:
      containers:
        - name: {{ .Chart.Name }}
          image: "{{ .Values.image.repo }}:{{ .Values.image.tag }}"
---
# values.yaml
replicaCount: 3
image:
  repo: ghcr.io/acme/web
  tag: "1.0"

Principles to hold onto

  • Pin dependency versions in Chart.yaml and commit Chart.lock
  • Use --atomic and --wait so failed upgrades roll back automatically
  • Validate rendered output with kubeconform/kube-linter in CI

Everyday commands

bash
helm upgrade --install web ./mychart -n prod --create-namespace \
  -f values.prod.yaml --atomic --wait
helm history web -n prod
helm rollback web 1 -n prod

Want senior help putting Helm to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult