Hi! I’ve built and maintain an open-source Helm chart for n8n as part of [HelmForge]( GitHub - helmforgedev/charts: Production-ready Helm charts with built-in S3 backup for Kubernetes · GitHub ), a collection of MIT-licensed Helm charts.
The chart supports:
- **Standalone and queue mode** (with Redis for horizontal scaling)
- **SQLite, PostgreSQL, and MySQL** as database backends (auto-detection or explicit configuration)
- **PostgreSQL and MySQL subcharts** for self-contained deployments
- **Built-in S3-compatible backup** — CronJob that runs the appropriate dump tool (sqlite3, pg_dump, mysqldump) and uploads to any S3 endpoint (AWS S3, MinIO, R2, B2)
- **Ingress, probes, security contexts, and resource limits** with sensible defaults
- CI validated with helm lint, helm template, helm unittest, and kubeconform
Install:
```bash
helm repo add helmforge https://repo.helmforge.dev
helm install n8n helmforge/n8n
# Or via OCI
helm install n8n oci://ghcr.io/helmforgedev/helm/n8n
```
- Chart source: charts/charts/n8n at main · helmforgedev/charts · GitHub
- ArtifactHub: n8n 1.3.0 · helmforge/helmforge
Would you be open to mentioning this in the n8n docs or community resources as a community-maintained Helm deployment option? Happy to answer any questions about the implementation.