EEdukron DevOps Library
KubernetesIntermediate12 submodules

Helm Package Management

Package Kubernetes manifests into reusable, versioned charts whose templates and values support controlled installation, upgrade, rollback, dependency, and environment variation.

How this module works

From concept to production evidence

Keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Learning outcomes

  • Explain chart structure and rendering
  • Write templates and values files
  • Install, upgrade, and roll back releases
  • Manage repositories and dependencies
  • Build custom charts for AKS

Flow diagram

Helm Package Management end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

  1. 01
    Author chartHelm Package Management stage 1: author chart with an auditable result before the next stage begins.
  2. 02
    Resolve valuesHelm Package Management stage 2: resolve values with an auditable result before the next stage begins.
  3. 03
    Render templatesHelm Package Management stage 3: render templates with an auditable result before the next stage begins.
  4. 04
    Validate manifestHelm Package Management stage 4: validate manifest with an auditable result before the next stage begins.
  5. 05
    Install or upgrade releaseHelm Package Management stage 5: install or upgrade release with an auditable result before the next stage begins.
  6. 06
    Observe and roll backHelm Package Management stage 6: observe and roll back with an auditable result before the next stage begins.

Integrated hands-on lab

Create and release an application chart

  1. Create chart structure
  2. Parameterize image, service, ingress, and resources
  3. Add a dependency
  4. Lint and render the chart
  5. Install, upgrade, and roll back on AKS

Complete module contents

12 full submodule notes

Read in order
01

Helm architecture

Helm architecture defines the major responsibilities, boundaries, and control flow that engineers use before selecting an implementation detail within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
02

Charts

Charts provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
03

Templates

Templates turns a manual or repeated decision into versioned, parameterized, testable, and observable execution within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
04

values.yaml

values.yaml turns a manual or repeated decision into versioned, parameterized, testable, and observable execution within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
05

Releases

Releases moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
06

Repositories

Repositories provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
07

Helm install

Helm install provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
08

Upgrade

Upgrade provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
09

Rollback

Rollback restores a safe service state while preserving evidence and reducing the chance that mitigation introduces a second failure within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
10

Dependencies

Dependencies provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
11

Custom charts

Custom charts provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes
12

Helm with AKS

Helm with AKS provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Helm Package Management. It is not an isolated definition: its value appears when it supports keep templates deterministic, define a stable values contract, validate rendered manifests before applying them, version chart and application independently, and make upgrades and rollback observable.

Open full notes