Helm Charts Overview

This section contains ready-to-study Helm chart examples. The goal is to move from hand-written manifests to reusable application packages that can be installed, upgraded, rolled back, and configured with values.

What a Helm chart gives you

• A standard folder structure for packaging Kubernetes resources.
• Templates that turn one deployment model into many environment-specific releases.
• A values.yaml file that centralizes the settings you change most often.
• A repeatable install and upgrade workflow for multi-resource applications.

How to approach these examples

• Start by reading Chart.yaml, values.yaml, and the templates/ folder in one chart.
• Compare how each chart exposes image settings, service configuration, ingress, and replica counts.
• Notice which values are meant to be changed per environment and which parts stay stable.

Charts in this section

• nginx-chart/ is a simple starting point for understanding Helm structure.
• ecom-app-chart/, inventory-order-chart/, and product-app-chart/ show more application-focused chart layouts.

Suggested practice

1. Run helm lint on one chart.
2. Render the manifests with helm template before installing anything.
3. Change a few values, re-render, and inspect how the output changes.
4. Install the chart into a test namespace once the rendered YAML looks correct.