What is Helmfile and how does it extend Helm for managing multiple releases?

Helmfile is a declarative spec for deploying multiple Helm charts together, improving Helm for complex microservices environments. It acts as a Helm orchestration layer.

Helmfile.yaml example: repositories: - name: bitnami url: https://charts.bitnami.com/bitnami - name: stable url: https://kubernetes-charts.storage.googleapis.com environments: dev: values: - values/dev.yaml prod: values: - values/prod.yaml releases: - name: postgresql namespace: database chart: bitnami/postgresql version: 12.1.0 values: - postgresql-values.yaml - postgresql-{{ .Environment.Name }}.yaml secrets: - secrets/postgresql-{{ .Environment.Name }}.yaml - name: redis namespace: cache chart: bitnami/redis version: 17.0.0 needs: - database/postgresql # Wait for dependency - name: myapp namespace: default chart: ./myapp-chart values: - myapp-values.yaml - name: ingress-nginx namespace: ingress chart: ingress-nginx/ingress-nginx version: 4.4.2 installed: {{ .Environment.Name | eq "prod" }} hooks: pre-install: "kubectl create namespace ingress --dry-run=client -o yaml | kubectl apply -f -"

Key Helmfile commands: helmfile diff # Show changes before applying helmfile apply # Apply changes (helm upgrade --install) helmfile sync # Sync releases to desired state helmfile status # Show release statuses helmfile destroy # Delete all releases helmfile template # Render templates without applying helmfile list # List all managed releases

Advanced features:

• Templating: Helmfile supports Go templates in the spec itself
• Hooks for pre/post operations in any shell
• Needs for release ordering and dependencies
• Secrets support via helm-secrets plugin integration
• Layered values with environment-specific overrides
• Selectors to filter releases: helmfile apply --selector name=postgresql

Use cases: Platform teams managing shared infrastructure, CI/CD pipelines deploying microservices, environment promotion workflows, disaster recovery (state as code).