Configuration as Code (CaC): Helms

1. Configuration as Code in the Cloud Stack

• IaC: clusters, networks, VMs (Terraform, Crossplan)
• CaC: runtime app/plaform configuration (Helm, Kustomize, YAML overlays)
• Why CaC:
  • Reproducibility
  • Reviewability
  • "Diff-able" ops
  • Promotion across environments

2. Helm Fundamentals

What Helm does?

• packaging (charts),
• templating (Go templates),
• release management (history/rollback)

Key objects

• Chart, Chart.yaml, templates/, values.yaml, values.schema.json

Release lifecycle: install → upgrade --reuse-values → rollback → uninstall

Security note: values may include secrets → never commit raw secrets