# Community Charts

> Discover community-driven Helm charts for open-source tools lacking official support. Deploy apps effortlessly on Kubernetes.

- [Community Charts](/index.md)

## blog

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

### actualbudget-chart-version-1.7.0-released

Announcing the release of actualbudget chart version 1.7.0 Helm chart, featuring app version 25.6.1, with new features and community-driven improvements.

- [actualbudget chart version 1.7.0 released](/blog/actualbudget-chart-version-1.7.0-released.md): Announcing the release of actualbudget chart version 1.7.0 Helm chart, featuring app version 25.6.1, with new features and community-driven improvements.

### actualbudget-chart-version-1.7.1-released

Discover what's new in actualbudget Helm chart version 1.7.1 with app version 25.7.0, including key improvements and updates from the open source community.

- [actualbudget chart version 1.7.1 update now available](/blog/actualbudget-chart-version-1.7.1-released.md): Discover what's new in actualbudget Helm chart version 1.7.1 with app version 25.7.0, including key improvements and updates from the open source community.

### actualbudget-chart-version-1.7.2-released

Discover what's new in actualbudget Helm chart v1.7.2 with app version 25.7.1, featuring updates and improvements from the open-source community.

- [actualbudget chart version 1.7.2 released](/blog/actualbudget-chart-version-1.7.2-released.md): Discover what's new in actualbudget Helm chart v1.7.2 with app version 25.7.1, featuring updates and improvements from the open-source community.

### actualbudget-chart-version-1.8.0-released

Discover what's new in actualbudget chart v1.8.0 for Helm, now supporting app version 25.7.1, with enhancements powered by community feedback.

- [actualbudget chart version 1.8.0 released](/blog/actualbudget-chart-version-1.8.0-released.md): Discover what's new in actualbudget chart v1.8.0 for Helm, now supporting app version 25.7.1, with enhancements powered by community feedback.

### actualbudget-chart-version-1.8.1-released

Discover actualbudget Helm chart 1.8.1 with app version 25.8.0—improved deployment experience and community-driven updates.

- [actualbudget chart version 1.8.1 released](/blog/actualbudget-chart-version-1.8.1-released.md): Discover actualbudget Helm chart 1.8.1 with app version 25.8.0—improved deployment experience and community-driven updates.

### actualbudget-chart-version-1.8.2-released

Discover the latest actualbudget Helm chart 1.8.2 with app version 25.9.0, featuring new updates, improved stability, and community contributions.

- [actualbudget chart version 1.8.2 released](/blog/actualbudget-chart-version-1.8.2-released.md): Discover the latest actualbudget Helm chart 1.8.2 with app version 25.9.0, featuring new updates, improved stability, and community contributions.

### actualbudget-chart-version-1.8.3-released

Discover what's new in actualbudget chart version 1.8.3, featuring app version 25.10.0, with community-driven updates and enhanced Kubernetes support.

- [actualbudget chart version 1.8.3 released](/blog/actualbudget-chart-version-1.8.3-released.md): Discover what's new in actualbudget chart version 1.8.3, featuring app version 25.10.0, with community-driven updates and enhanced Kubernetes support.

### actualbudget-chart-version-1.8.4-released

The actualbudget chart version 1.8.4 is now available, featuring app version 25.11.0 with improved functionality and better Kubernetes support.

- [actualbudget chart 1.8.4 now available](/blog/actualbudget-chart-version-1.8.4-released.md): The actualbudget chart version 1.8.4 is now available, featuring app version 25.11.0 with improved functionality and better Kubernetes support.

### actualbudget-chart-version-1.8.5-released

Discover what's new in actualbudget Helm chart 1.8.5 featuring app version 25.12.0, with enhancements and community-driven updates.

- [actualbudget chart version 1.8.5 released](/blog/actualbudget-chart-version-1.8.5-released.md): Discover what's new in actualbudget Helm chart 1.8.5 featuring app version 25.12.0, with enhancements and community-driven updates.

### actualbudget-chart-version-1.8.8-released

Discover the new actualbudget chart version 1.8.8 Helm chart, featuring app version 26.5.2, with exciting new features and community enhancements.

- [Actualbudget Chart Version 1.8.8 Released](/blog/actualbudget-chart-version-1.8.8-released.md): Discover the new actualbudget chart version 1.8.8 Helm chart, featuring app version 26.5.2, with exciting new features and community enhancements.

### actualbudget-chart-version-1.8.9-released

Announcing the release of actualbudget chart version 1.8.9 Helm chart, featuring app version 26.6.0, with new features and community-driven improvements.

- [actualbudget chart version 1.8.9 released](/blog/actualbudget-chart-version-1.8.9-released.md): Announcing the release of actualbudget chart version 1.8.9 Helm chart, featuring app version 26.6.0, with new features and community-driven improvements.

### actualbudget-chart-version-1.9.0-released

Discover the exciting features of the actualbudget chart version 1.9.0 Helm chart with app version 26.6.0, designed for smooth and efficient deployments.

- [actualbudget chart version 1.9.0 released](/blog/actualbudget-chart-version-1.9.0-released.md): Discover the exciting features of the actualbudget chart version 1.9.0 Helm chart with app version 26.6.0, designed for smooth and efficient deployments.

### archive

Archive

- [Archive](/blog/archive.md): Archive

### authors

Meet the authors behind the Community Charts blog. Discover contributors, their profiles, and their latest posts.

- [Authors](/blog/authors.md): Meet the authors behind the Community Charts blog. Discover contributors, their profiles, and their latest posts.

#### burakince

Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.

- [Burak Ince](/blog/authors/burakince.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/10.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/11.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/12.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/13.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/14.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/15.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/16.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/2.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/3.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/4.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/5.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/6.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/7.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/8.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.
- [Burak Ince](/blog/authors/burakince/page/9.md): Read blog posts by Burak Ince on Community Charts. Explore their contributions and expertise.

### cloudflared-chart-version-2.0.8-released

Discover what's new in cloudflared Helm chart version 2.0.8 with updated image support, enhanced deployment flexibility, and community-driven improvements.

- [cloudflared chart version 2.0.8 now available](/blog/cloudflared-chart-version-2.0.8-released.md): Discover what's new in cloudflared Helm chart version 2.0.8 with updated image support, enhanced deployment flexibility, and community-driven improvements.

### cloudflared-chart-version-2.0.9-released

Discover cloudflared Helm chart 2.0.9 with app version 2025.7.0, featuring enhancements to ingress schema and simplified Kubernetes deployment.

- [cloudflared chart version 2.0.9 released](/blog/cloudflared-chart-version-2.0.9-released.md): Discover cloudflared Helm chart 2.0.9 with app version 2025.7.0, featuring enhancements to ingress schema and simplified Kubernetes deployment.

### cloudflared-chart-version-2.1.0-released

Discover cloudflared Helm chart version 2.1.0 featuring app version 2025.7.0, now with enhanced secret support and community-driven improvements.

- [cloudflared chart version 2.1.0 released](/blog/cloudflared-chart-version-2.1.0-released.md): Discover cloudflared Helm chart version 2.1.0 featuring app version 2025.7.0, now with enhanced secret support and community-driven improvements.

### cloudflared-chart-version-2.1.1-released

Announcing Helm chart version 2.1.1 for cloudflared, featuring app version 2025.8.0 with enhanced functionality and community contributions.

- [cloudflared chart version 2.1.1 released](/blog/cloudflared-chart-version-2.1.1-released.md): Announcing Helm chart version 2.1.1 for cloudflared, featuring app version 2025.8.0 with enhanced functionality and community contributions.

### cloudflared-chart-version-2.1.2-released

Announcing cloudflared Helm chart version 2.1.2 with app version 2025.8.1, delivering updated features and community-driven enhancements.

- [cloudflared chart version 2.1.2 released](/blog/cloudflared-chart-version-2.1.2-released.md): Announcing cloudflared Helm chart version 2.1.2 with app version 2025.8.1, delivering updated features and community-driven enhancements.

### cloudflared-chart-version-2.1.3-released

Announcing the cloudflared chart version 2.1.3 for Helm, featuring app version 2025.9.0 and community-powered improvements.

- [cloudflared chart version 2.1.3 released](/blog/cloudflared-chart-version-2.1.3-released.md): Announcing the cloudflared chart version 2.1.3 for Helm, featuring app version 2025.9.0 and community-powered improvements.

### cloudflared-chart-version-2.2.0-released

Discover what's new in cloudflared Helm chart version 2.2.0 with app version 2025.9.0, including security updates and streamlined Kubernetes deployment.

- [cloudflared chart version 2.2.0 released](/blog/cloudflared-chart-version-2.2.0-released.md): Discover what's new in cloudflared Helm chart version 2.2.0 with app version 2025.9.0, including security updates and streamlined Kubernetes deployment.

### cloudflared-chart-version-2.2.1-released

Announcing the Helm chart release of cloudflared version 2.2.1 with app version 2025.9.1, featuring enhancements and community contributions.

- [cloudflared chart version 2.2.1 released](/blog/cloudflared-chart-version-2.2.1-released.md): Announcing the Helm chart release of cloudflared version 2.2.1 with app version 2025.9.1, featuring enhancements and community contributions.

### cloudflared-chart-version-2.2.10-released

Announcing the release of cloudflared chart version 2.2.10 Helm chart, featuring app version 2026.6.1, with new features and community-driven improvements.

- [Cloudflared Chart Version 2.2.10 Released](/blog/cloudflared-chart-version-2.2.10-released.md): Announcing the release of cloudflared chart version 2.2.10 Helm chart, featuring app version 2026.6.1, with new features and community-driven improvements.

### cloudflared-chart-version-2.2.2-released

Announcing the cloudflared Helm chart 2.2.2 with app version 2025.10.0, featuring community-backed enhancements for Kubernetes deployments.

- [cloudflared chart version 2.2.2 released](/blog/cloudflared-chart-version-2.2.2-released.md): Announcing the cloudflared Helm chart 2.2.2 with app version 2025.10.0, featuring community-backed enhancements for Kubernetes deployments.

### cloudflared-chart-version-2.2.3-released

Discover cloudflared Helm chart version 2.2.3, now supporting app version 2025.10.1, with streamlined Kubernetes deployment and community-led updates.

- [cloudflared chart version 2.2.3 released](/blog/cloudflared-chart-version-2.2.3-released.md): Discover cloudflared Helm chart version 2.2.3, now supporting app version 2025.10.1, with streamlined Kubernetes deployment and community-led updates.

### cloudflared-chart-version-2.2.4-released

Announcing cloudflared Helm chart version 2.2.4 with app version 2025.11.1, introducing enhancements and community-led updates.

- [cloudflared chart version 2.2.4 released](/blog/cloudflared-chart-version-2.2.4-released.md): Announcing cloudflared Helm chart version 2.2.4 with app version 2025.11.1, introducing enhancements and community-led updates.

### cloudflared-chart-version-2.2.8-released

Discover the latest cloudflared chart version 2.2.8 Helm chart, featuring app version 2026.5.2, packed with new features and community enhancements.

- [Cloudflared Chart Version 2.2.8 Released](/blog/cloudflared-chart-version-2.2.8-released.md): Discover the latest cloudflared chart version 2.2.8 Helm chart, featuring app version 2026.5.2, packed with new features and community enhancements.

### cloudflared-chart-version-2.2.9-released

Announcing the release of Cloudflared chart version 2.2.9 Helm chart, featuring app version 2026.6.0, with new features and community-driven improvements.

- [Cloudflared Chart Version 2.2.9 Released](/blog/cloudflared-chart-version-2.2.9-released.md): Announcing the release of Cloudflared chart version 2.2.9 Helm chart, featuring app version 2026.6.0, with new features and community-driven improvements.

### drone-chart-version-0.1.5-released

Discover the new drone chart version 0.1.5 Helm chart, featuring app version 2.28.2, packed with enhancements and community-driven improvements.

- [Exciting Release of Drone Chart Version 0.1.5](/blog/drone-chart-version-0.1.5-released.md): Discover the new drone chart version 0.1.5 Helm chart, featuring app version 2.28.2, packed with enhancements and community-driven improvements.

### mlflow-chart-version-1.10.0-released

Discover the enhanced mlflow chart version 1.10.0 Helm chart, featuring app version 3.14.0, with exciting new features and community-driven improvements.

- [mlflow chart version 1.10.0 released](/blog/mlflow-chart-version-1.10.0-released.md): Discover the enhanced mlflow chart version 1.10.0 Helm chart, featuring app version 3.14.0, with exciting new features and community-driven improvements.

### mlflow-chart-version-1.11.0-released

Announcing the release of mlflow chart version 1.11.0 Helm chart, featuring app version 3.14.0, with new features and community-driven improvements.

- [mlflow chart version 1.11.0 released](/blog/mlflow-chart-version-1.11.0-released.md): Announcing the release of mlflow chart version 1.11.0 Helm chart, featuring app version 3.14.0, with new features and community-driven improvements.

### mlflow-chart-version-1.11.1-released

Explore the new features in mlflow chart version 1.11.1 Helm chart, featuring app version 3.14.0, designed to enhance your Kubernetes deployment experience.

- [mlflow chart version 1.11.1 released](/blog/mlflow-chart-version-1.11.1-released.md): Explore the new features in mlflow chart version 1.11.1 Helm chart, featuring app version 3.14.0, designed to enhance your Kubernetes deployment experience.

### mlflow-chart-version-1.11.2-released

Discover the latest mlflow chart version 1.11.2 Helm chart, featuring app version 3.14.0, with exciting updates and community enhancements.

- [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md): Discover the latest mlflow chart version 1.11.2 Helm chart, featuring app version 3.14.0, with exciting updates and community enhancements.

### mlflow-chart-version-1.2.0-released

Announcing the release of mlflow chart version 1.2.0 Helm chart, featuring app version 3.1.0, with new features and community-driven improvements.

- [mlflow chart version 1.2.0 released](/blog/mlflow-chart-version-1.2.0-released.md): Announcing the release of mlflow chart version 1.2.0 Helm chart, featuring app version 3.1.0, with new features and community-driven improvements.

### mlflow-chart-version-1.3.0-released

Announcing the release of mlflow chart version 1.3.0 Helm chart, featuring app version 3.1.1, with new features and community-driven improvements.

- [mlflow chart version 1.3.0 released](/blog/mlflow-chart-version-1.3.0-released.md): Announcing the release of mlflow chart version 1.3.0 Helm chart, featuring app version 3.1.1, with new features and community-driven improvements.

### mlflow-chart-version-1.3.1-released

We're excited to announce mlflow chart version 1.3.1 with app version 3.1.3, packed with Helm dependency upgrades and community-powered improvements.

- [mlflow chart version 1.3.1 released](/blog/mlflow-chart-version-1.3.1-released.md): We're excited to announce mlflow chart version 1.3.1 with app version 3.1.3, packed with Helm dependency upgrades and community-powered improvements.

### mlflow-chart-version-1.3.2-released

Introducing mlflow Helm chart version 1.3.2 with app version 3.1.4, featuring improved usability, community updates, and seamless Kubernetes deployment.

- [mlflow chart version 1.3.2 released](/blog/mlflow-chart-version-1.3.2-released.md): Introducing mlflow Helm chart version 1.3.2 with app version 3.1.4, featuring improved usability, community updates, and seamless Kubernetes deployment.

### mlflow-chart-version-1.4.0-released

Discover what’s new in mlflow chart version 1.4.0 with app version 3.1.4, including enhanced AWS secret support and community-driven updates.

- [mlflow chart version 1.4.0 released](/blog/mlflow-chart-version-1.4.0-released.md): Discover what’s new in mlflow chart version 1.4.0 with app version 3.1.4, including enhanced AWS secret support and community-driven updates.

### mlflow-chart-version-1.4.1-released

Discover what’s new in the mlflow Helm chart version 1.4.1, featuring app version 3.2.0, with enhancements and contributions from the open-source community.

- [mlflow chart version 1.4.1 released](/blog/mlflow-chart-version-1.4.1-released.md): Discover what’s new in the mlflow Helm chart version 1.4.1, featuring app version 3.2.0, with enhancements and contributions from the open-source community.

### mlflow-chart-version-1.5.0-released

Introducing mlflow chart version 1.5.0 with app version 3.2.0, featuring new secret support and telemetry controls for streamlined Kubernetes deployment.

- [mlflow chart version 1.5.0 released](/blog/mlflow-chart-version-1.5.0-released.md): Introducing mlflow chart version 1.5.0 with app version 3.2.0, featuring new secret support and telemetry controls for streamlined Kubernetes deployment.

### mlflow-chart-version-1.6.0-released

Discover what’s new in mlflow Helm chart 1.6.0, now supporting app version 3.2.0, with performance enhancements and community-driven updates for Kubernetes deployments.

- [mlflow chart version 1.6.0 released](/blog/mlflow-chart-version-1.6.0-released.md): Discover what’s new in mlflow Helm chart 1.6.0, now supporting app version 3.2.0, with performance enhancements and community-driven updates for Kubernetes deployments.

### mlflow-chart-version-1.6.1-released

Discover mlflow Helm chart version 1.6.1, powered by app version 3.3.1, featuring enhanced dependencies and community-driven improvements.

- [mlflow chart version 1.6.1 released](/blog/mlflow-chart-version-1.6.1-released.md): Discover mlflow Helm chart version 1.6.1, powered by app version 3.3.1, featuring enhanced dependencies and community-driven improvements.

### mlflow-chart-version-1.6.2-released

The latest mlflow Helm chart version 1.6.2 is here, featuring app version 3.3.2, enhanced Kubernetes support, and community-led improvements.

- [mlflow chart version 1.6.2 released](/blog/mlflow-chart-version-1.6.2-released.md): The latest mlflow Helm chart version 1.6.2 is here, featuring app version 3.3.2, enhanced Kubernetes support, and community-led improvements.

### mlflow-chart-version-1.6.3-released

Discover mlflow Helm chart version 1.6.3 with app version 3.4.0, featuring usability improvements and stronger Kubernetes integrations.

- [mlflow chart version 1.6.3 released](/blog/mlflow-chart-version-1.6.3-released.md): Discover mlflow Helm chart version 1.6.3 with app version 3.4.0, featuring usability improvements and stronger Kubernetes integrations.

### mlflow-chart-version-1.7.0-released

Announcing the release of mlflow chart version 1.7.0 Helm chart, featuring app version 3.4.0, with new features and community-driven improvements.

- [mlflow chart version 1.7.0 released](/blog/mlflow-chart-version-1.7.0-released.md): Announcing the release of mlflow chart version 1.7.0 Helm chart, featuring app version 3.4.0, with new features and community-driven improvements.

### mlflow-chart-version-1.7.1-released

Discover the new mlflow Helm chart version 1.7.1 with app version 3.4.0, featuring flexible init container support and community-powered enhancements.

- [mlflow chart version 1.7.1 released](/blog/mlflow-chart-version-1.7.1-released.md): Discover the new mlflow Helm chart version 1.7.1 with app version 3.4.0, featuring flexible init container support and community-powered enhancements.

### mlflow-chart-version-1.7.2-released

Announcing mlflow Helm chart version 1.7.2 with app version 3.5.0, featuring dependency updates and community-driven improvements.

- [mlflow chart version 1.7.2 released](/blog/mlflow-chart-version-1.7.2-released.md): Announcing mlflow Helm chart version 1.7.2 with app version 3.5.0, featuring dependency updates and community-driven improvements.

### mlflow-chart-version-1.7.3-released

Introducing mlflow Helm chart 1.7.3 with app version 3.5.1, featuring updated dependencies and community-driven enhancements for Kubernetes deployments.

- [mlflow chart version 1.7.3 released](/blog/mlflow-chart-version-1.7.3-released.md): Introducing mlflow Helm chart 1.7.3 with app version 3.5.1, featuring updated dependencies and community-driven enhancements for Kubernetes deployments.

### mlflow-chart-version-1.7.4-released

Announcing the new mlflow Helm chart version 1.7.4 with app version 3.6.0, delivering improved support for Kubernetes deployments.

- [mlflow chart version 1.7.4 released](/blog/mlflow-chart-version-1.7.4-released.md): Announcing the new mlflow Helm chart version 1.7.4 with app version 3.6.0, delivering improved support for Kubernetes deployments.

### mlflow-chart-version-1.8.0-released

Introducing mlflow Helm chart version 1.8.0 with app version 3.6.0, offering improved init container resource support and community-driven enhancements.

- [mlflow chart version 1.8.0 released](/blog/mlflow-chart-version-1.8.0-released.md): Introducing mlflow Helm chart version 1.8.0 with app version 3.6.0, offering improved init container resource support and community-driven enhancements.

### mlflow-chart-version-1.8.1-released

Announcing the mlflow Helm chart 1.8.1 release with app version 3.7.0, bringing enhancements and community-driven updates for Kubernetes deployments.

- [mlflow chart version 1.8.1 released](/blog/mlflow-chart-version-1.8.1-released.md): Announcing the mlflow Helm chart 1.8.1 release with app version 3.7.0, bringing enhancements and community-driven updates for Kubernetes deployments.

### mlflow-chart-version-1.8.2-released

Discover the new features and community-driven improvements in mlflow chart version 1.8.2 Helm chart, featuring app version 3.12.0.

- [mlflow chart version 1.8.2 released](/blog/mlflow-chart-version-1.8.2-released.md): Discover the new features and community-driven improvements in mlflow chart version 1.8.2 Helm chart, featuring app version 3.12.0.

### mlflow-chart-version-1.8.3-released

Discover the new features and enhancements in mlflow chart version 1.8.3, featuring app version 3.12.0, aimed at simplifying Kubernetes deployment.

- [Mlflow Chart Version 1.8.3 Released](/blog/mlflow-chart-version-1.8.3-released.md): Discover the new features and enhancements in mlflow chart version 1.8.3, featuring app version 3.12.0, aimed at simplifying Kubernetes deployment.

### mlflow-chart-version-1.8.4-released

Discover the new features and enhancements in mlflow chart version 1.8.4 Helm chart, featuring app version 3.13.0, and community-driven improvements.

- [mlflow chart version 1.8.4 launched](/blog/mlflow-chart-version-1.8.4-released.md): Discover the new features and enhancements in mlflow chart version 1.8.4 Helm chart, featuring app version 3.13.0, and community-driven improvements.

### mlflow-chart-version-1.8.5-released

Discover the exciting release of MLflow chart version 1.8.5 Helm chart, featuring app version 3.13.0, with new features and community-driven enhancements.

- [MLflow Chart Version 1.8.5 Released](/blog/mlflow-chart-version-1.8.5-released.md): Discover the exciting release of MLflow chart version 1.8.5 Helm chart, featuring app version 3.13.0, with new features and community-driven enhancements.

### mlflow-chart-version-1.8.6-released

Discover the new features in mlflow chart version 1.8.6 Helm chart, featuring app version 3.14.0, with exciting updates and community-driven improvements.

- [mlflow chart version 1.8.6 released](/blog/mlflow-chart-version-1.8.6-released.md): Discover the new features in mlflow chart version 1.8.6 Helm chart, featuring app version 3.14.0, with exciting updates and community-driven improvements.

### mlflow-chart-version-1.9.0-released

Announcing the release of mlflow chart version 1.9.0 Helm chart, featuring app version 3.14.0, with new features and community-driven improvements.

- [mlflow Helm Chart Version 1.9.0 Released](/blog/mlflow-chart-version-1.9.0-released.md): Announcing the release of mlflow chart version 1.9.0 Helm chart, featuring app version 3.14.0, with new features and community-driven improvements.

### n8n-chart-version-1.10.0-released

Discover the new features and community contributions in n8n chart version 1.10.0 for Helm, powered by app version 1.99.1.

- [n8n chart version 1.10.0 now available](/blog/n8n-chart-version-1.10.0-released.md): Discover the new features and community contributions in n8n chart version 1.10.0 for Helm, powered by app version 1.99.1.

### n8n-chart-version-1.11.0-released

Discover what's new in the n8n Helm chart version 1.11.0 with app version 1.99.1, featuring improvements and updated deployment configurations.

- [n8n chart version 1.11.0 released](/blog/n8n-chart-version-1.11.0-released.md): Discover what's new in the n8n Helm chart version 1.11.0 with app version 1.99.1, featuring improvements and updated deployment configurations.

### n8n-chart-version-1.12.0-released

Discover what's new in the n8n Helm chart version 1.12.0 with app version 1.99.1, featuring fresh capabilities and community-driven enhancements.

- [n8n chart version 1.12.0 released](/blog/n8n-chart-version-1.12.0-released.md): Discover what's new in the n8n Helm chart version 1.12.0 with app version 1.99.1, featuring fresh capabilities and community-driven enhancements.

### n8n-chart-version-1.12.1-released

Announcing the n8n chart 1.12.1 Helm release featuring app version 1.100.1, with notable upgrades and community-led enhancements.

- [n8n chart version 1.12.1 now available](/blog/n8n-chart-version-1.12.1-released.md): Announcing the n8n chart 1.12.1 Helm release featuring app version 1.100.1, with notable upgrades and community-led enhancements.

### n8n-chart-version-1.12.2-released

Discover what's new in the n8n Helm chart version 1.12.2 release, now featuring app version 1.100.1 with enhanced stability and community-driven fixes.

- [n8n chart version 1.12.2 released](/blog/n8n-chart-version-1.12.2-released.md): Discover what's new in the n8n Helm chart version 1.12.2 release, now featuring app version 1.100.1 with enhanced stability and community-driven fixes.

### n8n-chart-version-1.12.3-released

Discover what’s new in the latest n8n Helm chart version 1.12.3, featuring app version 1.100.1 and valuable community-driven enhancements.

- [n8n Helm chart 1.12.3 now available](/blog/n8n-chart-version-1.12.3-released.md): Discover what’s new in the latest n8n Helm chart version 1.12.3, featuring app version 1.100.1 and valuable community-driven enhancements.

### n8n-chart-version-1.13.0-released

Discover what's new in n8n Helm chart version 1.13.0, with community improvements and Kubernetes deployment enhancements.

- [n8n chart 1.13.0 update is here](/blog/n8n-chart-version-1.13.0-released.md): Discover what's new in n8n Helm chart version 1.13.0, with community improvements and Kubernetes deployment enhancements.

### n8n-chart-version-1.13.10-released

Introducing Helm chart version 1.13.10 for n8n with app version 1.105.4. Explore new updates and enhancements from the open-source community.

- [n8n chart version 1.13.10 available now](/blog/n8n-chart-version-1.13.10-released.md): Introducing Helm chart version 1.13.10 for n8n with app version 1.105.4. Explore new updates and enhancements from the open-source community.

### n8n-chart-version-1.13.2-released

Discover what's new in n8n Helm chart version 1.13.2, featuring updated dependencies and enhancements designed for smoother Kubernetes deployments.

- [n8n chart version 1.13.2 released](/blog/n8n-chart-version-1.13.2-released.md): Discover what's new in n8n Helm chart version 1.13.2, featuring updated dependencies and enhancements designed for smoother Kubernetes deployments.

### n8n-chart-version-1.13.3-released

Discover what’s new in n8n Helm chart 1.13.3 with app version 1.102.3—community-driven enhancements and updated dependencies make deployments smoother than ever.

- [n8n chart version 1.13.3 released](/blog/n8n-chart-version-1.13.3-released.md): Discover what’s new in n8n Helm chart 1.13.3 with app version 1.102.3—community-driven enhancements and updated dependencies make deployments smoother than ever.

### n8n-chart-version-1.13.4-released

Discover what's new in n8n Helm chart version 1.13.4 with app version 1.102.4—updated images, improved Redis support, and powerful Kubernetes deployment enhancements.

- [n8n chart version 1.13.4 released](/blog/n8n-chart-version-1.13.4-released.md): Discover what's new in n8n Helm chart version 1.13.4 with app version 1.102.4—updated images, improved Redis support, and powerful Kubernetes deployment enhancements.

### n8n-chart-version-1.13.5-released

Discover what's new in n8n Helm chart version 1.13.5, including app version 1.103.2, with improved Redis and PostgreSQL dependencies for better Kubernetes deployments.

- [n8n chart version 1.13.5 released](/blog/n8n-chart-version-1.13.5-released.md): Discover what's new in n8n Helm chart version 1.13.5, including app version 1.103.2, with improved Redis and PostgreSQL dependencies for better Kubernetes deployments.

### n8n-chart-version-1.13.6-released

The latest n8n Helm chart version 1.13.6 is out, featuring app version 1.104.1 with updates for Kubernetes deployment and community-driven enhancements.

- [n8n Helm chart 1.13.6 now available](/blog/n8n-chart-version-1.13.6-released.md): The latest n8n Helm chart version 1.13.6 is out, featuring app version 1.104.1 with updates for Kubernetes deployment and community-driven enhancements.

### n8n-chart-version-1.13.7-released

Discover what's new in Helm chart 1.13.7 for n8n, now with app version 1.104.2 and community-powered enhancements for Kubernetes deployments.

- [n8n chart version 1.13.7 now available](/blog/n8n-chart-version-1.13.7-released.md): Discover what's new in Helm chart 1.13.7 for n8n, now with app version 1.104.2 and community-powered enhancements for Kubernetes deployments.

### n8n-chart-version-1.13.8-released

Explore the new n8n Helm chart version 1.13.8 featuring app version 1.105.2, with updated Redis and community-led improvements for Kubernetes deployments.

- [n8n chart version 1.13.8 released](/blog/n8n-chart-version-1.13.8-released.md): Explore the new n8n Helm chart version 1.13.8 featuring app version 1.105.2, with updated Redis and community-led improvements for Kubernetes deployments.

### n8n-chart-version-1.13.9-released

Announcing the release of n8n chart version 1.13.9 with app version 1.105.3, packed with new features and community enhancements for Kubernetes deployment.

- [n8n chart version 1.13.9 released](/blog/n8n-chart-version-1.13.9-released.md): Announcing the release of n8n chart version 1.13.9 with app version 1.105.3, packed with new features and community enhancements for Kubernetes deployment.

### n8n-chart-version-1.14.0-released

Announcing n8n Helm chart version 1.14.0 with app version 1.105.4, featuring improved persistence handling and community enhancements.

- [n8n chart version 1.14.0 released](/blog/n8n-chart-version-1.14.0-released.md): Announcing n8n Helm chart version 1.14.0 with app version 1.105.4, featuring improved persistence handling and community enhancements.

### n8n-chart-version-1.14.1-released

Announcing the release of n8n Helm chart 1.14.1 with app version 1.106.3, featuring enhanced features and improved dependency updates for Kubernetes users.

- [n8n chart version 1.14.1 released](/blog/n8n-chart-version-1.14.1-released.md): Announcing the release of n8n Helm chart 1.14.1 with app version 1.106.3, featuring enhanced features and improved dependency updates for Kubernetes users.

### n8n-chart-version-1.14.2-released

Discover what's new in the n8n Helm chart version 1.14.2 with app version 1.107.3, including updated dependencies and enhanced deployment flexibility.

- [n8n chart version 1.14.2 now available](/blog/n8n-chart-version-1.14.2-released.md): Discover what's new in the n8n Helm chart version 1.14.2 with app version 1.107.3, including updated dependencies and enhanced deployment flexibility.

### n8n-chart-version-1.14.3-released

Announcing the n8n Helm chart version 1.14.3 with app version 1.107.4, introducing updates and community-led enhancements for Kubernetes deployments.

- [n8n chart version 1.14.3 released](/blog/n8n-chart-version-1.14.3-released.md): Announcing the n8n Helm chart version 1.14.3 with app version 1.107.4, introducing updates and community-led enhancements for Kubernetes deployments.

### n8n-chart-version-1.15.0-released

Announcing the release of n8n chart version 1.15.0 Helm chart featuring app version 1.107.4, with new features and community-powered improvements.

- [n8n chart version 1.15.0 released](/blog/n8n-chart-version-1.15.0-released.md): Announcing the release of n8n chart version 1.15.0 Helm chart featuring app version 1.107.4, with new features and community-powered improvements.

### n8n-chart-version-1.15.1-released

Announcing n8n Helm chart 1.15.1 with app version 1.107.4, delivering improved Redis support and community-driven enhancements for Kubernetes deployments.

- [n8n chart version 1.15.1 released](/blog/n8n-chart-version-1.15.1-released.md): Announcing n8n Helm chart 1.15.1 with app version 1.107.4, delivering improved Redis support and community-driven enhancements for Kubernetes deployments.

### n8n-chart-version-1.15.10-released

n8n Helm chart version 1.15.10 is live with app version 1.112.5, bringing new features, improvements, and a better Kubernetes experience.

- [n8n chart version 1.15.10 released](/blog/n8n-chart-version-1.15.10-released.md): n8n Helm chart version 1.15.10 is live with app version 1.112.5, bringing new features, improvements, and a better Kubernetes experience.

### n8n-chart-version-1.15.11-released

Discover what's new in n8n Helm chart 1.15.11 with app version 1.112.6, featuring updates for smoother Kubernetes deployments and community-driven improvements.

- [n8n chart version 1.15.11 released](/blog/n8n-chart-version-1.15.11-released.md): Discover what's new in n8n Helm chart 1.15.11 with app version 1.112.6, featuring updates for smoother Kubernetes deployments and community-driven improvements.

### n8n-chart-version-1.15.12-released

Announcing the release of n8n Helm chart v1.15.12 with app version 1.113.3, bringing improvements and community-driven enhancements.

- [n8n chart version 1.15.12 released](/blog/n8n-chart-version-1.15.12-released.md): Announcing the release of n8n Helm chart v1.15.12 with app version 1.113.3, bringing improvements and community-driven enhancements.

### n8n-chart-version-1.15.13-released

Announcing the n8n chart version 1.15.13 with app version 1.114.3, including updates to dependencies and community enhancements.

- [n8n chart version 1.15.13 released](/blog/n8n-chart-version-1.15.13-released.md): Announcing the n8n chart version 1.15.13 with app version 1.114.3, including updates to dependencies and community enhancements.

### n8n-chart-version-1.15.14-released

Announcing the release of n8n chart version 1.15.14 Helm chart, featuring app version 1.114.4, with new features and community-driven improvements.

- [n8n chart version 1.15.14 released](/blog/n8n-chart-version-1.15.14-released.md): Announcing the release of n8n chart version 1.15.14 Helm chart, featuring app version 1.114.4, with new features and community-driven improvements.

### n8n-chart-version-1.15.15-released

Discover what's new in the Helm chart release of n8n version 1.15.15, featuring app version 1.115.2, updated dependencies, and community-powered enhancements.

- [n8n chart version 1.15.15 released](/blog/n8n-chart-version-1.15.15-released.md): Discover what's new in the Helm chart release of n8n version 1.15.15, featuring app version 1.115.2, updated dependencies, and community-powered enhancements.

### n8n-chart-version-1.15.16-released

n8n Helm chart version 1.15.16 is now live with app version 1.115.3, introducing updates and enhancements powered by community contributions.

- [n8n chart version 1.15.16 released](/blog/n8n-chart-version-1.15.16-released.md): n8n Helm chart version 1.15.16 is now live with app version 1.115.3, introducing updates and enhancements powered by community contributions.

### n8n-chart-version-1.15.17-released

Discover the n8n Helm chart version 1.15.17 with app version 1.116.2, offering enhanced performance, Redis and PostgreSQL updates, and seamless Kubernetes deployment.

- [n8n chart version 1.15.17 released](/blog/n8n-chart-version-1.15.17-released.md): Discover the n8n Helm chart version 1.15.17 with app version 1.116.2, offering enhanced performance, Redis and PostgreSQL updates, and seamless Kubernetes deployment.

### n8n-chart-version-1.15.18-released

Discover what's new in n8n Helm chart version 1.15.18 with app version 1.117.2, including Redis and PostgreSQL updates and improved Kubernetes deployment.

- [n8n chart version 1.15.18 released](/blog/n8n-chart-version-1.15.18-released.md): Discover what's new in n8n Helm chart version 1.15.18 with app version 1.117.2, including Redis and PostgreSQL updates and improved Kubernetes deployment.

### n8n-chart-version-1.15.19-released

Discover what's new in n8n Helm chart version 1.15.19 featuring app version 1.117.3, with performance updates and community enhancements.

- [n8n chart version 1.15.19 released](/blog/n8n-chart-version-1.15.19-released.md): Discover what's new in n8n Helm chart version 1.15.19 featuring app version 1.117.3, with performance updates and community enhancements.

### n8n-chart-version-1.15.2-released

Discover what's new in n8n Helm chart 1.15.2 featuring app version 1.108.2, including updated dependencies and community-backed improvements.

- [n8n Helm chart 1.15.2 now available](/blog/n8n-chart-version-1.15.2-released.md): Discover what's new in n8n Helm chart 1.15.2 featuring app version 1.108.2, including updated dependencies and community-backed improvements.

### n8n-chart-version-1.15.20-released

Announcing n8n chart version 1.15.20 Helm release with app version 1.118.2, featuring key upgrades and improved Kubernetes deployment.

- [n8n chart version 1.15.20 released](/blog/n8n-chart-version-1.15.20-released.md): Announcing n8n chart version 1.15.20 Helm release with app version 1.118.2, featuring key upgrades and improved Kubernetes deployment.

### n8n-chart-version-1.15.3-released

Discover the latest n8n Helm chart release 1.15.3 featuring app version 1.109.1, with updated images, improved dependencies, and community contributions.

- [n8n Helm chart 1.15.3 now available](/blog/n8n-chart-version-1.15.3-released.md): Discover the latest n8n Helm chart release 1.15.3 featuring app version 1.109.1, with updated images, improved dependencies, and community contributions.

### n8n-chart-version-1.15.4-released

Announcing the latest n8n Helm chart release 1.15.4 with app version 1.109.2, featuring new upgrades, improvements, and Kubernetes-friendly enhancements.

- [n8n chart version 1.15.4 released](/blog/n8n-chart-version-1.15.4-released.md): Announcing the latest n8n Helm chart release 1.15.4 with app version 1.109.2, featuring new upgrades, improvements, and Kubernetes-friendly enhancements.

### n8n-chart-version-1.15.5-released

Announcing the release of n8n chart version 1.15.5 Helm chart, featuring app version 1.110.1, with new features and community-driven improvements.

- [n8n chart version 1.15.5 released](/blog/n8n-chart-version-1.15.5-released.md): Announcing the release of n8n chart version 1.15.5 Helm chart, featuring app version 1.110.1, with new features and community-driven improvements.

### n8n-chart-version-1.15.6-released

Discover what's new in the n8n Helm chart version 1.15.6, featuring app version 1.111.0, with improvements driven by the open-source community.

- [n8n chart version 1.15.6 released](/blog/n8n-chart-version-1.15.6-released.md): Discover what's new in the n8n Helm chart version 1.15.6, featuring app version 1.111.0, with improvements driven by the open-source community.

### n8n-chart-version-1.15.7-released

Announcing the new n8n Helm chart v1.15.7 with app version 1.111.1, featuring improved stability and community-supported updates.

- [n8n chart version 1.15.7 released](/blog/n8n-chart-version-1.15.7-released.md): Announcing the new n8n Helm chart v1.15.7 with app version 1.111.1, featuring improved stability and community-supported updates.

### n8n-chart-version-1.15.8-released

Discover what’s new in n8n Helm chart version 1.15.8 with app version 1.112.3, packed with updates and community-powered improvements.

- [n8n chart version 1.15.8 released](/blog/n8n-chart-version-1.15.8-released.md): Discover what’s new in n8n Helm chart version 1.15.8 with app version 1.112.3, packed with updates and community-powered improvements.

### n8n-chart-version-1.15.9-released

Discover what's new in n8n Helm chart v1.15.9 with app version 1.112.4, including updates and community-driven enhancements.

- [n8n chart version 1.15.9 released](/blog/n8n-chart-version-1.15.9-released.md): Discover what's new in n8n Helm chart v1.15.9 with app version 1.112.4, including updates and community-driven enhancements.

### n8n-chart-version-1.16.0-released

Introducing n8n Helm chart version 1.16.0 with app version 1.118.2, featuring improved configuration and community-driven updates to boost your Kubernetes workflows.

- [n8n chart version 1.16.0 now available](/blog/n8n-chart-version-1.16.0-released.md): Introducing n8n Helm chart version 1.16.0 with app version 1.118.2, featuring improved configuration and community-driven updates to boost your Kubernetes workflows.

### n8n-chart-version-1.16.1-released

Announcing the release of n8n chart version 1.16.1 Helm chart, featuring app version 1.119.1, with new features and community-driven improvements.

- [n8n chart version 1.16.1 released](/blog/n8n-chart-version-1.16.1-released.md): Announcing the release of n8n chart version 1.16.1 Helm chart, featuring app version 1.119.1, with new features and community-driven improvements.

### n8n-chart-version-1.16.10-released

Announcing the n8n chart version 1.16.10 with app version 1.123.5, featuring key updates and improvements for Kubernetes deployments.

- [n8n chart version 1.16.10 released](/blog/n8n-chart-version-1.16.10-released.md): Announcing the n8n chart version 1.16.10 with app version 1.123.5, featuring key updates and improvements for Kubernetes deployments.

### n8n-chart-version-1.16.11-released

Announcing the release of the n8n Helm chart version 1.16.11 with app version 2.0.2, featuring improvements to Redis and PostgreSQL dependencies.

- [n8n chart version 1.16.11 released](/blog/n8n-chart-version-1.16.11-released.md): Announcing the release of the n8n Helm chart version 1.16.11 with app version 2.0.2, featuring improvements to Redis and PostgreSQL dependencies.

### n8n-chart-version-1.16.12-released

n8n Helm chart version 1.16.12 is now available with app version 2.0.3, bringing streamlined deployment and community-driven updates.

- [n8n chart version 1.16.12 released](/blog/n8n-chart-version-1.16.12-released.md): n8n Helm chart version 1.16.12 is now available with app version 2.0.3, bringing streamlined deployment and community-driven updates.

### n8n-chart-version-1.16.13-released

Announcing n8n Helm chart version 1.16.13 with app version 2.1.2, featuring enhanced Redis and PostgreSQL support and improved Kubernetes integration.

- [n8n chart version 1.16.13 released](/blog/n8n-chart-version-1.16.13-released.md): Announcing n8n Helm chart version 1.16.13 with app version 2.1.2, featuring enhanced Redis and PostgreSQL support and improved Kubernetes integration.

### n8n-chart-version-1.16.14-released

Discover what's new in the Helm chart release of n8n version 1.16.14 with app version 2.1.4, featuring upgrades and improvements for Kubernetes deployments.

- [n8n chart version 1.16.14 released](/blog/n8n-chart-version-1.16.14-released.md): Discover what's new in the Helm chart release of n8n version 1.16.14 with app version 2.1.4, featuring upgrades and improvements for Kubernetes deployments.

### n8n-chart-version-1.16.2-released

Announcing the n8n chart version 1.16.2 Helm release with app version 1.119.2, featuring updated dependencies and improvements powered by community support.

- [n8n chart version 1.16.2 released](/blog/n8n-chart-version-1.16.2-released.md): Announcing the n8n chart version 1.16.2 Helm release with app version 1.119.2, featuring updated dependencies and improvements powered by community support.

### n8n-chart-version-1.16.3-released

Announcing the release of n8n chart version 1.16.3 Helm chart featuring app version 1.120.3, packed with new features and improvements from the open-source community.

- [n8n chart version 1.16.3 released](/blog/n8n-chart-version-1.16.3-released.md): Announcing the release of n8n chart version 1.16.3 Helm chart featuring app version 1.120.3, packed with new features and improvements from the open-source community.

### n8n-chart-version-1.16.4-released

The n8n Helm chart version 1.16.4 is now available, featuring app version 1.120.4 and enhancements powered by our open-source community.

- [n8n chart version 1.16.4 now available](/blog/n8n-chart-version-1.16.4-released.md): The n8n Helm chart version 1.16.4 is now available, featuring app version 1.120.4 and enhancements powered by our open-source community.

### n8n-chart-version-1.16.45-released

Discover the new features in n8n chart version 1.16.45, featuring app version 2.22.6, and community-driven enhancements for seamless deployment.

- [n8n chart version 1.16.45 released](/blog/n8n-chart-version-1.16.45-released.md): Discover the new features in n8n chart version 1.16.45, featuring app version 2.22.6, and community-driven enhancements for seamless deployment.

### n8n-chart-version-1.16.46-released

Discover the n8n chart version 1.16.46 Helm chart release, featuring app version 2.23.2, with exciting new features and community enhancements.

- [n8n Chart Version 1.16.46 Released](/blog/n8n-chart-version-1.16.46-released.md): Discover the n8n chart version 1.16.46 Helm chart release, featuring app version 2.23.2, with exciting new features and community enhancements.

### n8n-chart-version-1.16.47-released

Announcing the release of n8n chart version 1.16.47 Helm chart, featuring app version 2.23.3, with new features and community-driven improvements.

- [n8n chart version 1.16.47 released](/blog/n8n-chart-version-1.16.47-released.md): Announcing the release of n8n chart version 1.16.47 Helm chart, featuring app version 2.23.3, with new features and community-driven improvements.

### n8n-chart-version-1.16.48-released

Discover the exciting new features in n8n chart version 1.16.48 Helm chart, with app version 2.23.3. Join us in celebrating community-driven enhancements.

- [n8n chart version 1.16.48 released](/blog/n8n-chart-version-1.16.48-released.md): Discover the exciting new features in n8n chart version 1.16.48 Helm chart, with app version 2.23.3. Join us in celebrating community-driven enhancements.

### n8n-chart-version-1.16.49-released

Discover the exciting updates in n8n chart version 1.16.49, featuring app version 2.23.3, new features, and community enhancements.

- [n8n chart version 1.16.49 released](/blog/n8n-chart-version-1.16.49-released.md): Discover the exciting updates in n8n chart version 1.16.49, featuring app version 2.23.3, new features, and community enhancements.

### n8n-chart-version-1.16.5-released

Announcing the release of n8n chart version 1.16.5 Helm chart, featuring app version 1.121.2, with new features and community-driven improvements.

- [n8n chart version 1.16.5 released](/blog/n8n-chart-version-1.16.5-released.md): Announcing the release of n8n chart version 1.16.5 Helm chart, featuring app version 1.121.2, with new features and community-driven improvements.

### n8n-chart-version-1.16.6-released

Announcing the release of n8n chart version 1.16.6 Helm chart, featuring app version 1.121.3, with new features and community-driven improvements.

- [n8n chart version 1.16.6 released](/blog/n8n-chart-version-1.16.6-released.md): Announcing the release of n8n chart version 1.16.6 Helm chart, featuring app version 1.121.3, with new features and community-driven improvements.

### n8n-chart-version-1.16.7-released

Announcing n8n Helm chart version 1.16.7 with app version 1.122.4, featuring new updates and community-led enhancements for Kubernetes users.

- [n8n chart version 1.16.7 released](/blog/n8n-chart-version-1.16.7-released.md): Announcing n8n Helm chart version 1.16.7 with app version 1.122.4, featuring new updates and community-led enhancements for Kubernetes users.

### n8n-chart-version-1.16.8-released

Announcing the n8n Helm chart 1.16.8 release with app version 1.122.5, featuring updated image and deployment enhancements.

- [n8n chart version 1.16.8 released](/blog/n8n-chart-version-1.16.8-released.md): Announcing the n8n Helm chart 1.16.8 release with app version 1.122.5, featuring updated image and deployment enhancements.

### n8n-chart-version-1.16.9-released

Announcing n8n Helm chart version 1.16.9 featuring app version 1.123.4, with enhanced deployment options and community-driven updates.

- [n8n chart version 1.16.9 released](/blog/n8n-chart-version-1.16.9-released.md): Announcing n8n Helm chart version 1.16.9 featuring app version 1.123.4, with enhanced deployment options and community-driven updates.

### n8n-chart-version-1.17.0-released

Discover the new features in n8n chart version 1.17.0 Helm chart, featuring app version 2.23.3, bringing enhancements and community improvements.

- [n8n chart version 1.17.0 released](/blog/n8n-chart-version-1.17.0-released.md): Discover the new features in n8n chart version 1.17.0 Helm chart, featuring app version 2.23.3, bringing enhancements and community improvements.

### n8n-chart-version-1.17.1-released

Discover the exciting features in n8n chart version 1.17.1 Helm chart, featuring app version 2.23.4, with enhancements driven by the community.

- [n8n chart version 1.17.1 released](/blog/n8n-chart-version-1.17.1-released.md): Discover the exciting features in n8n chart version 1.17.1 Helm chart, featuring app version 2.23.4, with enhancements driven by the community.

### n8n-chart-version-1.18.0-released

Announcing the release of n8n chart version 1.18.0 Helm chart, featuring app version 2.23.4, with new features and community-driven improvements.

- [n8n chart version 1.18.0 released](/blog/n8n-chart-version-1.18.0-released.md): Announcing the release of n8n chart version 1.18.0 Helm chart, featuring app version 2.23.4, with new features and community-driven improvements.

### n8n-chart-version-1.19.0-released

Discover the new features of n8n chart version 1.19.0 Helm chart, featuring app version 2.23.4, and improve your automation workflow today.

- [n8n chart version 1.19.0 released](/blog/n8n-chart-version-1.19.0-released.md): Discover the new features of n8n chart version 1.19.0 Helm chart, featuring app version 2.23.4, and improve your automation workflow today.

### n8n-chart-version-1.20.0-released

Announcing the release of n8n chart version 1.20.0 Helm chart, featuring app version 2.23.4, with new features and community-driven improvements.

- [n8n chart version 1.20.0 released](/blog/n8n-chart-version-1.20.0-released.md): Announcing the release of n8n chart version 1.20.0 Helm chart, featuring app version 2.23.4, with new features and community-driven improvements.

### n8n-chart-version-1.21.0-released

Announcing the release of n8n chart version 1.21.0 Helm chart, featuring app version 2.23.4, with new features and community-driven improvements.

- [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md): Announcing the release of n8n chart version 1.21.0 Helm chart, featuring app version 2.23.4, with new features and community-driven improvements.

### n8n-chart-version-1.22.0-released

Discover the features of n8n chart version 1.22.0 Helm chart, featuring app version 2.23.4, along with community enhancements and improvements.

- [n8n chart version 1.22.0 released](/blog/n8n-chart-version-1.22.0-released.md): Discover the features of n8n chart version 1.22.0 Helm chart, featuring app version 2.23.4, along with community enhancements and improvements.

### n8n-chart-version-1.22.1-released

Announcing the release of n8n chart version 1.22.1 Helm chart, featuring app version 2.25.6, with new features and community-driven improvements.

- [n8n chart version 1.22.1 released](/blog/n8n-chart-version-1.22.1-released.md): Announcing the release of n8n chart version 1.22.1 Helm chart, featuring app version 2.25.6, with new features and community-driven improvements.

### n8n-chart-version-1.22.2-released

Discover the exciting features and community improvements in n8n chart version 1.22.2 Helm chart, featuring app version 2.25.7, released on June 11, 2026.

- [n8n chart version 1.22.2 released](/blog/n8n-chart-version-1.22.2-released.md): Discover the exciting features and community improvements in n8n chart version 1.22.2 Helm chart, featuring app version 2.25.7, released on June 11, 2026.

### n8n-chart-version-1.22.3-released

Discover the new features of n8n chart version 1.22.3 Helm chart, featuring app version 2.26.4, with community-driven improvements for easier deployments.

- [n8n chart version 1.22.3 released](/blog/n8n-chart-version-1.22.3-released.md): Discover the new features of n8n chart version 1.22.3 Helm chart, featuring app version 2.26.4, with community-driven improvements for easier deployments.

### n8n-chart-version-1.22.4-released

Announcing the release of n8n chart version 1.22.4 Helm chart, featuring app version 2.26.6, with new features and community-driven improvements.

- [n8n chart version 1.22.4 released](/blog/n8n-chart-version-1.22.4-released.md): Announcing the release of n8n chart version 1.22.4 Helm chart, featuring app version 2.26.6, with new features and community-driven improvements.

### n8n-chart-version-1.22.5-released

Discover the enhancements in n8n chart version 1.22.5 Helm chart, featuring app version 2.26.6, including new features and community contributions.

- [n8n chart version 1.22.5 released](/blog/n8n-chart-version-1.22.5-released.md): Discover the enhancements in n8n chart version 1.22.5 Helm chart, featuring app version 2.26.6, including new features and community contributions.

### n8n-chart-version-1.22.6-released

Announcing the release of n8n chart version 1.22.6 Helm chart, featuring app version 2.26.7, with new features and community-driven improvements.

- [n8n chart version 1.22.6 released](/blog/n8n-chart-version-1.22.6-released.md): Announcing the release of n8n chart version 1.22.6 Helm chart, featuring app version 2.26.7, with new features and community-driven improvements.

### n8n-chart-version-1.22.7-released

Discover the new features and community-driven improvements in n8n chart version 1.22.7 Helm chart, featuring app version 2.26.7.

- [n8n chart version 1.22.7 released](/blog/n8n-chart-version-1.22.7-released.md): Discover the new features and community-driven improvements in n8n chart version 1.22.7 Helm chart, featuring app version 2.26.7.

### n8n-chart-version-1.23.0-released

Announcing the release of n8n chart version 1.23.0 Helm chart, featuring app version 2.26.7, with new features and community-driven improvements.

- [n8n chart version 1.23.0 released](/blog/n8n-chart-version-1.23.0-released.md): Announcing the release of n8n chart version 1.23.0 Helm chart, featuring app version 2.26.7, with new features and community-driven improvements.

### n8n-chart-version-1.23.1-released

Announcing the release of n8n chart version 1.23.1 Helm chart, featuring app version 2.26.8, with new features and community-driven improvements.

- [n8n chart version 1.23.1 released](/blog/n8n-chart-version-1.23.1-released.md): Announcing the release of n8n chart version 1.23.1 Helm chart, featuring app version 2.26.8, with new features and community-driven improvements.

### n8n-chart-version-1.8.6-released

Announcing the release of n8n chart version 1.8.6 Helm chart, featuring app version 1.98.2, with new features and community-driven improvements.

- [n8n chart version 1.8.6 released](/blog/n8n-chart-version-1.8.6-released.md): Announcing the release of n8n chart version 1.8.6 Helm chart, featuring app version 1.98.2, with new features and community-driven improvements.

### n8n-chart-version-1.8.7-released

Announcing the release of n8n chart version 1.8.7 Helm chart, featuring app version 1.99.1, with new features and community-driven improvements.

- [n8n chart version 1.8.7 released](/blog/n8n-chart-version-1.8.7-released.md): Announcing the release of n8n chart version 1.8.7 Helm chart, featuring app version 1.99.1, with new features and community-driven improvements.

### n8n-chart-version-1.9.0-released

Announcing the release of n8n chart version 1.9.0 Helm chart, featuring app version 1.99.1, with new features and community-driven improvements.

- [n8n chart version 1.9.0 released](/blog/n8n-chart-version-1.9.0-released.md): Announcing the release of n8n chart version 1.9.0 Helm chart, featuring app version 1.99.1, with new features and community-driven improvements.

### n8n-chart-version-1.9.1-released

Announcing the release of n8n chart version 1.9.1 Helm chart, featuring app version 1.99.1, with new features and community-driven improvements.

- [n8n chart version 1.9.1 released](/blog/n8n-chart-version-1.9.1-released.md): Announcing the release of n8n chart version 1.9.1 Helm chart, featuring app version 1.99.1, with new features and community-driven improvements.

### outline-chart-version-0.4.0-released

Discover what's new in Outline chart 0.4.0—including expanded external secret support and improved integrations—to simplify your Kubernetes deployments.

- [Outline chart 0.4.0 brings powerful enhancements](/blog/outline-chart-version-0.4.0-released.md): Discover what's new in Outline chart 0.4.0—including expanded external secret support and improved integrations—to simplify your Kubernetes deployments.

### outline-chart-version-0.4.1-released

Discover what's new in outline Helm chart 0.4.1 with updated dependencies, community enhancements, and streamlined Kubernetes deployments.

- [outline chart version 0.4.1 released](/blog/outline-chart-version-0.4.1-released.md): Discover what's new in outline Helm chart 0.4.1 with updated dependencies, community enhancements, and streamlined Kubernetes deployments.

### outline-chart-version-0.4.2-released

Outline Helm chart version 0.4.2 is now live, featuring app version 0.85.1 with enhanced reliability, updated dependencies, and community-led improvements.

- [Outline chart version 0.4.2 now available](/blog/outline-chart-version-0.4.2-released.md): Outline Helm chart version 0.4.2 is now live, featuring app version 0.85.1 with enhanced reliability, updated dependencies, and community-led improvements.

### outline-chart-version-0.4.3-released

Outline Helm chart 0.4.3 is now available, featuring app version 0.85.1 with PostgreSQL fixes and better S3 config—built with community input.

- [Outline chart 0.4.3 released with app version 0.85.1](/blog/outline-chart-version-0.4.3-released.md): Outline Helm chart 0.4.3 is now available, featuring app version 0.85.1 with PostgreSQL fixes and better S3 config—built with community input.

### outline-chart-version-0.5.0-released

Discover outline Helm chart version 0.5.0, featuring app version 0.85.1. Learn about new features, improvements, and how the open-source community contributed.

- [Outline chart version 0.5.0 now available](/blog/outline-chart-version-0.5.0-released.md): Discover outline Helm chart version 0.5.0, featuring app version 0.85.1. Learn about new features, improvements, and how the open-source community contributed.

### outline-chart-version-0.5.1-released

Discover outline Helm chart v0.5.1 featuring app v0.85.1—enhanced auth integration and community-driven improvements for Kubernetes deployments.

- [outline chart version 0.5.1 released](/blog/outline-chart-version-0.5.1-released.md): Discover outline Helm chart v0.5.1 featuring app v0.85.1—enhanced auth integration and community-driven improvements for Kubernetes deployments.

### outline-chart-version-0.6.0-released

Discover what's new in the Outline Helm chart v0.6.0 with app version 0.85.1, including improved PostgreSQL support and key community updates.

- [Outline chart version 0.6.0 released](/blog/outline-chart-version-0.6.0-released.md): Discover what's new in the Outline Helm chart v0.6.0 with app version 0.85.1, including improved PostgreSQL support and key community updates.

### outline-chart-version-0.6.1-released

Discover the new features and upgrades in Outline Helm chart version 0.6.1 with app version 0.86.0, now easier to deploy on Kubernetes with improved Redis and PostgreSQL support.

- [Outline chart version 0.6.1 released](/blog/outline-chart-version-0.6.1-released.md): Discover the new features and upgrades in Outline Helm chart version 0.6.1 with app version 0.86.0, now easier to deploy on Kubernetes with improved Redis and PostgreSQL support.

### outline-chart-version-0.6.2-released

Discover what's new in the Outline Helm chart 0.6.2, now featuring app version 0.86.1, improved dependencies, and community-driven enhancements.

- [Outline chart update 0.6.2 brings app version 0.86.1](/blog/outline-chart-version-0.6.2-released.md): Discover what's new in the Outline Helm chart 0.6.2, now featuring app version 0.86.1, improved dependencies, and community-driven enhancements.

### outline-chart-version-0.6.3-released

Introducing the Outline Helm Chart 0.6.3 release with app version 0.87.1, including updated dependencies and community enhancements.

- [Outline Helm Chart 0.6.3 Released with App Version 0.87.1](/blog/outline-chart-version-0.6.3-released.md): Introducing the Outline Helm Chart 0.6.3 release with app version 0.87.1, including updated dependencies and community enhancements.

### outline-chart-version-0.6.4-released

Discover what's new in Outline Helm chart version 0.6.4 featuring app version 0.87.3, with improvements, updates, and community input.

- [Outline chart update 0.6.4 now available](/blog/outline-chart-version-0.6.4-released.md): Discover what's new in Outline Helm chart version 0.6.4 featuring app version 0.87.3, with improvements, updates, and community input.

### outline-chart-version-0.6.5-released

Discover what's new in Outline Helm chart 0.6.5, featuring app version 0.87.4, with enhancements for easier Kubernetes deployment and community-driven updates.

- [Outline chart version 0.6.5 released](/blog/outline-chart-version-0.6.5-released.md): Discover what's new in Outline Helm chart 0.6.5, featuring app version 0.87.4, with enhancements for easier Kubernetes deployment and community-driven updates.

### outline-chart-version-0.7.0-released

Discover Outline Helm chart version 0.7.0, featuring app version 0.87.4, with new enhancements and improved Kubernetes deployment capabilities.

- [Outline chart 0.7.0 released with app version 0.87.4](/blog/outline-chart-version-0.7.0-released.md): Discover Outline Helm chart version 0.7.0, featuring app version 0.87.4, with new enhancements and improved Kubernetes deployment capabilities.

### outline-chart-version-0.7.1-released

Outline Helm chart 0.7.1 is now available with app version 1.0.0, featuring improved dependencies and community enhancements.

- [Outline chart update 0.7.1 with app version 1.0.0](/blog/outline-chart-version-0.7.1-released.md): Outline Helm chart 0.7.1 is now available with app version 1.0.0, featuring improved dependencies and community enhancements.

### outline-chart-version-0.7.2-released

Discover what's new in Outline Helm chart 0.7.2 with app version 1.0.1, now featuring updated Redis and PostgreSQL dependencies for improved Kubernetes readiness.

- [Outline chart 0.7.2 includes app version 1.0.1 with Redis and Postgres updates](/blog/outline-chart-version-0.7.2-released.md): Discover what's new in Outline Helm chart 0.7.2 with app version 1.0.1, now featuring updated Redis and PostgreSQL dependencies for improved Kubernetes readiness.

### outline-chart-version-0.7.3-released

Discover outline Helm chart version 0.7.3 featuring app version 1.1.0, with updated dependencies and community-powered enhancements.

- [Outline chart version 0.7.3 released](/blog/outline-chart-version-0.7.3-released.md): Discover outline Helm chart version 0.7.3 featuring app version 1.1.0, with updated dependencies and community-powered enhancements.

### outline-chart-version-0.7.4-released

Discover the new features and improvements in outline chart version 0.7.4 Helm chart, featuring app version 1.7.1. Join our community-driven journey!

- [Outline Chart Version 0.7.4 Released](/blog/outline-chart-version-0.7.4-released.md): Discover the new features and improvements in outline chart version 0.7.4 Helm chart, featuring app version 1.7.1. Join our community-driven journey!

### outline-chart-version-0.7.5-released

Announcing the release of Outline chart version 0.7.5 Helm chart, featuring app version 1.8.0, with new features and community-driven improvements.

- [Outline Chart Version 0.7.5 Released](/blog/outline-chart-version-0.7.5-released.md): Announcing the release of Outline chart version 0.7.5 Helm chart, featuring app version 1.8.0, with new features and community-driven improvements.

### outline-chart-version-0.8.0-released

Discover the enhanced outline chart version 0.8.0 with app version 1.8.0, featuring new functionalities and community-driven improvements.

- [Outline Chart Version 0.8.0 Released](/blog/outline-chart-version-0.8.0-released.md): Discover the enhanced outline chart version 0.8.0 with app version 1.8.0, featuring new functionalities and community-driven improvements.

### outline-chart-version-0.8.1-released

Announcing the release of Outline Chart version 0.8.1 Helm chart, featuring app version 1.8.1, with new features and community-driven improvements.

- [Outline Chart Version 0.8.1 Released](/blog/outline-chart-version-0.8.1-released.md): Announcing the release of Outline Chart version 0.8.1 Helm chart, featuring app version 1.8.1, with new features and community-driven improvements.

### outline-chart-version-0.9.0-released

Announcing the release of outline chart version 0.9.0 Helm chart, featuring app version 1.8.1, with new features and community-driven improvements.

- [outline chart version 0.9.0 released](/blog/outline-chart-version-0.9.0-released.md): Announcing the release of outline chart version 0.9.0 Helm chart, featuring app version 1.8.1, with new features and community-driven improvements.

### page


#### 10

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/10.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 11

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/11.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 12

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/12.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 13

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/13.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 14

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/14.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 15

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/15.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 16

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/16.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 2

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/2.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 3

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/3.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 4

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/4.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 5

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/5.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 6

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/6.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 7

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/7.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 8

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/8.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

#### 9

Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

- [Community Charts Blog Posts](/blog/page/9.md): Discover Community Helm Charts blog posts for new chart releases, Kubernetes deployment guides, updates, and tips for open-source DevOps solutions.

### pypiserver-chart-version-0.1.8-released

Discover what's new in the pypiserver Helm chart version 0.1.8, featuring app version v2.4.0, with key updates and enhancements for Kubernetes deployments.

- [pypiserver chart version 0.1.8 released](/blog/pypiserver-chart-version-0.1.8-released.md): Discover what's new in the pypiserver Helm chart version 0.1.8, featuring app version v2.4.0, with key updates and enhancements for Kubernetes deployments.

### tags

Browse all tags for blog posts about Helm, Kubernetes, and more. Find topics and discover content in the Community Charts blog.

- [Tags](/blog/tags.md): Browse all tags for blog posts about Helm, Kubernetes, and more. Find topics and discover content in the Community Charts blog.

#### actual-budget

Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.

- [12 posts tagged with "Actual Budget"](/blog/tags/actual-budget.md): Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.
- [12 posts tagged with "Actual Budget"](/blog/tags/actual-budget/page/2.md): Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.

#### ci-cd

Discover expert CI/CD strategies, automation workflows, and top tools for continuous integration and continuous deployment to accelerate your software delivery pipeline.

- [One post tagged with "CI/CD"](/blog/tags/ci-cd.md): Discover expert CI/CD strategies, automation workflows, and top tools for continuous integration and continuous deployment to accelerate your software delivery pipeline.

#### cloud-databases

Expert guides and best practices for connecting to managed cloud databases and caches on AWS, Azure, GCP, and other leading cloud providers.

- [One post tagged with "Cloud Databases"](/blog/tags/cloud-databases.md): Expert guides and best practices for connecting to managed cloud databases and caches on AWS, Azure, GCP, and other leading cloud providers.

#### cloudflared

Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.

- [14 posts tagged with "Cloudflared"](/blog/tags/cloudflared.md): Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.
- [14 posts tagged with "Cloudflared"](/blog/tags/cloudflared/page/2.md): Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.

#### community

Join a vibrant community where ideas, projects, and support come together to help everyone grow and succeed.

- [One post tagged with "Community"](/blog/tags/community.md): Join a vibrant community where ideas, projects, and support come together to help everyone grow and succeed.

#### devops

Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.

- [7 posts tagged with "DevOps"](/blog/tags/devops.md): Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.

#### drone

Build, test, and deploy your code confidently with Drone, a friendly and powerful CI/CD platform for developers.

- [One post tagged with "Drone"](/blog/tags/drone.md): Build, test, and deploy your code confidently with Drone, a friendly and powerful CI/CD platform for developers.

#### helm

Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.

- [159 posts tagged with "Helm"](/blog/tags/helm.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/10.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/11.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/12.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/13.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/14.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/15.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/16.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/2.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/3.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/4.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/5.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/6.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/7.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/8.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.
- [159 posts tagged with "Helm"](/blog/tags/helm/page/9.md): Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.

#### kubernetes

Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.

- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/10.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/11.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/12.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/13.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/14.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/15.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/16.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/2.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/3.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/4.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/5.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/6.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/7.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/8.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.
- [159 posts tagged with "Kubernetes"](/blog/tags/kubernetes/page/9.md): Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.

#### mlflow

Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.

- [29 posts tagged with "Mlflow"](/blog/tags/mlflow.md): Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.
- [29 posts tagged with "Mlflow"](/blog/tags/mlflow/page/2.md): Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.
- [29 posts tagged with "Mlflow"](/blog/tags/mlflow/page/3.md): Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.

#### n8n

Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.

- [81 posts tagged with "n8n"](/blog/tags/n8n.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/2.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/3.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/4.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/5.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/6.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/7.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/8.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.
- [81 posts tagged with "n8n"](/blog/tags/n8n/page/9.md): Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.

#### open-source

Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.

- [159 posts tagged with "Open Source"](/blog/tags/open-source.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/10.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/11.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/12.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/13.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/14.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/15.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/16.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/2.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/3.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/4.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/5.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/6.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/7.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/8.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.
- [159 posts tagged with "Open Source"](/blog/tags/open-source/page/9.md): Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.

#### outline

Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.

- [21 posts tagged with "Outline"](/blog/tags/outline.md): Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.
- [21 posts tagged with "Outline"](/blog/tags/outline/page/2.md): Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.
- [21 posts tagged with "Outline"](/blog/tags/outline/page/3.md): Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.

#### postgres

Learn how to configure applications with PostgreSQL for reliable data storage, including guides for managed PostgreSQL on AWS, Google Cloud, and Azure.

- [3 posts tagged with "Postgres"](/blog/tags/postgres.md): Learn how to configure applications with PostgreSQL for reliable data storage, including guides for managed PostgreSQL on AWS, Google Cloud, and Azure.

#### pypiserver

Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.

- [One post tagged with "PyPI Server"](/blog/tags/pypiserver.md): Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.

#### redis

Configure your applications with Redis for caching, queueing, and real-time data, including managed Redis on major cloud providers.

- [3 posts tagged with "Redis"](/blog/tags/redis.md): Configure your applications with Redis for caching, queueing, and real-time data, including managed Redis on major cloud providers.

### welcome-to-community-charts

Discover GitHub Community Charts - Helm charts for MLflow, n8n, & more. Join our community-driven Kubernetes project!

- [Welcome to Helm Charts - Kubernetes with Community Power](/blog/welcome-to-community-charts.md): Discover GitHub Community Charts - Helm charts for MLflow, n8n, & more. Join our community-driven Kubernetes project!

## search

- [Search the documentation](/search.md)

## docs


### category


#### actualbudget

Documentation for deploying Actual Budget on Kubernetes using the community-maintained Helm chart.

- [Actual Budget Helm Chart](/docs/category/actualbudget.md): Documentation for deploying Actual Budget on Kubernetes using the community-maintained Helm chart.

#### charts

Browse all charts

- [Charts](/docs/category/charts.md): Browse all charts

#### cloudflared

Documentation for deploying Cloudflared Tunnel on Kubernetes using the community-maintained Helm chart.

- [Cloudflared Tunnel Helm Chart](/docs/category/cloudflared.md): Documentation for deploying Cloudflared Tunnel on Kubernetes using the community-maintained Helm chart.

#### drone

Documentation for deploying Drone CI on Kubernetes using the community-maintained Helm chart.

- [Drone CI Helm Chart](/docs/category/drone.md): Documentation for deploying Drone CI on Kubernetes using the community-maintained Helm chart.

#### mlflow

Documentation for deploying MLflow on Kubernetes using the community-maintained Helm chart.

- [MLflow Helm Chart](/docs/category/mlflow.md): Documentation for deploying MLflow on Kubernetes using the community-maintained Helm chart.

#### n8n

Documentation for deploying n8n on Kubernetes using the community-maintained Helm chart.

- [N8N Helm Chart](/docs/category/n8n.md): Documentation for deploying n8n on Kubernetes using the community-maintained Helm chart.

#### outline

Documentation for deploying Outline on Kubernetes using the community-maintained Helm chart.

- [Outline Helm Chart](/docs/category/outline.md): Documentation for deploying Outline on Kubernetes using the community-maintained Helm chart.

#### pypiserver

Documentation for deploying minimal PyPI Server on Kubernetes using the community-maintained Helm chart.

- [PyPI Server Helm Chart](/docs/category/pypiserver.md): Documentation for deploying minimal PyPI Server on Kubernetes using the community-maintained Helm chart.

### charts


#### actualbudget

- [Advanced Configuration](/docs/charts/actualbudget/advanced-configuration.md): Advanced configuration options for Actual Budget including security, networking, and customization
- [Authentication Setup](/docs/charts/actualbudget/authentication.md): Configure authentication methods for Actual Budget including password, header-based, and OpenID Connect
- [Configuration Guide](/docs/charts/actualbudget/configuration.md): Learn how to configure the Actual Budget Helm chart for your deployment
- [Storage and Persistence](/docs/charts/actualbudget/storage.md): Configure persistent storage and data management for Actual Budget deployments
- [Troubleshooting](/docs/charts/actualbudget/troubleshooting.md): Common issues and solutions for Actual Budget Helm chart deployments
- [Actual Budget Chart Usage Guide](/docs/charts/actualbudget/usage.md): Get started with Actual Budget Helm chart deployment and basic usage

#### cloudflared

- [Advanced Configuration](/docs/charts/cloudflared/advanced-configuration.md): Advanced configuration options for Cloudflared Tunnel including high availability, monitoring, and customization
- [Configuration Guide](/docs/charts/cloudflared/configuration.md): Learn how to configure the Cloudflared Tunnel Helm chart for your deployment
- [Ingress Configuration](/docs/charts/cloudflared/ingress-configuration.md): Configure ingress rules for Cloudflare Tunnel to route traffic to your Kubernetes services
- [Troubleshooting](/docs/charts/cloudflared/troubleshooting.md): Common issues and solutions for Cloudflared Tunnel Helm chart deployments
- [Tunnel Setup Guide](/docs/charts/cloudflared/tunnel-setup.md): Set up Cloudflare Tunnel for secure access to your Kubernetes services
- [Cloudflared Chart Usage Guide](/docs/charts/cloudflared/usage.md): Learn how to deploy and use Cloudflared Tunnel with the community-maintained Helm chart

#### drone

- [Advanced Configuration](/docs/charts/drone/advanced-configuration.md): Advanced configuration options for Drone Helm chart, including runners, RBAC, and custom Kubernetes settings.
- [Authentication Guide](/docs/charts/drone/authentication.md): How to configure authentication providers for Drone using the Helm chart.
- [Configuration Guide](/docs/charts/drone/configuration.md): Detailed guide to configuring the Drone Helm chart for production and custom use cases.
- [Storage Guide](/docs/charts/drone/storage.md): Guide to persistent storage and database configuration for Drone Helm chart deployments.
- [Troubleshooting Guide](/docs/charts/drone/troubleshooting.md): Troubleshooting common issues with the Drone Helm chart on Kubernetes.
- [Drone Chart Usage Guide](/docs/charts/drone/usage.md): How to install, upgrade, and use the Drone Helm chart for CI/CD on Kubernetes.

#### mlflow

- [Authentication Configuration](/docs/charts/mlflow/authentication-configuration.md): Complete guide to configuring authentication for MLflow on Kubernetes. Learn about basic auth, LDAP integration, PostgreSQL auth backend, and enterprise security features.
- [Autoscaling Setup](/docs/charts/mlflow/autoscaling-setup.md): Complete guide to configuring autoscaling for MLflow on Kubernetes. Learn about Horizontal Pod Autoscaler (HPA), and cluster autoscaling strategies.
- [AWS S3 Integration](/docs/charts/mlflow/aws-s3-integration.md): Complete guide to configuring MLflow with AWS S3 for artifact storage. Learn about IAM roles, MinIO compatibility, and production-ready S3 configurations.
- [Azure Blob Storage Integration](/docs/charts/mlflow/azure-blob-storage-integration.md): Complete guide to configuring MLflow with Azure Blob Storage for artifact storage. Learn about managed identities, service principals, and production-ready Azure configurations.
- [Basic Installation with SQLite](/docs/charts/mlflow/basic-installation.md): Step-by-step guide to installing MLflow with SQLite backend on Kubernetes using the community-maintained Helm chart. Perfect for development, testing, and small-scale deployments.
- [Google Cloud Storage Integration](/docs/charts/mlflow/google-cloud-storage-integration.md): Complete guide to configuring MLflow with Google Cloud Storage for artifact storage. Learn about service accounts, IAM roles, and production-ready GCS configurations.
- [MySQL Backend Installation](/docs/charts/mlflow/mysql-backend-installation.md): Complete guide to setting up MLflow with MySQL backend on Kubernetes. Learn about database migrations, PyMySQL driver, and production-ready configurations.
- [PostgreSQL Backend Installation](/docs/charts/mlflow/postgresql-backend-installation.md): Complete guide to setting up MLflow with PostgreSQL backend on Kubernetes. Learn about database migrations, connection health checks, and production-ready configurations.
- [Troubleshooting and Monitoring](/docs/charts/mlflow/troubleshooting-and-monitoring.md): Comprehensive troubleshooting guide for MLflow on Kubernetes. Learn about common issues, debugging techniques, monitoring setup, and performance optimization.
- [MLflow Chart Usage](/docs/charts/mlflow/usage.md): Complete guide to deploying and configuring MLflow on Kubernetes using the community-maintained Helm chart. Learn about databases, cloud storage, authentication, autoscaling, and monitoring.

#### n8n

- [Managed Redis Setup for n8n](/docs/charts/n8n/cloud-redis.md): Configure n8n to use managed Redis services on GCP, AWS, and Azure for queue mode and production deployments.
- [n8n Configuration Reference](/docs/charts/n8n/configuration.md): Comprehensive configuration reference for the n8n Helm chart with detailed examples and enterprise best practices
- [n8n Database Setup](/docs/charts/n8n/database-setup.md): Complete guide to setting up and configuring databases for n8n on Kubernetes
- [n8n Monitoring Setup](/docs/charts/n8n/monitoring.md): Complete guide to setting up monitoring and observability for n8n including Prometheus metrics, logging, health checks, and alerting
- [n8n Queue Mode Setup](/docs/charts/n8n/queue-mode.md): Complete guide to setting up n8n in queue mode for distributed execution with Redis, worker nodes, and webhook nodes
- [n8n Storage Configuration](/docs/charts/n8n/storage.md): Complete guide to configuring binary data storage for n8n including filesystem, S3-compatible storage, and MinIO integration
- [n8n Troubleshooting Guide](/docs/charts/n8n/troubleshooting.md): Common issues and solutions for n8n Helm chart deployments
- [n8n Chart Usage Guide](/docs/charts/n8n/usage.md): Deploy and configure n8n on Kubernetes with enterprise-grade features using our community-maintained Helm chart

#### outline

- [Advanced Configuration](/docs/charts/outline/advanced-configuration.md): Advanced configuration options for Outline including integrations, SMTP, monitoring, and customization
- [Authentication Setup](/docs/charts/outline/authentication.md): Configure authentication methods for Outline including Google, Azure, OIDC, Slack, GitHub, and more
- [Configuration Guide](/docs/charts/outline/configuration.md): Learn how to configure the Outline Helm chart for your deployment
- [Database Configuration](/docs/charts/outline/database.md): Configure PostgreSQL database for Outline including built-in and external database options
- [Storage Configuration](/docs/charts/outline/storage.md): Configure file storage for Outline including local storage and S3-compatible storage
- [Troubleshooting](/docs/charts/outline/troubleshooting.md): Common issues and solutions for Outline Helm chart deployments
- [Outline Chart Usage Guide](/docs/charts/outline/usage.md): Get started with Outline Helm chart deployment and basic usage

#### pypiserver

- [Advanced Configuration](/docs/charts/pypiserver/advanced-configuration.md): Advanced PyPI Server configuration for production deployments, high availability, monitoring, and security
- [Configuration](/docs/charts/pypiserver/configuration.md): Learn how to configure PyPI Server chart with custom values, environment variables, and deployment options
- [Storage](/docs/charts/pypiserver/storage.md): Configure persistent storage for PyPI Server packages, authentication files, and data persistence
- [Troubleshooting](/docs/charts/pypiserver/troubleshooting.md): Common issues, debugging commands, and solutions for PyPI Server Helm chart deployments
- [PyPI Server Chart Usage](/docs/charts/pypiserver/usage.md): Learn how to deploy and use PyPI Server on Kubernetes with the community-maintained Helm chart

### getting-started

Learn how to add the GitHub Community Charts Helm repository and start deploying open-source tools like MLflow, n8n, and Actual Budget on Kubernetes.

- [Getting Started with GitHub Community Charts](/docs/getting-started.md): Learn how to add the GitHub Community Charts Helm repository and start deploying open-source tools like MLflow, n8n, and Actual Budget on Kubernetes.


---

# Full Documentation Content

## [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md)

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **mlflow Helm chart version 1.11.2** on June 21, 2026, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements to streamline the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.2 chart[​](#whats-new-in-mlflow-1112-chart "Direct link to What's New in mlflow 1.11.2 chart")

This latest version includes important updates to the Helm chart (version 1.11.2) alongside the underlying application (version 3.14.0). Here’s a brief overview of the enhancements:

* **Changed**: Updated dbchecker image version to 1.38.0
  <!-- -->
  * [dbchecker](https://hub.docker.com/r/library/busybox)
* **Changed**: Updated ini-file-initializer image version to 1.38.0
  <!-- -->
  * [ini-file-initializer](https://hub.docker.com/r/library/busybox)

For a comprehensive list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.2) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.11.2-released.md)


---

# actualbudget chart version 1.7.0 released

June 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **actualbudget Helm chart version 1.7.0** on 2025-06-24, featuring **app version 25.6.1**. This update brings new features, enhancements, and community-driven improvements to simplify deploying actualbudget on Kubernetes.

## What's New in actualbudget 1.7.0 chart[​](#whats-new-in-actualbudget-170-chart "Direct link to What's New in actualbudget 1.7.0 chart")

This release includes updates to the Helm chart (version 1.7.0) and the underlying application (version 25.6.1). Below is the detailed changelog:

* **Changed**: Change pod security context to actual user and group
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/pull/144)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.7.0) on GitHub.

<!-- -->

## Getting Started with actualbudget 1.7.0 chart[​](#getting-started-with-actualbudget-170-chart "Direct link to Getting Started with actualbudget 1.7.0 chart")

Ready to deploy actualbudget 1.7.0? Our [installation guides](https://community-charts.github.io/docs/category/actualbudget) provide step-by-step instructions to get you started, including:

* Quick installation with default configurations.
* Customizing settings to suit your environment.
* Best practices for production deployments.

Visit the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) to explore all available options and deploy actualbudget today.

## Why Choose the actualbudget Helm Chart?[​](#why-choose-the-actualbudget-helm-chart "Direct link to Why Choose the actualbudget Helm Chart?")

The actualbudget helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying actualbudget on Kubernetes straightforward and reliable. Key benefits include:

* **Ease of Use**: Simplified installation and configuration.
* **Community-Driven**: Regular updates and improvements from contributors.
* **Flexibility**: Configurable options to meet diverse use cases.
* **Reliability**: Tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a community-driven project, and we welcome your contributions! Whether you're fixing bugs, improving documentation, or suggesting new features, here's how you can get started:

* **Explore the Chart**: Check out the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting actualbudget and GitHub Community Charts. Let's continue making Kubernetes deployments easier, together!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-24-actualbudget-chart-version-1-7-0-released.md)


---

# actualbudget chart version 1.7.1 update now available

July 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the **actualbudget Helm chart (v1.7.1)** is now available as of July 2, 2025. This release also includes the updated **application version 25.7.0**, bringing helpful improvements and refinements based on community feedback to enhance your Kubernetes deployment experience.

## What’s New in actualbudget 1.7.1[​](#whats-new-in-actualbudget-171 "Direct link to What’s New in actualbudget 1.7.1")

This release updates both the Helm chart (v1.7.1) and the actualbudget application (v25.7.0). Here’s a summary of the latest changes:

* ✅ **Updated**: Upgraded the container image to actualbudget/actual-server version 25.7.0
  <!-- -->
  * View on [Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For full details, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.7.1).

<!-- -->

## Get Started with actualbudget 1.7.1[​](#get-started-with-actualbudget-171 "Direct link to Get Started with actualbudget 1.7.1")

Deploying actualbudget is easier than ever. Our [installation documentation](https://community-charts.github.io/docs/category/actualbudget) walks you through everything you need, including:

* Fast installation using default settings
* Custom configuration options for various environments
* Deployment tips for stable, production-ready setups

Visit the [actualbudget chart docs](https://community-charts.github.io/docs/category/actualbudget) to get started today.

## Why Use the actualbudget Helm Chart?[​](#why-use-the-actualbudget-helm-chart "Direct link to Why Use the actualbudget Helm Chart?")

The actualbudget Helm chart—maintained by the [GitHub Community Charts Project](https://github.com/community-charts/helm-charts)—makes running actualbudget on Kubernetes a seamless experience. Here's why users love it:

* 🚀 **Easy to Use**: Get up and running quickly with intuitive setups
* 🤝 **Community-Powered**: Regular updates and improvements from open source contributors
* ⚙️ **Highly Configurable**: Tailor deployments to meet specific needs
* 🛡️ **Reliable**: Designed for strength and stability in real-world environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The GitHub Community Charts project thrives on community input—and you’re invited to be a part of it! There are plenty of ways to contribute:

* 🔍 Explore [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) to learn more
* 📥 Contribute via pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Report issues or share feedback by opening a [GitHub issue](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being a part of the actualbudget and GitHub Community Charts journey. Together, we're making Kubernetes deployments better every day!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-02-actualbudget-chart-version-1-7-1-released.md)


---

# actualbudget chart version 1.7.2 released

July 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the actualbudget Helm chart, **v1.7.2**, is officially available as of **July 3, 2025**. This release includes the updated **app version 25.7.1**, introducing new features and enhancements to make deploying actualbudget on Kubernetes even smoother.

## What’s New in actualbudget Helm Chart 1.7.2[​](#whats-new-in-actualbudget-helm-chart-172 "Direct link to What’s New in actualbudget Helm Chart 1.7.2")

This release brings improvements to both the Helm chart (v1.7.2) and the actualbudget application (v25.7.1). Highlights include:

* ✅ **Updated**: actualbudget/actual-server container image to version 25.7.1
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For the full list of changes and technical details, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.7.2).

<!-- -->

## How to Get Started with actualbudget 1.7.2[​](#how-to-get-started-with-actualbudget-172 "Direct link to How to Get Started with actualbudget 1.7.2")

Ready to upgrade or install? Our handy [installation guides](https://community-charts.github.io/docs/category/actualbudget) walk you through everything you need:

* Quick setup using default configs
* Steps to tailor deployments to your environment
* Best practices for production rollouts

Visit our [official documentation](https://community-charts.github.io/docs/category/actualbudget) to explore all your options and get up and running today.

## Why Use the actualbudget Helm Chart?[​](#why-use-the-actualbudget-helm-chart "Direct link to Why Use the actualbudget Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the actualbudget Helm chart is built for simplicity and reliability on Kubernetes.

Benefits include:

* 🎯 **Simple setup**: Get started quickly with minimal configuration
* 🌍 **Community powered**: Continuously improved by contributors like you
* 🔧 **Highly customizable**: Flexible settings for diverse use cases
* 🧪 **Proven stability**: Tested across Kubernetes environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

actualbudget and GitHub Community Charts are open-source and community-driven—we’d love your involvement! Here are a few ways to contribute:

* 📘 Dive into the [documentation](https://community-charts.github.io/docs/category/actualbudget) to learn the ins and outs
* 🔧 Submit PRs on our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Found a bug? [Report it here](https://github.com/community-charts/helm-charts/issues)
* 💡 Have ideas? [Request features](https://github.com/community-charts/helm-charts/issues/new)

Thanks for helping us make Kubernetes deployments better and more accessible for everyone. Let’s build amazing things—together!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-03-actualbudget-chart-version-1-7-2-released.md)


---

# actualbudget chart version 1.8.0 released

July 27, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **actualbudget Helm chart version 1.8.0**, published on **July 27, 2025**, and bundled with **application version 25.7.1**. This release includes handy new features and improvements inspired by the community to streamline how you deploy actualbudget on Kubernetes.

## Highlights in actualbudget 1.8.0[​](#highlights-in-actualbudget-180 "Direct link to Highlights in actualbudget 1.8.0")

With this chart update, actualbudget continues to grow as a Kubernetes-friendly, open-source budgeting solution. Here’s what’s new in version 1.8.0:

* ✅ **Support for existing secret** for OpenID provider makes integration smoother.
  <br />
  [View Issue #186](https://github.com/community-charts/helm-charts/issues/186)
* ✅ **New parameters** `authMethod` and `tokenExpiration` added for OpenID provider, giving you better authentication controls.
  <br />
  [View Issue #188](https://github.com/community-charts/helm-charts/issues/188)

To dive into the full list of changes, check out the [official release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.0).

<!-- -->

## Get Started with actualbudget 1.8.0[​](#get-started-with-actualbudget-180 "Direct link to Get Started with actualbudget 1.8.0")

Deploying actualbudget with Helm has never been easier. Whether you're spinning up a test deployment or going into production, our [installation guides](https://community-charts.github.io/docs/category/actualbudget) have you covered with:

* One-command quickstart using default values.
* Full customization for your infrastructure or cloud setup.
* Tips and best practices for monitoring and scaling.

Visit the [actualbudget docs](https://community-charts.github.io/docs/category/actualbudget) to get everything up and running in minutes.

## Why use the actualbudget Helm chart?[​](#why-use-the-actualbudget-helm-chart "Direct link to Why use the actualbudget Helm chart?")

The actualbudget Helm chart—maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project—is tailored to support secure, flexible, and scalable deployments on Kubernetes. Here's why users love it:

* 🛠️ **Easy to Use** – Install and update with a few Helm commands.
* 🌍 **Open-Source & Community-Backed** – Constantly evolving thanks to contributors like you.
* 🔧 **Highly Configurable** – Supports a wide range of deployment needs.
* 💡 **Production-Ready** – Regularly tested for stability and Kubernetes compatibility.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We're building this together! Whether you’d like to improve the chart, share your feedback, or report an issue, here are a few ways to get involved:

* 📚 Learn more in the [official documentation](https://community-charts.github.io/docs/category/actualbudget).
* 🤝 Contribute via pull requests at our [GitHub repository](https://github.com/community-charts/helm-charts).
* 🐞 Report bugs or issues through our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Suggest a feature or enhancement that can help others in the community.

Thank you to all contributors who help make actualbudget even better with every release. Let’s keep building a great open-source experience for everyone running Kubernetes!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-27-actualbudget-chart-version-1-8-0-released.md)


---

# actualbudget chart version 1.8.1 released

August 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the official release of the **actualbudget Helm chart v1.8.1**, featuring **application version 25.8.0**, as of August 2, 2025. This update delivers a more seamless Kubernetes deployment experience, with new capabilities and key improvements inspired by community feedback.

## What's New in Helm Chart 1.8.1[​](#whats-new-in-helm-chart-181 "Direct link to What's New in Helm Chart 1.8.1")

This release includes important refinements to the Helm chart and brings the actual budgeting application up to version 25.8.0:

* 📦 **Updated**: Docker image for `actualbudget/actual-server` is now set to `25.8.0`
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For a complete breakdown of the changes in this release, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.1).

<!-- -->

## Quick Start Guide[​](#quick-start-guide "Direct link to Quick Start Guide")

Ready to get started with actualbudget 1.8.1? Whether you're testing locally or rolling out in a production environment, our [step-by-step documentation](https://community-charts.github.io/docs/category/actualbudget) has you covered:

* 🚀 Quick install with sensible defaults
* ⚙️ Customize settings to fit your environment
* 🛡️ Recommended practices for production-grade deployments

Explore the full [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) and deploy with confidence.

## Why Use the actualbudget Helm Chart?[​](#why-use-the-actualbudget-helm-chart "Direct link to Why Use the actualbudget Helm Chart?")

The actualbudget Helm chart—maintained by the [GitHub Community Charts project](https://github.com/community-charts/helm-charts)—makes it easier than ever to run actualbudget on Kubernetes. Here’s why developers love it:

* 🔧 **User-Friendly**: Set up and go with minimal fuss
* 🤝 **Community-Powered**: Shaped by open-source contributors
* 🧩 **Customizable**: Adaptable to your unique deployment needs
* 🧪 **Proven Reliable**: Tested and optimized for Kubernetes environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Our charts are powered by open-source collaboration, and there are many ways you can get involved:

* 📖 Dive into the [actualbudget docs](https://community-charts.github.io/docs/category/actualbudget)
* 🧑‍💻 Contribute code or improvements in our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Found a bug? [Report an issue](https://github.com/community-charts/helm-charts/issues)
* 💡 Have a feature idea? [Submit a request](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the actualbudget and GitHub Community Charts ecosystem. Let’s keep making Kubernetes application deployments simpler—together!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-02-actualbudget-chart-version-1-8-1-released.md)


---

# actualbudget chart version 1.8.2 released

September 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to announce the release of the **actualbudget Helm chart version 1.8.2**, officially available as of September 4, 2025. This update ships with **application version 25.9.0**, bringing usability improvements and valuable community-driven enhancements to streamline your Kubernetes deployments.

## What’s New in actualbudget 1.8.2[​](#whats-new-in-actualbudget-182 "Direct link to What’s New in actualbudget 1.8.2")

The actualbudget chart version 1.8.2 introduces an updated container image and improvements that align with the newest features of the application. Highlights include:

* 🔄 **Updated**: Bumped `actualbudget/actual-server` image to version **25.9.0**
  <br />
  <!-- -->
  → [View Docker Image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

To view the full list of changes, check out the [actualbudget 1.8.2 release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.2).

<!-- -->

## Get Started with actualbudget 1.8.2[​](#get-started-with-actualbudget-182 "Direct link to Get Started with actualbudget 1.8.2")

Ready to deploy the latest release? Follow our comprehensive [installation guides](https://community-charts.github.io/docs/category/actualbudget) to get started quickly:

* Deploy using default configurations in just a few steps.
* Customize the chart to fit your specific production or development environment.
* Discover best practices for managing actualbudget on Kubernetes.

Explore the full [documentation here](https://community-charts.github.io/docs/category/actualbudget).

## Why Use the actualbudget Helm Chart?[​](#why-use-the-actualbudget-helm-chart "Direct link to Why Use the actualbudget Helm Chart?")

The actualbudget chart, maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), offers a simplified and reliable way to run actualbudget in Kubernetes. Here’s what makes it stand out:

* 🚀 **Simple Setup**: Quick to install with ready-to-use defaults.
* 🤝 **Community Focused**: Constantly improved by contributors worldwide.
* ⚙️ **Customizable**: Easily adapt the deployment to your infrastructure needs.
* ✅ **Kubernetes Ready**: Tested for resilience across various environments.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Be part of our growing open-source community! There are many ways to contribute and engage:

* 📚 Dive into the [documentation](https://community-charts.github.io/docs/category/actualbudget) for configuration details.
* 🛠 Contribute by submitting pull requests to the [GitHub repository](https://github.com/community-charts/helm-charts).
* 🐛 Found a bug or have feedback? [Open an issue](https://github.com/community-charts/helm-charts/issues).
* 💡 Share your ideas by [requesting features](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being a part of the actualbudget journey. Your support helps us grow a thriving open-source ecosystem around Kubernetes and Helm!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-04-actualbudget-chart-version-1-8-2-released.md)


---

# actualbudget chart version 1.8.3 released

October 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the 🧾 **actualbudget Helm chart (v1.8.3)** is now available, featuring the newly updated **app version 25.10.0**, as of 2025-10-03. This version continues our focus on improving the experience of deploying actualbudget on Kubernetes with enhanced support, better performance, and key community contributions.

## What’s New in actualbudget 1.8.3[​](#whats-new-in-actualbudget-183 "Direct link to What’s New in actualbudget 1.8.3")

This release includes both chart and application updates to keep your deployments modern and efficient:

* ✅ **Updated:** actualbudget/actual-server image upgraded to version 25.10.0
  <br />
  <!-- -->
  ↳ View the [Docker image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For a full list of changes and enhancements, check out the official [v1.8.3 release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.3) on GitHub.

<!-- -->

## Getting Started with actualbudget 1.8.3[​](#getting-started-with-actualbudget-183 "Direct link to Getting Started with actualbudget 1.8.3")

Ready to try the new release? Whether you're setting up a new environment or upgrading from a previous version, our [step-by-step installation guides](https://community-charts.github.io/docs/category/actualbudget) will walk you through:

* Quickstart installs with minimal configuration
* Tailoring the chart to your Kubernetes environment
* Applying production best practices

Dive into the [official documentation](https://community-charts.github.io/docs/category/actualbudget) and get actualbudget running today in just a few steps.

## Why Deploy actualbudget with Helm?[​](#why-deploy-actualbudget-with-helm "Direct link to Why Deploy actualbudget with Helm?")

The actualbudget Helm chart, actively maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, is built for cloud-native, scalable budgeting deployments on Kubernetes. With it, you gain:

* 🛠️ **Simple Deployment:** Helm makes installation and updates easy
* 🌱 **Community Contributions:** Benefit from a growing and active open-source community
* ⚙️ **Flexible Configurations:** Customize based on your infrastructure and workflows
* 🚀 **Reliable Operations:** Continuously tested and maintained for Kubernetes environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

actualbudget and the GitHub Community Charts project thrive on open-source collaboration. Whether you are a new user or an experienced contributor, getting involved is easy:

* 📚 Learn more in the [actualbudget chart docs](https://community-charts.github.io/docs/category/actualbudget)
* 🛠️ Contribute code or docs via [GitHub pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or issues on [GitHub Issues](https://github.com/community-charts/helm-charts/issues)
* 💡 Share ideas or feature requests via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being a part of the actualbudget journey. Together, we’re making budgeting open, accessible, and powerful—one Kubernetes deployment at a time.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-03-actualbudget-chart-version-1-8-3-released.md)


---

# actualbudget chart 1.8.4 now available

November 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **actualbudget Helm chart version 1.8.4**, now live as of November 3, 2025, and featuring the latest **application version 25.11.0**. This updated release continues our commitment to easy, reliable deployment of actualbudget on Kubernetes, with meaningful enhancements inspired by the open-source community.

<!-- -->

## What’s New in 1.8.4[​](#whats-new-in-184 "Direct link to What’s New in 1.8.4")

This version delivers an updated chart alongside the new actualbudget application version, improving performance and reliability:

* ✅ **Updated**: Bumped actualbudget/actual-server image to version 25.11.0
  <!-- -->
  * [Docker Hub - actual-server](https://hub.docker.com/r/actualbudget/actual-server)

To view the detailed changelog, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.4).

## Get Started with actualbudget on Kubernetes[​](#get-started-with-actualbudget-on-kubernetes "Direct link to Get Started with actualbudget on Kubernetes")

Looking to deploy version 1.8.4 in your environment? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/actualbudget) make it simple:

* Get up and running quickly with default settings.
* Learn how to tailor configurations for your specific needs.
* Follow best practices for production-grade deployments.

Visit the [official documentation](https://community-charts.github.io/docs/category/actualbudget) to begin your journey.

## Why Use the actualbudget Helm Chart?[​](#why-use-the-actualbudget-helm-chart "Direct link to Why Use the actualbudget Helm Chart?")

The official actualbudget Helm chart from [GitHub Community Charts](https://github.com/community-charts/helm-charts) is built with flexibility and reliability in mind. Here’s why teams choose it:

* 🚀 **Streamlined Helm experience**: Get set up with minimal overhead.
* 🌍 **Backed by Community**: Developed and maintained by passionate contributors.
* 🔧 **Highly customizable**: Supports a variety of workloads and infrastructure.
* 🛡️ **Stability-focused**: Verified in real-world Kubernetes environments.

Whether you're managing finances at home or supporting teams, our Helm chart helps actualbudget scale with you.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

actualbudget is powered by a growing open-source community. Whether you’re interested in contributing code, refining docs, or shaping features, we welcome your support!

Here’s how to get involved:

* 🔍 Dive into the [actualbudget chart documentation](https://community-charts.github.io/docs/category/actualbudget).
* 💡 Submit improvements or bug fixes with a [pull request](https://github.com/community-charts/helm-charts).
* 🐞 Found an issue? [Open a ticket](https://github.com/community-charts/helm-charts/issues).
* ✨ Got ideas? [Suggest features](https://github.com/community-charts/helm-charts/issues/new) we should consider next.

Thanks for being part of the actualbudget and Helm chart community—together, we're making Kubernetes deployments better for everyone.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-03-actualbudget-chart-version-1-8-4-released.md)


---

# actualbudget chart version 1.8.5 released

December 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **actualbudget Helm chart version 1.8.5**, officially available as of 2025-12-04! This update includes **application version 25.12.0**, offering important enhancements and valuable contributions from our vibrant open-source community.

<!-- -->

## Highlights of version 1.8.5[​](#highlights-of-version-185 "Direct link to Highlights of version 1.8.5")

The latest chart release introduces upgraded components and improved deployment capabilities for Kubernetes users. Here’s what’s new:

* 📦 **Updated**: actualbudget/actual-server Docker image upgraded to version 25.12.0
  <br />
  <!-- -->
  ➤ [View upstream image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

Review the full list of changes in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.5) on GitHub.

## Start deploying with the latest chart[​](#start-deploying-with-the-latest-chart "Direct link to Start deploying with the latest chart")

Looking to install or upgrade to version 1.8.5? Our [setup documentation](https://community-charts.github.io/docs/category/actualbudget) makes the process smooth and flexible, whether you're new or experienced. You'll find:

* Fast startup using default values
* Guidance for advanced configuration
* Best practices for production readiness

Everything you need to deploy actualbudget confidently is in the [official documentation](https://community-charts.github.io/docs/category/actualbudget).

## Why use the actualbudget Helm chart?[​](#why-use-the-actualbudget-helm-chart "Direct link to Why use the actualbudget Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the actualbudget chart helps teams run their finances app seamlessly in containerized environments.

Here’s why developers and ops teams trust this chart:

* ✅ **Simplicity**: Easy setup on any Kubernetes cluster
* 🤝 **Backed by the community**: Actively maintained and enriched by contributors
* ⚙️ **Adaptable**: Configure it to match your infrastructure needs
* 🔒 **Stable**: Verified configurations for reliable deployments on production systems

## Join our community of contributors[​](#join-our-community-of-contributors "Direct link to Join our community of contributors")

We believe in building together. The GitHub Community Charts project grows with input from users like you. Here’s how to participate:

* Read the [documentation](https://community-charts.github.io/docs/category/actualbudget) to understand the chart inside and out
* [Contribute code or improvements](https://github.com/community-charts/helm-charts) via pull requests
* [Report issues and bugs](https://github.com/community-charts/helm-charts/issues)
* [Suggest features](https://github.com/community-charts/helm-charts/issues/new) that would make this chart even better

Thank you for being part of the open-source journey. Together, we’re simplifying actualbudget deployments on Kubernetes!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-04-actualbudget-chart-version-1-8-5-released.md)


---

# Actualbudget Chart Version 1.8.8 Released

May 29, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **actualbudget Helm chart version 1.8.8** on May 29, 2026, featuring the **app version 26.5.2**. This update introduces a range of new features, enhancements, and community-driven improvements to make deploying actualbudget on Kubernetes even easier.

## What's New in the Actualbudget 1.8.8 Chart[​](#whats-new-in-the-actualbudget-188-chart "Direct link to What's New in the Actualbudget 1.8.8 Chart")

This release encompasses updates to both the Helm chart (version 1.8.8) and the underlying application (version 26.5.2). Here’s a snapshot of the changelog:

* **Changed**: Updated the actualbudget/actual-server image to version 26.5.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/actualbudget/actual-server)

For a comprehensive list of changes, please view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.8) on GitHub.

<!-- -->

## Getting Started with the Actualbudget 1.8.8 Chart[​](#getting-started-with-the-actualbudget-188-chart "Direct link to Getting Started with the Actualbudget 1.8.8 Chart")

Are you ready to deploy actualbudget 1.8.8? Check out our [installation guides](https://community-charts.github.io/docs/category/actualbudget) for clear, step-by-step instructions to help you begin, including:

* Quick installation with default configurations.
* Customizing settings to fit your environment.
* Best practices to ensure successful production deployments.

Visit the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) to explore all available options and get started deploying actualbudget today.

## Why Choose the Actualbudget Helm Chart?[​](#why-choose-the-actualbudget-helm-chart "Direct link to Why Choose the Actualbudget Helm Chart?")

The actualbudget Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is specifically designed to facilitate easy and reliable deployments of actualbudget on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy simplified installation and configuration.
* **Community-Driven**: Benefit from regular updates and improvements contributed by members of our community.
* **Flexibility**: Utilize configurable options tailored to diverse use cases.
* **Reliability**: Rely on a chart that has been thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we invite you to contribute! Whether you're fixing bugs, enhancing documentation, or proposing new features, here’s how you can be a part of our journey:

* **Explore the Chart**: Dive into the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) for detailed configuration options.
* **Contribute**: Share your changes by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your ideas for improvements through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting actualbudget and GitHub Community Charts. Together, let's make Kubernetes deployments simpler and more efficient!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-05-29-actualbudget-chart-version-1-8-8-released.md)


---

# actualbudget chart version 1.8.9 released

June 2, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **actualbudget Helm chart version 1.8.9** as of June 2, 2026, along with **app version 26.6.0**. This latest update introduces new features, enhancements, and improvements driven by our wonderful community, all designed to make deploying actualbudget on Kubernetes smoother and more efficient.

## What's New in actualbudget 1.8.9 chart[​](#whats-new-in-actualbudget-189-chart "Direct link to What's New in actualbudget 1.8.9 chart")

The 1.8.9 release includes significant updates to both the Helm chart and the application. Here’s a quick overview of what has changed:

* **Changed**: Updated the actualbudget/actual-server image version to 26.6.0
  <!-- -->
  * [View the Upstream Project](https://hub.docker.com/r/actualbudget/actual-server)

For a comprehensive list of changes, you can check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.9) on GitHub.

<!-- -->

## Getting Started with actualbudget 1.8.9 chart[​](#getting-started-with-actualbudget-189-chart "Direct link to Getting Started with actualbudget 1.8.9 chart")

Eager to deploy actualbudget 1.8.9? Our [installation guides](https://community-charts.github.io/docs/category/actualbudget) provide clear, step-by-step instructions to help you get set up, including:

* Quick installation with default configurations.
* Customizing settings tailored to your environment.
* Best practices for production deployments.

Explore all the available options and deploy actualbudget today by visiting the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget).

## Why Choose the actualbudget Helm Chart?[​](#why-choose-the-actualbudget-helm-chart "Direct link to Why Choose the actualbudget Helm Chart?")

The actualbudget Helm chart, proudly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to facilitate straightforward and dependable deployments on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy a simplified installation and configuration process.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our dedicated community.
* **Flexibility**: Take advantage of configurable options to meet a variety of use cases.
* **Reliability**: Count on our tested solutions for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

Your contributions can make a real difference! GitHub Community Charts is a collaborative project, and we invite you to be part of it. Whether you’re interested in fixing bugs, enhancing documentation, or proposing new features, here’s how you can get involved:

* **Explore the Chart**: Dive into the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) for detailed configuration information.
* **Contribute**: Feel free to submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you discover a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions for improvements through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your ongoing support of actualbudget and GitHub Community Charts. Together, let's continue to simplify Kubernetes deployments!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-02-actualbudget-chart-version-1-8-9-released.md)


---

# actualbudget chart version 1.9.0 released

June 20, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **actualbudget Helm chart version 1.9.0** on June 20, 2026, featuring **app version 26.6.0**. This latest update introduces enhanced functionalities and community-driven improvements, making it easier than ever to deploy actualbudget on Kubernetes.

## What's New in actualbudget 1.9.0 chart[​](#whats-new-in-actualbudget-190-chart "Direct link to What's New in actualbudget 1.9.0 chart")

This release includes significant updates to the Helm chart (version 1.9.0) alongside the underlying application (version 26.6.0). Here’s a sneak peek at the changes:

* **Added**: Optional image digest support for immutable image pulls
* **Fixed**: Corrected secret namespace to use the release namespace rather than an undefined value
* **Fixed**: Aligned schema default values with the actual values.yaml defaults
* **Fixed**: Corrected a typo in the supplementalGroups schema title
* **Fixed**: Adjusted the notContains test assertion on scalar fields to use isNull
* **Fixed**: Updated NOTES.txt to reflect configurable service port in port-forward instructions
* **Fixed**: Implemented @deprecated marker convention for the discoverUrl field
* **Fixed**: Enabled readOnlyRootFilesystem and added a built-in tmp emptyDir volume

For a comprehensive list of changes, please take a look at the [release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.9.0) on GitHub.

<!-- -->

## Getting Started with actualbudget 1.9.0 chart[​](#getting-started-with-actualbudget-190-chart "Direct link to Getting Started with actualbudget 1.9.0 chart")

Eager to deploy actualbudget 1.9.0? Our [installation guides](https://community-charts.github.io/docs/category/actualbudget) provide easy-to-follow instructions that include:

* Quick installation options with default settings.
* Customizing configurations to match your environment.
* Best practices for seamless production deployments.

Visit the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) to explore all available options and deploy actualbudget today.

## Why Choose the actualbudget Helm Chart?[​](#why-choose-the-actualbudget-helm-chart "Direct link to Why Choose the actualbudget Helm Chart?")

The actualbudget Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to provide a straightforward and reliable way to deploy actualbudget on Kubernetes. Here are some key benefits:

* **Ease of Use**: Simplified installation and configuration process.
* **Community-Driven**: Regular updates and enhancements from dedicated contributors.
* **Flexibility**: Numerous configurable options to meet various use cases.
* **Reliability**: Rigorously tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we welcome your contributions! Whether you're fixing bugs, enhancing documentation, or suggesting fresh features, here’s how you can get involved:

* **Explore the Chart**: Visit the [actualbudget documentation](https://community-charts.github.io/docs/category/actualbudget) for configuration details.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting actualbudget and GitHub Community Charts. Together, let’s continue simplifying Kubernetes deployments!

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-20-actualbudget-chart-version-1-9-0-released.md)


---

### 2026[​](#2026 "Direct link to 2026")

* [May 29](/blog/drone-chart-version-0.1.5-released.md)
  <!-- -->
  [ - ](/blog/drone-chart-version-0.1.5-released.md)
  <!-- -->
  [Exciting Release of Drone Chart Version 0.1.5](/blog/drone-chart-version-0.1.5-released.md)
* [May 29](/blog/actualbudget-chart-version-1.8.8-released.md)
  <!-- -->
  [ - ](/blog/actualbudget-chart-version-1.8.8-released.md)
  <!-- -->
  [Actualbudget Chart Version 1.8.8 Released](/blog/actualbudget-chart-version-1.8.8-released.md)
* [May 29](/blog/cloudflared-chart-version-2.2.8-released.md)
  <!-- -->
  [ - ](/blog/cloudflared-chart-version-2.2.8-released.md)
  <!-- -->
  [Cloudflared Chart Version 2.2.8 Released](/blog/cloudflared-chart-version-2.2.8-released.md)
* [May 29](/blog/outline-chart-version-0.7.4-released.md)
  <!-- -->
  [ - ](/blog/outline-chart-version-0.7.4-released.md)
  <!-- -->
  [Outline Chart Version 0.7.4 Released](/blog/outline-chart-version-0.7.4-released.md)
* [May 31](/blog/mlflow-chart-version-1.8.2-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.8.2-released.md)
  <!-- -->
  [mlflow chart version 1.8.2 released](/blog/mlflow-chart-version-1.8.2-released.md)
* [May 31](/blog/mlflow-chart-version-1.8.3-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.8.3-released.md)
  <!-- -->
  [Mlflow Chart Version 1.8.3 Released](/blog/mlflow-chart-version-1.8.3-released.md)
* [June 2](/blog/mlflow-chart-version-1.8.4-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.8.4-released.md)
  <!-- -->
  [mlflow chart version 1.8.4 launched](/blog/mlflow-chart-version-1.8.4-released.md)
* [June 2](/blog/outline-chart-version-0.7.5-released.md)
  <!-- -->
  [ - ](/blog/outline-chart-version-0.7.5-released.md)
  <!-- -->
  [Outline Chart Version 0.7.5 Released](/blog/outline-chart-version-0.7.5-released.md)
* [June 2](/blog/actualbudget-chart-version-1.8.9-released.md)
  <!-- -->
  [ - ](/blog/actualbudget-chart-version-1.8.9-released.md)
  <!-- -->
  [actualbudget chart version 1.8.9 released](/blog/actualbudget-chart-version-1.8.9-released.md)
* [June 2](/blog/n8n-chart-version-1.16.45-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.16.45-released.md)
  <!-- -->
  [n8n chart version 1.16.45 released](/blog/n8n-chart-version-1.16.45-released.md)
* [June 2](/blog/outline-chart-version-0.8.0-released.md)
  <!-- -->
  [ - ](/blog/outline-chart-version-0.8.0-released.md)
  <!-- -->
  [Outline Chart Version 0.8.0 Released](/blog/outline-chart-version-0.8.0-released.md)
* [June 2](/blog/n8n-chart-version-1.16.46-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.16.46-released.md)
  <!-- -->
  [n8n Chart Version 1.16.46 Released](/blog/n8n-chart-version-1.16.46-released.md)
* [June 2](/blog/mlflow-chart-version-1.8.5-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.8.5-released.md)
  <!-- -->
  [MLflow Chart Version 1.8.5 Released](/blog/mlflow-chart-version-1.8.5-released.md)
* [June 5](/blog/n8n-chart-version-1.16.47-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.16.47-released.md)
  <!-- -->
  [n8n chart version 1.16.47 released](/blog/n8n-chart-version-1.16.47-released.md)
* [June 5](/blog/n8n-chart-version-1.16.48-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.16.48-released.md)
  <!-- -->
  [n8n chart version 1.16.48 released](/blog/n8n-chart-version-1.16.48-released.md)
* [June 5](/blog/n8n-chart-version-1.16.49-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.16.49-released.md)
  <!-- -->
  [n8n chart version 1.16.49 released](/blog/n8n-chart-version-1.16.49-released.md)
* [June 5](/blog/n8n-chart-version-1.17.0-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.17.0-released.md)
  <!-- -->
  [n8n chart version 1.17.0 released](/blog/n8n-chart-version-1.17.0-released.md)
* [June 6](/blog/n8n-chart-version-1.17.1-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.17.1-released.md)
  <!-- -->
  [n8n chart version 1.17.1 released](/blog/n8n-chart-version-1.17.1-released.md)
* [June 7](/blog/n8n-chart-version-1.18.0-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.18.0-released.md)
  <!-- -->
  [n8n chart version 1.18.0 released](/blog/n8n-chart-version-1.18.0-released.md)
* [June 7](/blog/outline-chart-version-0.8.1-released.md)
  <!-- -->
  [ - ](/blog/outline-chart-version-0.8.1-released.md)
  <!-- -->
  [Outline Chart Version 0.8.1 Released](/blog/outline-chart-version-0.8.1-released.md)
* [June 7](/blog/n8n-chart-version-1.19.0-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.19.0-released.md)
  <!-- -->
  [n8n chart version 1.19.0 released](/blog/n8n-chart-version-1.19.0-released.md)
* [June 7](/blog/n8n-chart-version-1.20.0-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.20.0-released.md)
  <!-- -->
  [n8n chart version 1.20.0 released](/blog/n8n-chart-version-1.20.0-released.md)
* [June 7](/blog/n8n-chart-version-1.21.0-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.21.0-released.md)
  <!-- -->
  [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md)
* [June 7](/blog/n8n-chart-version-1.22.0-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.0-released.md)
  <!-- -->
  [n8n chart version 1.22.0 released](/blog/n8n-chart-version-1.22.0-released.md)
* [June 10](/blog/n8n-chart-version-1.22.1-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.1-released.md)
  <!-- -->
  [n8n chart version 1.22.1 released](/blog/n8n-chart-version-1.22.1-released.md)
* [June 10](/blog/cloudflared-chart-version-2.2.9-released.md)
  <!-- -->
  [ - ](/blog/cloudflared-chart-version-2.2.9-released.md)
  <!-- -->
  [Cloudflared Chart Version 2.2.9 Released](/blog/cloudflared-chart-version-2.2.9-released.md)
* [June 11](/blog/n8n-chart-version-1.22.2-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.2-released.md)
  <!-- -->
  [n8n chart version 1.22.2 released](/blog/n8n-chart-version-1.22.2-released.md)
* [June 17](/blog/n8n-chart-version-1.22.3-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.3-released.md)
  <!-- -->
  [n8n chart version 1.22.3 released](/blog/n8n-chart-version-1.22.3-released.md)
* [June 18](/blog/n8n-chart-version-1.22.4-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.4-released.md)
  <!-- -->
  [n8n chart version 1.22.4 released](/blog/n8n-chart-version-1.22.4-released.md)
* [June 18](/blog/mlflow-chart-version-1.8.6-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.8.6-released.md)
  <!-- -->
  [mlflow chart version 1.8.6 released](/blog/mlflow-chart-version-1.8.6-released.md)
* [June 19](/blog/n8n-chart-version-1.22.5-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.5-released.md)
  <!-- -->
  [n8n chart version 1.22.5 released](/blog/n8n-chart-version-1.22.5-released.md)
* [June 19](/blog/cloudflared-chart-version-2.2.10-released.md)
  <!-- -->
  [ - ](/blog/cloudflared-chart-version-2.2.10-released.md)
  <!-- -->
  [Cloudflared Chart Version 2.2.10 Released](/blog/cloudflared-chart-version-2.2.10-released.md)
* [June 19](/blog/n8n-chart-version-1.22.6-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.6-released.md)
  <!-- -->
  [n8n chart version 1.22.6 released](/blog/n8n-chart-version-1.22.6-released.md)
* [June 19](/blog/n8n-chart-version-1.22.7-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.22.7-released.md)
  <!-- -->
  [n8n chart version 1.22.7 released](/blog/n8n-chart-version-1.22.7-released.md)
* [June 19](/blog/n8n-chart-version-1.23.0-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.23.0-released.md)
  <!-- -->
  [n8n chart version 1.23.0 released](/blog/n8n-chart-version-1.23.0-released.md)
* [June 19](/blog/n8n-chart-version-1.23.1-released.md)
  <!-- -->
  [ - ](/blog/n8n-chart-version-1.23.1-released.md)
  <!-- -->
  [n8n chart version 1.23.1 released](/blog/n8n-chart-version-1.23.1-released.md)
* [June 20](/blog/mlflow-chart-version-1.9.0-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.9.0-released.md)
  <!-- -->
  [mlflow Helm Chart Version 1.9.0 Released](/blog/mlflow-chart-version-1.9.0-released.md)
* [June 20](/blog/actualbudget-chart-version-1.9.0-released.md)
  <!-- -->
  [ - ](/blog/actualbudget-chart-version-1.9.0-released.md)
  <!-- -->
  [actualbudget chart version 1.9.0 released](/blog/actualbudget-chart-version-1.9.0-released.md)
* [June 20](/blog/outline-chart-version-0.9.0-released.md)
  <!-- -->
  [ - ](/blog/outline-chart-version-0.9.0-released.md)
  <!-- -->
  [outline chart version 0.9.0 released](/blog/outline-chart-version-0.9.0-released.md)
* [June 21](/blog/mlflow-chart-version-1.10.0-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.10.0-released.md)
  <!-- -->
  [mlflow chart version 1.10.0 released](/blog/mlflow-chart-version-1.10.0-released.md)
* [June 21](/blog/mlflow-chart-version-1.11.0-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.11.0-released.md)
  <!-- -->
  [mlflow chart version 1.11.0 released](/blog/mlflow-chart-version-1.11.0-released.md)
* [June 21](/blog/mlflow-chart-version-1.11.1-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.11.1-released.md)
  <!-- -->
  [mlflow chart version 1.11.1 released](/blog/mlflow-chart-version-1.11.1-released.md)
* [June 21](/blog/mlflow-chart-version-1.11.2-released.md)
  <!-- -->
  [ - ](/blog/mlflow-chart-version-1.11.2-released.md)
  <!-- -->
  [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md)


---

# Authors

* [![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

  ## [Burak Ince](/blog/authors/burakince.md)

  159

  Software Developer

  [](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")


---

## [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md)

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **mlflow Helm chart version 1.11.2** on June 21, 2026, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements to streamline the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.2 chart[​](#whats-new-in-mlflow-1112-chart "Direct link to What's New in mlflow 1.11.2 chart")

This latest version includes important updates to the Helm chart (version 1.11.2) alongside the underlying application (version 3.14.0). Here’s a brief overview of the enhancements:

* **Changed**: Updated dbchecker image version to 1.38.0
  <!-- -->
  * [dbchecker](https://hub.docker.com/r/library/busybox)
* **Changed**: Updated ini-file-initializer image version to 1.38.0
  <!-- -->
  * [ini-file-initializer](https://hub.docker.com/r/library/busybox)

For a comprehensive list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.2) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.11.2-released.md)


---

## [cloudflared chart version 2.1.3 released](/blog/cloudflared-chart-version-2.1.3-released.md)

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest cloudflared Helm chart—version 2.1.3—officially available as of September 18, 2025. This update includes app version 2025.9.0 and brings helpful enhancements designed to simplify your Kubernetes deployments.

## What’s new in cloudflared 2.1.3[​](#whats-new-in-cloudflared-213 "Direct link to What’s new in cloudflared 2.1.3")

Version 2.1.3 focuses on staying up to date with upstream developments and ensuring a smoother deployment experience. Key changes include:

* ✅ Updated container image to cloudflare/cloudflared version 2025.9.0
  <!-- -->
  * [Check the image on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

Review the full changelog in the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.3) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.1.3-released.md)


---

## [Outline Helm Chart 0.6.3 Released with App Version 0.87.1](/blog/outline-chart-version-0.6.3-released.md)

September 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the Outline Helm chart—version 0.6.3—available as of 2025-09-01. This release includes app version 0.87.1 and brings enhancements, updated dependencies, and valuable contributions from the open-source community.

## What’s New in 0.6.3[​](#whats-new-in-063 "Direct link to What’s New in 0.6.3")

This update refreshes both the Outline application and its supporting Helm chart, helping you streamline deployments on Kubernetes.

Here’s what’s included in this version:

* 🔄 Updated to use the latest Outline Docker image (v0.87.1)
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🧠 Redis dependency upgraded from 22.0.1 to 22.0.7
  <br />
  <!-- -->
  → [View Redis Helm Chart](https://artifacthub.io/packages/helm/bitnami/redis)
* 🐘 PostgreSQL dependency updated from 16.7.24 to 16.7.27
  <br />
  <!-- -->
  → [View PostgreSQL Helm Chart](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.3).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.6.3-released.md)


---

## [pypiserver chart version 0.1.8 released](/blog/pypiserver-chart-version-0.1.8-released.md)

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of our Helm chart for pypiserver — version 0.1.8 — now available as of August 19, 2025. This release delivers support for app version **v2.4.0**, bringing new features and meaningful improvements to make your Helm-based deployments even more seamless.

**Tags:**

* [PyPI Server](/blog/tags/pypiserver.md "Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/pypiserver-chart-version-0.1.8-released.md)


---

## [n8n chart version 1.13.8 released](/blog/n8n-chart-version-1.13.8-released.md)

August 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest stable version of the **n8n Helm chart — version 1.13.8**, published on August 4, 2025! This release includes **n8n app version 1.105.2**, with valuable upgrades and refinements to improve your workflow automation experience on Kubernetes.

## What’s new in Helm chart 1.13.8?[​](#whats-new-in-helm-chart-1138 "Direct link to What’s new in Helm chart 1.13.8?")

In this version, both the chart and its dependencies have been refreshed to deliver a more secure and reliable deployment experience.

* ✅ **Updated**: n8n image version is now 1.105.2
  <br />
  <!-- -->
  → Check out the upstream repo: [n8n GitHub](https://github.com/n8n-io/n8n)
* 🔁 **Updated**: Redis dependency upgrade from 21.2.13 to 21.2.14
  <br />
  <!-- -->
  → View it on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For a complete breakdown, see the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.13.8-released.md)


---

## [mlflow chart version 1.3.2 released](/blog/mlflow-chart-version-1.3.2-released.md)

July 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **mlflow Helm chart version 1.3.2** is now available as of **2025-07-24**, bringing you **mlflow app version 3.1.4**. This release delivers usability enhancements and community-driven improvements to make deploying mlflow on Kubernetes even smoother and more efficient.

## What’s New in Helm Chart 1.3.2[​](#whats-new-in-helm-chart-132 "Direct link to What’s New in Helm Chart 1.3.2")

With this release, both the Helm chart and the application itself have been upgraded to offer better functionality and integration:

* 🚀 **Updated**: Container image upgraded to `burakince/mlflow:3.1.4`
  <br />
  <!-- -->
  → View on [Docker Hub](https://hub.docker.com/r/burakince/mlflow)

To see all technical changes, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.2).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.3.2-released.md)


---

## [outline chart version 0.4.1 released](/blog/outline-chart-version-0.4.1-released.md)

July 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm Chart version 0.4.1**, available as of July 4, 2025. This update delivers important improvements and refreshed dependencies to make deploying Outline on your Kubernetes clusters smoother and more efficient.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.4.1-released.md)


---

## [n8n chart version 1.10.0 now available](/blog/n8n-chart-version-1.10.0-released.md)

June 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **n8n Helm chart version 1.10.0**, launched on 2025-06-27 and powered by **application version 1.99.1**. This update introduces new features, usability enhancements, and community-requested improvements that make deploying n8n on Kubernetes easier and more flexible than ever.

## What’s New in Version 1.10.0[​](#whats-new-in-version-1100 "Direct link to What’s New in Version 1.10.0")

This release includes updates to both the Helm chart and the underlying application. Highlights from the changelog include:

* ✅ **Form Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/147)
* ✅ **MCP Server Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/148)
* ✅ **New flag introduced to enable or disable service as needed**

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.10.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.10.0-released.md)


---

## [n8n chart version 1.22.6 released](/blog/n8n-chart-version-1.22.6-released.md)

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the arrival of **n8n Helm chart version 1.22.6** on 2026-06-19, which includes the latest **app version 2.26.7**. This update features a variety of enhancements and community-driven improvements aimed at simplifying the deployment of n8n on Kubernetes.

## What's New in n8n 1.22.6 Chart[​](#whats-new-in-n8n-1226-chart "Direct link to What's New in n8n 1.22.6 Chart")

This release encompasses updates for both the Helm chart (version 1.22.6) and the underlying application (version 2.26.7). Here’s a glimpse into the changes made:

* **Changed**: Updated the n8nio/n8n image version to 2.26.7
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency postgresql from 18.7.5 to 18.7.6
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of the changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.6) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.22.6-released.md)


---

## [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md)

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce that **n8n Helm chart version 1.21.0** has been released as of 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and community-driven improvements designed to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.21.0 chart[​](#whats-new-in-n8n-1210-chart "Direct link to What's New in n8n 1.21.0 chart")

This release brings important updates to both the Helm chart (version 1.21.0) and the underlying application (version 2.23.4). Here are some highlights from the changelog:

* **Added**: Support for extra manifests through `extraManifests` and `extraTemplateManifests` values.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.21.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.21.0-released.md)


---

## [MLflow Chart Version 1.8.5 Released](/blog/mlflow-chart-version-1.8.5-released.md)

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **MLflow Helm chart version 1.8.5** on June 2, 2026, featuring **app version 3.13.0**. This update brings a wealth of new features, enhancements, and community-driven improvements designed to streamline your MLflow deployment on Kubernetes.

## What's New in MLflow 1.8.5 Chart[​](#whats-new-in-mlflow-185-chart "Direct link to What's New in MLflow 1.8.5 Chart")

This release includes updates to both the Helm chart (version 1.8.5) and the underlying application (version 3.13.0). Here are some of the key changes:

* **Fixed**: Resolved broken screenshot URL(s) in the MLflow chart.

For a comprehensive list of changes, you can view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.5) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.5-released.md)


---

## [Cloudflared Chart Version 2.2.8 Released](/blog/cloudflared-chart-version-2.2.8-released.md)

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **cloudflared Helm chart version 2.2.8** on May 29, 2026, featuring **app version 2026.5.2**. This update introduces new features and community-driven enhancements to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.8 Chart[​](#whats-new-in-cloudflared-228-chart "Direct link to What's New in Cloudflared 2.2.8 Chart")

This release not only updates the Helm chart (version 2.2.8) but also the underlying application (version 2026.5.2). Here are the key changes:

* **Changed**: Updated cloudflare/cloudflared image version to 2026.5.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete breakdown of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.8) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.2.8-released.md)


---

## [n8n chart version 1.16.8 released](/blog/n8n-chart-version-1.16.8-released.md)

December 5, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.16.8**, is now available as of December 5, 2025. This release packages **app version 1.122.5** and includes key updates to streamline your workflow automation deployments on Kubernetes.

## What’s New in Version 1.16.8[​](#whats-new-in-version-1168 "Direct link to What’s New in Version 1.16.8")

This update brings improvements to the Helm chart along with the bump to the latest n8n app release. Here's what’s changed:

* 🛠️ **Updated**: n8nio/n8n Docker image upgraded to version 1.122.5
  <br />
  <!-- -->
  → [Upstream Repository](https://github.com/n8n-io/n8n)

Check out the full changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.16.8-released.md)


---

## [mlflow chart version 1.8.0 released](/blog/mlflow-chart-version-1.8.0-released.md)

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.8.0**, available as of 2025-11-08. This release includes the latest **app version 3.6.0** and brings valuable improvements focused on performance, customization, and Kubernetes-native deployments.

## What’s New in mlflow Helm chart 1.8.0[​](#whats-new-in-mlflow-helm-chart-180 "Direct link to What’s New in mlflow Helm chart 1.8.0")

This version of the chart includes important updates designed to offer greater flexibility when running mlflow on Kubernetes. Highlights include:

* ✅ **Resource Configuration for Init Containers**: You can now define compute resources for the `dbchecker` and `ini-file-initializer` init containers.
  <br />
  <!-- -->
  See the discussion on [GitHub Issue #265](https://github.com/community-charts/helm-charts/issues/265)

These changes allow for more efficient use of resources and better alignment with production-grade deployments.

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.0).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.0-released.md)


---

## [Outline chart update 0.7.1 with app version 1.0.0](/blog/outline-chart-version-0.7.1-released.md)

October 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.7.1**, officially available as of October 27, 2025. This latest version includes **app version 1.0.0**, delivering key updates, improved stability, and valuable contributions from our open-source community.

Whether you're running Outline in production or exploring it for the first time, this release brings smoother deployment and better integration with your Kubernetes environment.

## What’s new in version 0.7.1[​](#whats-new-in-version-071 "Direct link to What’s new in version 0.7.1")

This update improves both the Helm chart and important dependencies, aligning with the latest enhancements from upstream projects:

* ✅ Upgraded Outline Docker image to **v1.0.0**
  <br />
  <!-- -->
  ↳ [View upstream image](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Updated Redis dependency from 22.0.7 to **23.2.1**
  <br />
  <!-- -->
  ↳ [Redis Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Updated PostgreSQL dependency from 16.7.27 to **18.1.1**
  <br />
  <!-- -->
  ↳ [PostgreSQL Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

See the full changelog in the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.1).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.7.1-released.md)


---

## [actualbudget chart version 1.8.3 released](/blog/actualbudget-chart-version-1.8.3-released.md)

October 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the 🧾 **actualbudget Helm chart (v1.8.3)** is now available, featuring the newly updated **app version 25.10.0**, as of 2025-10-03. This version continues our focus on improving the experience of deploying actualbudget on Kubernetes with enhanced support, better performance, and key community contributions.

## What’s New in actualbudget 1.8.3[​](#whats-new-in-actualbudget-183 "Direct link to What’s New in actualbudget 1.8.3")

This release includes both chart and application updates to keep your deployments modern and efficient:

* ✅ **Updated:** actualbudget/actual-server image upgraded to version 25.10.0
  <br />
  <!-- -->
  ↳ View the [Docker image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For a full list of changes and enhancements, check out the official [v1.8.3 release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.3) on GitHub.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/actualbudget-chart-version-1.8.3-released.md)


---

# cloudflared chart version 2.0.8 now available

July 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **cloudflared Helm chart version 2.0.8**, published on July 4th, 2025! This update brings performance enhancements, added flexibility, and contributions from our open-source community—all designed to make deploying cloudflared on Kubernetes even easier.

<!-- -->

## What's New in 2.0.8[​](#whats-new-in-208 "Direct link to What's New in 2.0.8")

The latest version updates the Helm chart to **2.0.8**, which includes:

* 🔄 **Updated**: Bumped the cloudflare/cloudflared image to `2025.7.0`
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

📝 For a full overview of changes, take a look at the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.0.8).

## Start Using the cloudflared Helm Chart[​](#start-using-the-cloudflared-helm-chart "Direct link to Start Using the cloudflared Helm Chart")

Getting started with the 2.0.8 version of the chart is simple. Our [cloudflared installation guide](https://community-charts.github.io/docs/category/cloudflared) walks you through:

* Fast installation using defaults
* Advanced configuration to meet custom requirements
* Tips for production-ready Kubernetes deployments

Ready to get started? [Dive into the docs](https://community-charts.github.io/docs/category/cloudflared).

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

Maintained by the [GitHub Community Charts project](https://github.com/community-charts/helm-charts), the cloudflared Helm chart is a trusted, community-supported solution for Kubernetes users. Here’s what makes it stand out:

* 🚀 **Quick to Deploy**: Streamlined setup for rapid implementation
* 🛠 **Community-Powered**: Evolving continuously with help from contributors
* ⚙ **Highly Configurable**: Adaptable to any infrastructure or use case
* 💡 **Production-Ready**: Tested for resilience and scalability in Kubernetes environments

Whether you're running on AWS, Azure, or a private cloud cluster, this chart helps deliver secure tunneling with ease.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

This project thrives thanks to an active and passionate open-source community. Here’s how you can get involved:

* ✏️ Improve the chart: Review and enhance the [documentation](https://community-charts.github.io/docs/category/cloudflared)
* 🤝 Submit fixes or features: Visit our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or issues: Use our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💬 Request new features: Share your ideas to help shape the roadmap

Thanks for supporting cloudflared and the Helm charts community. Together, let’s make secure Kubernetes deployments simple and scalable!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-04-cloudflared-chart-version-2-0-8-released.md)


---

# cloudflared chart version 2.0.9 released

July 16, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce that the latest release of the **cloudflared Helm chart (v2.0.9)** is now available, officially released on **July 16, 2025**. This version packages **cloudflared app version 2025.7.0**, bringing improved stability and enhanced usability for your Kubernetes deployments.

<!-- -->

## What’s New in v2.0.9[​](#whats-new-in-v209 "Direct link to What’s New in v2.0.9")

This update includes some important improvements:

* 🛠️ **Enhanced ingress schema definition** for better flexibility and configuration management.

You can view the full changelog and technical notes in the [official release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.0.9).

## Getting Started with cloudflared 2.0.9[​](#getting-started-with-cloudflared-209 "Direct link to Getting Started with cloudflared 2.0.9")

Looking to install or upgrade? Our updated [installation guides](https://community-charts.github.io/docs/category/cloudflared) walk you through everything you need:

* Simple, one-line installation using defaults.
* Tips to tailor configurations to your environment.
* Suggestions for secure and reliable production setups.

Explore the complete documentation to make the most of this release.

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, this chart helps you deploy cloudflared reliably on Kubernetes. With each version, we aim for:

* ⚙️ **Simplicity** – Get started quickly with minimal setup.
* 🤝 **Community collaboration** – Built and improved with feedback from developers and operators like you.
* 🔧 **Customization** – Tweak deployments to fit your exact use case.
* ✅ **Stability** – Tested and ready for Kubernetes production environments.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The success of the cloudflared chart is powered by an amazing open-source community. We'd love your help making it even better!

* 📚 Learn more in the [documentation](https://community-charts.github.io/docs/category/cloudflared).
* 👨‍💻 Contribute via pull requests on our [GitHub](https://github.com/community-charts/helm-charts).
* 🐞 Report bugs or ideas on the [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 🌟 Suggest new features to help improve the chart for everyone.

Thanks for being part of this journey. Let’s keep building a better Kubernetes experience—together!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-16-cloudflared-chart-version-2-0-9-released.md)


---

# cloudflared chart version 2.1.0 released

August 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **cloudflared Helm chart version 2.1.0**, officially available as of August 3, 2025! This update includes **app version 2025.7.0** and brings several meaningful enhancements designed to improve deployment flexibility and align with community needs.

## What’s New in Version 2.1.0[​](#whats-new-in-version-210 "Direct link to What’s New in Version 2.1.0")

chart version 2.1.0 introduces focused improvements that make running cloudflared in your Kubernetes clusters even more seamless. Here's what's been added:

* ✅ **New support** for referencing existing Kubernetes secrets for JSON credential files and PEM certificate files used by cloudflared tunnels.

These new capabilities enhance secret management, making production deployments more secure and configuration more flexible.

Check out the full changelog in the official [GitHub release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.0).

<!-- -->

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Ready to upgrade or install cloudflared 2.1.0? Head over to our step-by-step [installation guide](https://community-charts.github.io/docs/category/cloudflared), which covers everything from basic deployments to advanced configurations:

* 🚀 Quick setup using default values
* 🔧 Custom configurations for different environments
* 🛡️ Best practices for production readiness

You’ll find comprehensive instructions and tips to get cloudflared up and running quickly and securely.

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

Developed and maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the cloudflared Helm chart is a reliable solution for running Cloudflare Tunnel agents on Kubernetes. Its benefits include:

* 📦 **Streamlined deployment** with Helm on Kubernetes
* 🌐 **Flexible configuration** options for various workloads
* 🤝 **Backed by the community** with regular updates and contributions
* 🔁 **Actively maintained** with new features based on real user feedback

This release continues the community’s mission of making cloud-native development more accessible and secure.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’d love your help making the cloudflared chart even better! Whether you’re looking to contribute code, report a bug, or suggest improvements, there are plenty of ways to get involved:

* 📚 Review the [documentation](https://community-charts.github.io/docs/category/cloudflared) to understand available options
* 🛠️ Submit improvements via [pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Report issues or bugs on our [GitHub issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new ideas through [feature requests](https://github.com/community-charts/helm-charts/issues/new)

Thank you to everyone who contributes and supports the project — your involvement drives every release forward.

Let’s keep making Kubernetes deployments easier, together!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-03-cloudflared-chart-version-2-1-0-released.md)


---

# cloudflared chart version 2.1.1 released

August 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the official release of the **cloudflared Helm chart version 2.1.1**, published on **August 8, 2025**, and featuring the latest **application version 2025.8.0**. This update introduces a refreshed container image and builds on community contributions to improve deployment in Kubernetes environments.

## What’s New in cloudflared 2.1.1[​](#whats-new-in-cloudflared-211 "Direct link to What’s New in cloudflared 2.1.1")

Chart version 2.1.1 includes important enhancements to streamline your cloudflared setup. Here’s what’s changed:

* ✅ **Updated Image**: Upgraded to `cloudflare/cloudflared:2025.8.0`
  <br />
  <!-- -->
  🔗 [View on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete list of updates and technical details, check out the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.1) on GitHub.

<!-- -->

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Deploying cloudflared 2.1.1 is faster and easier than ever. Follow our [step-by-step installation guides](https://community-charts.github.io/docs/category/cloudflared) to get up and running with:

* Quick setup using default values
* Advanced customizations to match your use case
* Tips and best practices for production environments

Head over to the [official documentation](https://community-charts.github.io/docs/category/cloudflared) to start your deployment journey.

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

The cloudflared Helm chart, actively maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), offers a reliable and flexible way to run cloudflared on Kubernetes. Here’s what sets it apart:

* ⚙️ **Simple Setup**: Get started quickly with easy-to-follow configurations
* 👥 **Backed by the Community**: Developed and improved by contributors like you
* 🔧 **Highly Configurable**: Tweak it to match your environment and preferences
* 🔐 **Production-Ready**: Built and tested for Kubernetes resilience

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We believe in open collaboration and welcome your involvement! Whether you're a developer, ops engineer, or Kubernetes enthusiast, there are many ways to contribute:

* 📄 Explore the [documentation](https://community-charts.github.io/docs/category/cloudflared) for advanced configuration tips
* 🛠️ Contribute code or improvements via [pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Found a problem? [Report a bug](https://github.com/community-charts/helm-charts/issues)
* 💡 Have an idea? [Request a feature](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the cloudflared community. Your feedback, testing, and contributions help us build better tools for everyone deploying on Kubernetes.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-08-cloudflared-chart-version-2-1-1-released.md)


---

# cloudflared chart version 2.1.2 released

August 22, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the **cloudflared Helm chart—v2.1.2**—is now available as of August 22, 2025! This release includes the updated **cloudflared app version 2025.8.1**, bringing feature improvements and refined stability for Kubernetes-based deployments.

## What’s New in v2.1.2[​](#whats-new-in-v212 "Direct link to What’s New in v2.1.2")

With chart version 2.1.2, you’ll find updated components and helpful enhancements designed with the community in mind:

* ✅ **Image Update**: Upgraded to `cloudflare/cloudflared:2025.8.1`
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

Discover the full list of updates by visiting the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.2) on GitHub.

<!-- -->

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Getting up and running with cloudflared 2.1.2 is simple. Whether you're performing a fresh deployment or upgrading an existing setup, our documentation has you covered:

* 📦 Easy install with default settings
* 🔧 Options to customize for your environment
* 🛡️ Production-ready best practices

👉 Visit the official [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to learn how to configure and deploy it today.

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

Developed and maintained by the open-source [Community Charts team](https://github.com/community-charts/helm-charts), this Helm chart offers a robust, production-ready solution for running cloudflared on Kubernetes:

* 🧩 **Simplicity**: Install and manage with ease via Helm
* 🌍 **Community-led**: Powered by contributions from users around the world
* 🛠️ **Highly Configurable**: Designed to fit diverse cloud-native setups
* 🔁 **Continuously Improved**: Frequently updated with upstream changes and refinements

## Join the Community[​](#join-the-community "Direct link to Join the Community")

cloudflared Helm is driven by a passionate open-source community—and you’re welcome to be a part of it! Here’s how you can get involved:

* ✅ Learn more in our [chart documentation](https://community-charts.github.io/docs/category/cloudflared)
* 🔧 Contribute on [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report issues via the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features or improvements

Thanks for being part of the journey—let’s keep making Kubernetes deployments more powerful, together.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-22-cloudflared-chart-version-2-1-2-released.md)


---

# cloudflared chart version 2.1.3 released

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest cloudflared Helm chart—version 2.1.3—officially available as of September 18, 2025. This update includes app version 2025.9.0 and brings helpful enhancements designed to simplify your Kubernetes deployments.

## What’s new in cloudflared 2.1.3[​](#whats-new-in-cloudflared-213 "Direct link to What’s new in cloudflared 2.1.3")

Version 2.1.3 focuses on staying up to date with upstream developments and ensuring a smoother deployment experience. Key changes include:

* ✅ Updated container image to cloudflare/cloudflared version 2025.9.0
  <!-- -->
  * [Check the image on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

Review the full changelog in the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.3) on GitHub.

<!-- -->

## How to get started with cloudflared 2.1.3[​](#how-to-get-started-with-cloudflared-213 "Direct link to How to get started with cloudflared 2.1.3")

Deploying cloudflared with Helm is easier than ever. Our [installation guide](https://community-charts.github.io/docs/category/cloudflared) walks you through:

* Quick setup for testing or development environments
* Configuration options for custom deployments
* Recommendations for production-grade setups

Visit the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to explore available values and customizations.

## Why use the cloudflared Helm chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why use the cloudflared Helm chart?")

Maintained by the open-source community via [GitHub Community Charts](https://github.com/community-charts/helm-charts), the cloudflared Helm chart offers:

* 🛠️ Easy installation and configuration on Kubernetes
* 🙌 Contributions from a growing group of community members
* 🔧 Flexible settings to support a variety of use cases
* 🔒 Secure and stable performance aligned with best DevOps practices

## Join the community[​](#join-the-community "Direct link to Join the community")

cloudflared’s success relies on the contributions of its users. Whether you want to report a bug, enhance documentation, or suggest new features, here’s how to get involved:

* 📖 Learn more with our [cloudflared docs](https://community-charts.github.io/docs/category/cloudflared)
* 🔧 Contribute code via [pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Report issues or bugs through our [GitHub issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Propose new ideas for improvement

Thank you for being part of the cloudflared and Kubernetes open-source journey. We look forward to building more together!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-18-cloudflared-chart-version-2-1-3-released.md)


---

# cloudflared chart version 2.2.0 released

September 20, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to announce the latest release of the **cloudflared Helm chart version 2.2.0**, featuring **application version 2025.9.0**, officially available as of 2025-09-20. This update brings important enhancements and community-driven improvements to help you deploy cloudflared more effectively on Kubernetes.

## What’s New in cloudflared 2.2.0[​](#whats-new-in-cloudflared-220 "Direct link to What’s New in cloudflared 2.2.0")

This release includes several meaningful changes in both the Helm chart (v2.2.0) and the application (v2025.9.0):

* ➖ **Security Enhanced**: The NET\_RAW capability has been removed from the default security context, helping to reduce unnecessary permissions.
* 🔧 **Configuration Improvement**: The TUNNEL\_ORIGIN\_CERT environment variable is now consistently set with the correct certificate file path.

These updates improve security and reliability while simplifying configuration.

Read the full list of changes in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.0).

<!-- -->

## Get Started with cloudflared 2.2.0[​](#get-started-with-cloudflared-220 "Direct link to Get Started with cloudflared 2.2.0")

Eager to upgrade or deploy for the first time? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/cloudflared) walk you through every step, including:

* Quick start using default setup.
* Customizing values to match your environment.
* Production-ready deployment recommendations.

Visit the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to get up and running quickly.

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the cloudflared chart provides an easy, flexible, and secure way to deploy cloudflared in Kubernetes environments. Benefits include:

* 🧩 **Simple Setup**: Deploy with minimal effort using Helm.
* 🤝 **Community-Powered**: Always improving with help from contributors around the world.
* 🎛️ **Highly Configurable**: Tailor it to suit your Kubernetes setup.
* 🔄 **Robust and Tested**: Built for stability in production-grade clusters.

## Get Involved and Contribute[​](#get-involved-and-contribute "Direct link to Get Involved and Contribute")

cloudflared is an open-source project, and your input matters. Join our growing community in shaping the evolution of the Helm chart. Here's how you can participate:

* 📘 Explore the [documentation](https://community-charts.github.io/docs/category/cloudflared) to understand all configuration options.
* 🛠️ Contribute via pull requests on our [GitHub repo](https://github.com/community-charts/helm-charts).
* 🐞 Report issues or bugs [right here](https://github.com/community-charts/helm-charts/issues).
* 💡 Suggest new features or improvements through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being part of the growing cloudflared and Kubernetes community. Together, we're making open-source deployment more powerful and accessible!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-20-cloudflared-chart-version-2-2-0-released.md)


---

# cloudflared chart version 2.2.1 released

September 22, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the latest version of the **cloudflared Helm chart (v2.2.1)** is now available as of September 22, 2025. This release includes **application version 2025.9.1** and introduces updated components and refinements guided by valuable community feedback.

## What’s New in Version 2.2.1[​](#whats-new-in-version-221 "Direct link to What’s New in Version 2.2.1")

In this release, we’ve updated the cloudflared image and continued our commitment to provide a secure and seamless deployment experience for Kubernetes users:

* 🔄 **Updated**: Upgraded the cloudflare/cloudflared image to version 2025.9.1
  <br />
  <!-- -->
  → View on [Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

You can find the full list of changes and improvements in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.1).

<!-- -->

## Get Started with cloudflared[​](#get-started-with-cloudflared "Direct link to Get Started with cloudflared")

Ready to deploy cloudflared on your Kubernetes cluster? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/cloudflared) will help you:

* Install the Helm chart with minimal setup.
* Modify default values to fit your custom configs.
* Apply best practices for production-grade deployments.

Visit our [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to learn more and get started quickly.

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), the cloudflared Helm chart offers:

* ✅ **Simplicity**: Easy to deploy and manage in Kubernetes environments.
* 🔧 **Configurability**: Tailor it to meet your specific use case or infrastructure needs.
* 🤝 **Community Contributions**: Evolving with direct input from a passionate community.
* 🔒 **Stability**: Built for reliable performance in production workloads.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Want to shape the future of the cloudflared Helm chart? Whether you're a developer, DevOps engineer, or open-source enthusiast, there are many ways to get involved:

* 📘 Dive into our [documentation](https://community-charts.github.io/docs/category/cloudflared) to explore chart configurations.
* 🔧 Contribute code or documentation via our [GitHub repository](https://github.com/community-charts/helm-charts).
* 🐞 Report any bugs or issues you encounter through our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Submit ideas or feature requests to help guide future releases.

Thank you for being part of the cloudflared and open-source Helm community. Let’s keep improving Kubernetes deployment workflows—together!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-22-cloudflared-chart-version-2-2-1-released.md)


---

# Cloudflared Chart Version 2.2.10 Released

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the launch of the **cloudflared Helm chart version 2.2.10**, released on 2026-06-19, featuring **app version 2026.6.1**. This update introduces a host of new features, enhancements, and community-driven improvements designed to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.10 Chart[​](#whats-new-in-cloudflared-2210-chart "Direct link to What's New in Cloudflared 2.2.10 Chart")

In this release, we've made updates to both the Helm chart (version 2.2.10) and the underlying application (version 2026.6.1). Here’s a brief overview of the notable changes:

* **Changed**: Updated the cloudflare/cloudflared image version to 2026.6.1.
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a detailed list of all changes, please check the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.10) on GitHub.

<!-- -->

## Getting Started with Cloudflared 2.2.10 Chart[​](#getting-started-with-cloudflared-2210-chart "Direct link to Getting Started with Cloudflared 2.2.10 Chart")

Are you ready to deploy cloudflared 2.2.10? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/cloudflared) are here to help you through every step of the process, including:

* Quick installation with default configurations.
* Customization options tailored for your environment.
* Best practices for production deployments.

Dive into the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to explore all the options available and get cloudflared up and running today!

## Why Choose the Cloudflared Helm Chart?[​](#why-choose-the-cloudflared-helm-chart "Direct link to Why Choose the Cloudflared Helm Chart?")

The cloudflared Helm chart, proudly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to make the deployment of cloudflared on Kubernetes both simple and reliable. Here are key benefits:

* **Ease of Use**: Enjoy a streamlined installation and configuration process.
* **Community-Driven**: Regular updates and enhancements contributed by our vibrant community.
* **Flexibility**: Configurable options adapted to various use cases.
* **Reliability**: Rigorously tested for stability in diverse Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

Join us in making the cloudflared project even better! GitHub Community Charts is a collaborative initiative, and your contributions are invaluable. Whether it's fixing bugs, enhancing documentation, or proposing new features, here’s how you can participate:

* **Explore the Chart**: Visit the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) for in-depth configuration details.
* **Contribute**: Make your mark by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your ideas for enhancements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of cloudflared and GitHub Community Charts. Together, we can simplify Kubernetes deployments and foster a thriving open-source community!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-19-cloudflared-chart-version-2-2-10-released.md)


---

# cloudflared chart version 2.2.2 released

October 15, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the latest release of the **cloudflared Helm chart version 2.2.2**, published on October 15, 2025. This update includes **app version 2025.10.0**, bringing performance improvements, version bumps, and enhanced reliability for running cloudflared in Kubernetes environments.

## What’s new in version 2.2.2[​](#whats-new-in-version-222 "Direct link to What’s new in version 2.2.2")

This minor release updates both the Helm chart and the underlying container image to the latest version. Highlights include:

* ✅ **Image updated**: The chart now uses the latest cloudflare/cloudflared image — `2025.10.0`
  * [View on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

To learn more about this release, view the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.2).

<!-- -->

## Get started with cloudflared 2.2.2[​](#get-started-with-cloudflared-222 "Direct link to Get started with cloudflared 2.2.2")

Deploying cloudflared into your Kubernetes cluster has never been easier. Our [setup documentation](https://community-charts.github.io/docs/category/cloudflared) will guide you through:

* Installing with default settings in minutes
* Customizing values to fit your infrastructure
* Following best practices for staging and production environments

Head over to the [official documentation](https://community-charts.github.io/docs/category/cloudflared) for configuration examples and advanced usage tips.

## Why cloudflared on Helm?[​](#why-cloudflared-on-helm "Direct link to Why cloudflared on Helm?")

Maintained by the vibrant [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the cloudflared Helm chart makes deploying and managing Argo Tunnel seamless within Kubernetes. What makes it stand out:

* 📦 **Streamlined deployments**: Helm simplifies installs and upgrades
* 🌐 **Built by the community**: Improvements and fixes contributed by real users
* ⚙️ **Highly configurable**: Set up for dev clusters or hardened production environments
* 🔒 **Reliable operation**: Proven stability in a range of Kubernetes workloads

## Contribute to the community[​](#contribute-to-the-community "Direct link to Contribute to the community")

We’d love your help making this chart even better. Whether you're adding new features, improving documentation, or reporting bugs, your contribution matters.

* 🧭 Explore config options in the [cloudflared docs](https://community-charts.github.io/docs/category/cloudflared)
* 🛠 Submit pull requests via our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐛 Found a bug? [Open an issue](https://github.com/community-charts/helm-charts/issues)
* 💡 Got an idea? Share suggestions in our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thanks for supporting the cloudflared chart and the open-source Helm community. Together, we’re making Kubernetes more accessible and powerful for everyone.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-15-cloudflared-chart-version-2-2-2-released.md)


---

# cloudflared chart version 2.2.3 released

October 31, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to introduce the latest release of the **cloudflared Helm chart version 2.2.3**, now available as of October 31, 2025. This update includes **app version 2025.10.1** and brings valuable improvements to help you deploy cloudflared more easily and efficiently on Kubernetes.

<!-- -->

## What’s New in Version 2.2.3[​](#whats-new-in-version-223 "Direct link to What’s New in Version 2.2.3")

This release focuses on alignment with the latest upstream version and continued chart maintenance. Key update includes:

* 🔧 **Updated:** Uses the new cloudflare/cloudflared image version 2025.10.1
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

For the full list of changes, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.3) on GitHub.

## Getting Started with cloudflared 2.2.3[​](#getting-started-with-cloudflared-223 "Direct link to Getting Started with cloudflared 2.2.3")

Whether you're deploying for the first time or upgrading an existing setup, our [installation guides](https://community-charts.github.io/docs/category/cloudflared) offer everything you need:

* Quick-start instructions with default values
* Configuration tips tailored to different environments
* Best practices for production-ready deployments

Visit the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) and get started today.

## Why Choose the cloudflared Helm Chart?[​](#why-choose-the-cloudflared-helm-chart "Direct link to Why Choose the cloudflared Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the cloudflared chart is built with Kubernetes users in mind. Here's why it's a great choice:

* 🚀 **Easy to Use**: Clean defaults and simplified setup
* 💬 **Community-Backed**: Crowdsourced improvements and contributions
* 🔧 **Highly Configurable**: Flexible to meet your specific needs
* ✅ **Proven Stability**: Optimized for Kubernetes environments

## Join Our Community[​](#join-our-community "Direct link to Join Our Community")

Want to help make the chart even better? Whether you're a seasoned Helm pro or just getting started, there’s a place for you in the GitHub Community Charts project:

* 📚 Dive into the [documentation](https://community-charts.github.io/docs/category/cloudflared)
* 🤝 Contribute via [pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Report issues in our [tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Share feature ideas directly with the community

Thank you for supporting cloudflared and contributing to the open-source ecosystem. Let’s keep building reliable, accessible Kubernetes tools—together.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-31-cloudflared-chart-version-2-2-3-released.md)


---

# cloudflared chart version 2.2.4 released

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **cloudflared Helm chart version 2.2.4**, published on 2025-11-08. This version includes the latest **app version 2025.11.1**, featuring valuable enhancements and updates inspired by contributions from our open-source community.

## What’s New in cloudflared 2.2.4[​](#whats-new-in-cloudflared-224 "Direct link to What’s New in cloudflared 2.2.4")

This update brings improvements to both the Helm chart (version 2.2.4) and the underlying application (version 2025.11.1). Highlights include:

* ✅ **Updated** cloudflare/cloudflared container image to version 2025.11.1
  <br />
  <!-- -->
  🔗 [View on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

For full details, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.4) on GitHub.

<!-- -->

## Get Started with cloudflared 2.2.4[​](#get-started-with-cloudflared-224 "Direct link to Get Started with cloudflared 2.2.4")

Looking to deploy cloudflared on your Kubernetes cluster? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/cloudflared) walk you through:

* Quick-start instructions using default settings
* How to tailor deployments for your environment
* Best practices for production use

Head over to the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to explore upgrade paths, configuration options, and implementation tips.

## Why Use the cloudflared Helm Chart?[​](#why-use-the-cloudflared-helm-chart "Direct link to Why Use the cloudflared Helm Chart?")

Built and maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the cloudflared Helm chart offers several key advantages:

* 🚀 **Simple Installation**: Spin up cloudflared with minimal effort
* 🔄 **Regular Updates**: Community-powered contributions and enhancements
* ⚙️ **Highly Configurable**: Adapt the chart to fit your Kubernetes setup
* 🔐 **Reliable**: Battle-tested for production environments

## Join Our Open-Source Community[​](#join-our-open-source-community "Direct link to Join Our Open-Source Community")

cloudflared is developed and maintained with the help of a growing group of contributors. We’d love for you to be part of it! Here’s how you can get involved:

* 📘 Review the [documentation](https://community-charts.github.io/docs/category/cloudflared)
* 🛠️ Improve the chart by submitting [pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Found a bug or issue? [Report it here](https://github.com/community-charts/helm-charts/issues)
* 💡 Help shape the future by [suggesting new features](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being a part of the community. Let’s build better Kubernetes tools together!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-08-cloudflared-chart-version-2-2-4-released.md)


---

# Cloudflared Chart Version 2.2.8 Released

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **cloudflared Helm chart version 2.2.8** on May 29, 2026, featuring **app version 2026.5.2**. This update introduces new features and community-driven enhancements to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.8 Chart[​](#whats-new-in-cloudflared-228-chart "Direct link to What's New in Cloudflared 2.2.8 Chart")

This release not only updates the Helm chart (version 2.2.8) but also the underlying application (version 2026.5.2). Here are the key changes:

* **Changed**: Updated cloudflare/cloudflared image version to 2026.5.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete breakdown of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.8) on GitHub.

<!-- -->

## Getting Started with Cloudflared 2.2.8 Chart[​](#getting-started-with-cloudflared-228-chart "Direct link to Getting Started with Cloudflared 2.2.8 Chart")

Ready to deploy cloudflared 2.2.8? Our [installation guides](https://community-charts.github.io/docs/category/cloudflared) offer step-by-step instructions to help you get started, including:

* Quick installation with default settings.
* Customizing configurations for your unique environment.
* Best practices for secure and reliable production deployments.

Visit the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to explore all your options and deploy cloudflared today.

## Why Choose the Cloudflared Helm Chart?[​](#why-choose-the-cloudflared-helm-chart "Direct link to Why Choose the Cloudflared Helm Chart?")

The cloudflared Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to simplify deploying cloudflared on Kubernetes effectively. Here are some key benefits:

* **Ease of Use**: Effortless installation and configuration process.
* **Community-Driven**: Regular updates and enhancements from our dedicated contributors.
* **Flexibility**: Configurable options that cater to a variety of use cases.
* **Reliability**: Thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

At GitHub Community Charts, we believe in the power of collaboration and welcome your contributions! Whether you're fixing bugs, enhancing documentation, or suggesting new features, here's how you can join us:

* **Explore the Chart**: Dive into the [cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) for detailed configuration information.
* **Contribute**: Feel free to submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of cloudflared and GitHub Community Charts. Together, let's make Kubernetes deployments even easier!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-05-29-cloudflared-chart-version-2-2-8-released.md)


---

# Cloudflared Chart Version 2.2.9 Released

June 10, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the release of the **Cloudflared Helm chart version 2.2.9** on June 10, 2026, featuring **app version 2026.6.0**. This update brings an array of new features, enhancements, and community-driven improvements, making it even easier to deploy Cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.9 Chart[​](#whats-new-in-cloudflared-229-chart "Direct link to What's New in Cloudflared 2.2.9 Chart")

This release includes significant updates to both the Helm chart (version 2.2.9) and the underlying application (version 2026.6.0). Here’s a brief overview of what’s included:

* **Changed**: Updated the Cloudflare Cloudflared image version to 2026.6.0
  <!-- -->
  * Check out the [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)
* **Added**: Configurable liveness and readiness probes to enhance monitoring capabilities

For a complete list of changes, please view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.9) on GitHub.

<!-- -->

## Getting Started with Cloudflared 2.2.9 Chart[​](#getting-started-with-cloudflared-229-chart "Direct link to Getting Started with Cloudflared 2.2.9 Chart")

Ready to deploy Cloudflared 2.2.9? Our [installation guides](https://community-charts.github.io/docs/category/cloudflared) provide comprehensive, step-by-step instructions to help you get started, including:

* Quick installation with default configurations.
* Customization options to fit your specific environment.
* Best practices for deploying in production.

Visit the [Cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) to explore all available options and deploy Cloudflared today.

## Why Choose the Cloudflared Helm Chart?[​](#why-choose-the-cloudflared-helm-chart "Direct link to Why Choose the Cloudflared Helm Chart?")

The Cloudflared Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make the deployment of Cloudflared on Kubernetes straightforward and dependable. Here are some key benefits:

* **Ease of Use**: Installation and configuration made simple.
* **Community-Driven**: Regular improvements and updates from contributors ensure quality.
* **Flexibility**: Configurable options to accommodate diverse use cases.
* **Reliability**: Thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community contributions, and we would love to have you onboard! Whether it’s fixing bugs, enhancing documentation, or suggesting new features, here’s how you can get started:

* **Explore the Chart**: Dive into the [Cloudflared documentation](https://community-charts.github.io/docs/category/cloudflared) for detailed configuration information.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of Cloudflared and GitHub Community Charts. Together, let’s continue simplifying Kubernetes deployments!

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-10-cloudflared-chart-version-2-2-9-released.md)


---

# Exciting Release of Drone Chart Version 0.1.5

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share that the **drone Helm chart version 0.1.5** is now live as of 2026-05-29, featuring **app version 2.28.2**. This update brings a host of new features, enhancements, and community-driven improvements that make deploying Drone on Kubernetes even more straightforward and efficient.

## What's New in Drone 0.1.5 Chart[​](#whats-new-in-drone-015-chart "Direct link to What's New in Drone 0.1.5 Chart")

This latest release includes updates to both the Helm chart (version 0.1.5) and the underlying application (version 2.28.2). Here’s a quick overview of what’s new:

* **Changed**: Updated to the drone/drone image version 2.28.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/drone/drone)

To see the full list of changes, feel free to check the [release notes](https://github.com/community-charts/helm-charts/releases/tag/drone-0.1.5) on GitHub.

<!-- -->

## Getting Started with Drone 0.1.5 Chart[​](#getting-started-with-drone-015-chart "Direct link to Getting Started with Drone 0.1.5 Chart")

Eager to deploy Drone 0.1.5? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/drone) offer step-by-step instructions that cover everything you need to know, including:

* Quick installation with default settings.
* Customizing configurations for your specific environment.
* Best practices for successful production deployments.

Dive into the [drone documentation](https://community-charts.github.io/docs/category/drone) to explore all available options and start your deployment today!

## Why Choose the Drone Helm Chart?[​](#why-choose-the-drone-helm-chart "Direct link to Why Choose the Drone Helm Chart?")

The Drone Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is expertly designed to facilitate reliable deployments of Drone on Kubernetes. Here are some of the key benefits:

* **Ease of Use**: Streamlined installation and configuration processes.
* **Community-Driven**: Regular updates and enhancements from dedicated contributors.
* **Flexibility**: Configurable options that cater to a variety of use cases.
* **Reliability**: Thoroughly tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

Join us in enhancing the Drone and GitHub Community Charts experience! Your contributions are invaluable, and there are several ways you can get involved:

* **Explore the Chart**: Visit the [drone documentation](https://community-charts.github.io/docs/category/drone) for in-depth configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest enhancements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of Drone and GitHub Community Charts. Together, let’s keep making Kubernetes deployments easier and more accessible!

**Tags:**

* [Drone](/blog/tags/drone.md "Build, test, and deploy your code confidently with Drone, a friendly and powerful CI/CD platform for developers.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-05-29-drone-chart-version-0-1-5-released.md)


---

# mlflow chart version 1.10.0 released

June 21, 2026 ·

<!-- -->

4 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **mlflow Helm chart version 1.10.0** on June 21, 2026, featuring **app version 3.14.0**. This latest update includes a host of new features, enhancements, and improvements driven by our vibrant community, all designed to ensure a smoother deployment experience for mlflow on Kubernetes.

## What's New in mlflow 1.10.0 chart[​](#whats-new-in-mlflow-1100-chart "Direct link to What's New in mlflow 1.10.0 chart")

This release showcases significant updates to both the Helm chart (version 1.10.0) and the underlying application (version 3.14.0). Here’s a look at some of the key changes:

* **Added**: Optional image digest support for immutable image pulls

* **Added**: MinIO subchart for S3-compatible artifact storage without external dependencies

* **Added**: Support for uvicorn-opts with log-level merging; uvicorn is now the default server for log injection instead of gunicorn

  <!-- -->

  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/223)
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/310)
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/411)

* **Security**: Enhanced security with readOnlyRootFilesystem and a built-in tmp emptyDir volume

* **Fixed**: Default key names for AWS authentication to ensure existingSecret works with minimal setup
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/225)

* **Security**: Automatic injection of MLFLOW\_SERVER\_ALLOWED\_HOSTS from ingress hosts to mitigate DNS rebinding risks
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/285)

* **Changed**: Documented azure-identity requirement for AKS Managed Identity; workaround using AZURE\_STORAGE\_CONNECTION\_STRING via extraEnvVars
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/423)

* **Security**: Automatic injection of MLFLOW\_SERVER\_CORS\_ALLOWED\_ORIGINS to prevent CORS-based cross-origin threats

* **Added**: New serverAllowedHosts and corsAllowedOrigins values for additional ingress customization; duplicates are removed

* **Fixed**: Auto-configuration of auth PostgreSQL backend from the Bitnami subchart when specific conditions are met
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/504)

* **Added**: Configurable serverHost value for MLflow server binding; defaults to 0.0.0.0
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/230)

* **Added**: Support for Azure Active Directory and MSI authentication with backendStore.mssql.connectionUrl
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/248)

* **Added**: capability to store MSSQL connection URLs in a Kubernetes Secret for better security management
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/248)

* **Fixed**: Resolved issues with ini-file-initializer init container regarding LDAP-only deployments
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/426)

* **Fixed**: Clarified usage of service.name and provided guidance for resource name overrides
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/468)

* **Added**: ExtraDeploy value to allow rendering of additional Kubernetes objects alongside the chart
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/53)

* **Added**: Support for pod scheduling priority with priorityClassName value
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/317)

* **Added**: capability to annotate deployment resource metadata
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/461)

* **Fixed**: Ensured mutual exclusivity for auth and ldapAuth settings; both cannot be enabled simultaneously

* **Fixed**: Corrected schema defaults for various service and security settings

For the complete list of changes, check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.10.0) on GitHub.

<!-- -->

## Getting Started with mlflow 1.10.0 chart[​](#getting-started-with-mlflow-1100-chart "Direct link to Getting Started with mlflow 1.10.0 chart")

Are you ready to deploy mlflow 1.10.0? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/mlflow) will provide you with step-by-step instructions to help you get started, including:

* Quick installations with default configurations.
* Tailoring settings to meet your unique environment.
* Best practices for ensuring smooth production deployments.

Explore the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to discover all available options and launch your mlflow deployment today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, managed by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is your go-to solution for leveraging Kubernetes for mlflow deployment. Key benefits include:

* **User-Friendly**: Simple installation and intuitive configuration.
* **Community-Driven**: Regular updates and enhancements contributed by community members.
* **Flexible**: A range of configurable options to suit diverse use cases.
* **Reliable**: Thoroughly tested to ensure stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

We believe in the strength of community! The GitHub Community Charts project thrives on contributions, and we invite you to join us. Whether you are debugging, enhancing documentation, or proposing new features, here's how you can participate:

* **Explore the Chart**: Dive into the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for configuration insights.
* **Contribute**: Share your expertise by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a problem? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your ideas via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of mlflow and GitHub Community Charts. Together, we can continue to simplify Kubernetes deployments for everyone!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-21-mlflow-chart-version-1-10-0-released.md)


---

# mlflow chart version 1.11.0 released

June 21, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **mlflow Helm chart version 1.11.0** on 2026-06-21, featuring **app version 3.14.0**. This update introduces innovative features, valuable enhancements, and contributions from our dedicated community, aimed at streamlining the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.0 chart[​](#whats-new-in-mlflow-1110-chart "Direct link to What's New in mlflow 1.11.0 chart")

The latest release features updates to both the Helm chart (version 1.11.0) and the underlying application (version 3.14.0). Here is a summary of what’s new:

* **Security**: Introduced a securityContext to the ini-file-initializer and dbchecker init containers
  <!-- -->
  * [GitHub PR](https://github.com/community-charts/helm-charts/pull/433)

For an in-depth look at all changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.0) on GitHub.

<!-- -->

## Getting Started with mlflow 1.11.0 chart[​](#getting-started-with-mlflow-1110-chart "Direct link to Getting Started with mlflow 1.11.0 chart")

Excited to deploy mlflow 1.11.0? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/mlflow) provide you with everything you need to know, including:

* Quick installation with default configurations.
* Customization options tailored to your environment.
* Best practices for effective production deployments.

Explore the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to discover all available options and get started with deploying mlflow today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to facilitate smooth and reliable deployments of mlflow on Kubernetes. Here are some key advantages:

* **Ease of Use**: Simplified installation and configuration processes.
* **Community-Driven**: Engaging updates and enhancements from our contributors.
* **Flexibility**: Configurable options that cater to a variety of use cases.
* **Reliability**: Thoroughly tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on collaboration, and we welcome your contributions! Whether you're addressing bugs, enhancing documentation, or proposing new features, here's how you can get involved:

* **Explore the Chart**: Discover configuration details in the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow).
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting mlflow and GitHub Community Charts. Together, let's make Kubernetes deployments even easier!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-21-mlflow-chart-version-1-11-0-released.md)


---

# mlflow chart version 1.11.1 released

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **mlflow Helm chart version 1.11.1** on June 21, 2026, featuring **app version 3.14.0**. This update introduces an array of new features, enhancements, and community-driven improvements aimed at simplifying your experience deploying mlflow on Kubernetes.

## What's New in mlflow 1.11.1 chart[​](#whats-new-in-mlflow-1111-chart "Direct link to What's New in mlflow 1.11.1 chart")

This release encompasses updates to the Helm chart (version 1.11.1) as well as the underlying application (version 3.14.0). Here’s a brief overview of the changes:

* **Changed**: Updated oauth2-proxy image version to v7.15.3
  <!-- -->
  * [oauth2-proxy](https://quay.io/repository/oauth2-proxy/oauth2-proxy)
* **Changed**: Updated dependency postgresql from 18.7.5 to 18.7.6
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of updates, check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.1) on GitHub.

<!-- -->

## Getting Started with mlflow 1.11.1 chart[​](#getting-started-with-mlflow-1111-chart "Direct link to Getting Started with mlflow 1.11.1 chart")

Are you ready to deploy mlflow 1.11.1? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) offer step-by-step support to help you get started, including:

* Quick installation with default configurations.
* Customization options tailored to your environment.
* Best practices for production deployments.

Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to discover the full range of options and deploy mlflow with confidence!

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to streamline the deployment of mlflow on Kubernetes. Here’s why it stands out:

* **Ease of Use**: Enjoy a simplified installation and configuration process.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our vibrant community.
* **Flexibility**: Access configurable options to suit a variety of use cases.
* **Reliability**: Rely on our chart that has been rigorously tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community contributions, and we warmly invite you to join us! Whether you’re fixing bugs, enhancing documentation, or proposing new features, here’s how to get involved:

* **Explore the Chart**: Dive into the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for detailed configuration options.
* **Contribute**: Submit pull requests through our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of mlflow and the GitHub Community Charts. Together, let’s make Kubernetes deployments easier and more efficient!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-21-mlflow-chart-version-1-11-1-released.md)


---

# mlflow chart version 1.11.2 released

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **mlflow Helm chart version 1.11.2** on June 21, 2026, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements to streamline the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.2 chart[​](#whats-new-in-mlflow-1112-chart "Direct link to What's New in mlflow 1.11.2 chart")

This latest version includes important updates to the Helm chart (version 1.11.2) alongside the underlying application (version 3.14.0). Here’s a brief overview of the enhancements:

* **Changed**: Updated dbchecker image version to 1.38.0
  <!-- -->
  * [dbchecker](https://hub.docker.com/r/library/busybox)
* **Changed**: Updated ini-file-initializer image version to 1.38.0
  <!-- -->
  * [ini-file-initializer](https://hub.docker.com/r/library/busybox)

For a comprehensive list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.2) on GitHub.

<!-- -->

## Getting Started with mlflow 1.11.2 chart[​](#getting-started-with-mlflow-1112-chart "Direct link to Getting Started with mlflow 1.11.2 chart")

Excited to deploy mlflow 1.11.2? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) offer detailed, step-by-step instructions to help you begin, including:

* Quick installation with default configurations.
* Options for customizing settings tailored to your environment.
* Best practices to ensure reliable production deployments.

Don’t forget to visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to explore all available options and get started with your mlflow deployment today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to simplify and enhance your Kubernetes deployment experience. Here are some key benefits:

* **Ease of Use**: Enjoy a straightforward installation and configuration process.
* **Community-Driven**: Regular updates and improvements come from dedicated contributors.
* **Flexibility**: Configurable options make it suitable for various use cases.
* **Reliability**: Rigorously tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

We invite you to join the GitHub Community Charts project! Contributions from community members are always welcome. Whether you’re interested in fixing bugs, enhancing documentation, or proposing new features, here's how you can participate:

* **Explore the Chart**: Discover configuration details in the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow).
* **Contribute**: Share your enhancements by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Feel free to suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of mlflow and GitHub Community Charts. Together, let’s make deploying on Kubernetes even easier!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-21-mlflow-chart-version-1-11-2-released.md)


---

# mlflow chart version 1.2.0 released

June 22, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **mlflow Helm chart version 1.2.0** on 2025-06-22, featuring **app version 3.1.0**. This update brings new features, enhancements, and community-driven improvements to simplify deploying mlflow on Kubernetes.

## What's New in mlflow 1.2.0 chart[​](#whats-new-in-mlflow-120-chart "Direct link to What's New in mlflow 1.2.0 chart")

This release includes updates to the Helm chart (version 1.2.0) and the underlying application (version 3.1.0). Below is the detailed changelog:

* **Added**: Log level configuration added
  <!-- -->
  * [Github Issue](https://github.com/community-charts/helm-charts/issues/137)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.2.0) on GitHub.

<!-- -->

## Getting Started with mlflow 1.2.0 chart[​](#getting-started-with-mlflow-120-chart "Direct link to Getting Started with mlflow 1.2.0 chart")

Ready to deploy mlflow 1.2.0? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) provide step-by-step instructions to get you started, including:

* Quick installation with default configurations.
* Customizing settings to suit your environment.
* Best practices for production deployments.

Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to explore all available options and deploy mlflow today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying mlflow on Kubernetes straightforward and reliable. Key benefits include:

* **Ease of Use**: Simplified installation and configuration.
* **Community-Driven**: Regular updates and improvements from contributors.
* **Flexibility**: Configurable options to meet diverse use cases.
* **Reliability**: Tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a community-driven project, and we welcome your contributions! Whether you're fixing bugs, improving documentation, or suggesting new features, here's how you can get started:

* **Explore the Chart**: Check out the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting mlflow and GitHub Community Charts. Let's continue making Kubernetes deployments easier, together!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-22-mlflow-chart-version-1-2-0-released.md)


---

# mlflow chart version 1.3.0 released

June 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **mlflow Helm chart version 1.3.0** on 2025-06-25, featuring **app version 3.1.1**. This update brings new features, enhancements, and community-driven improvements to simplify deploying mlflow on Kubernetes.

## What's New in mlflow 1.3.0 chart[​](#whats-new-in-mlflow-130-chart "Direct link to What's New in mlflow 1.3.0 chart")

This release includes updates to the Helm chart (version 1.3.0) and the underlying application (version 3.1.1). Below is the detailed changelog:

* **Changed**: Update burakince/mlflow image version to 3.1.1
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/burakince/mlflow)
* **Added**: Add group attribute key for Active Directory users
  <!-- -->
  * [Github Issue](https://github.com/burakince/mlflow/issues/221)
* **Changed**: Update bitnami/postgresql chart version to 16.7.13
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql/16.7.13)
* **Changed**: Update bitnami/mysql chart version to 13.0.2
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/mysql/13.0.2)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.0) on GitHub.

<!-- -->

## Getting Started with mlflow 1.3.0 chart[​](#getting-started-with-mlflow-130-chart "Direct link to Getting Started with mlflow 1.3.0 chart")

Ready to deploy mlflow 1.3.0? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) provide step-by-step instructions to get you started, including:

* Quick installation with default configurations.
* Customizing settings to suit your environment.
* Best practices for production deployments.

Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to explore all available options and deploy mlflow today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying mlflow on Kubernetes straightforward and reliable. Key benefits include:

* **Ease of Use**: Simplified installation and configuration.
* **Community-Driven**: Regular updates and improvements from contributors.
* **Flexibility**: Configurable options to meet diverse use cases.
* **Reliability**: Tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a community-driven project, and we welcome your contributions! Whether you're fixing bugs, improving documentation, or suggesting new features, here's how you can get started:

* **Explore the Chart**: Check out the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting mlflow and GitHub Community Charts. Let's continue making Kubernetes deployments easier, together!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-25-mlflow-chart-version-1-3-0-released.md)


---

# mlflow chart version 1.3.1 released

July 23, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.3.1**, officially available as of **July 23, 2025**. This update includes **mlflow app version 3.1.3**, featuring enhancements, updated dependencies, and meaningful contributions from our open-source community.

## What’s New in mlflow 1.3.1[​](#whats-new-in-mlflow-131 "Direct link to What’s New in mlflow 1.3.1")

Helm chart version 1.3.1 introduces several key improvements and version bumps to support a smoother and more secure deployment experience on Kubernetes:

* 🔄 **App Update**: Upgraded `burakince/mlflow` image to version `3.1.3`
  * [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)
* 📦 **PostgreSQL Update**: Bumped the Bitnami `postgresql` dependency from `16.7.13` to `16.7.21`
  * [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)
* 📦 **MySQL Update**: Upgraded Bitnami `mysql` dependency from `13.0.2` to `14.0.0`
  * [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/mysql)

For a complete breakdown of changes, see the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.1).

<!-- -->

## Getting Started with mlflow 1.3.1[​](#getting-started-with-mlflow-131 "Direct link to Getting Started with mlflow 1.3.1")

Excited to get started with mlflow? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/mlflow) walk you through:

* Deploying quickly with default settings.
* Customizing configurations for your specific environment.
* Leveraging best practices for production-ready clusters.

Whether you're running a quick proof of concept or setting up for a large-scale deployment, the mlflow Helm chart has you covered.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the mlflow Helm chart is designed for developers, data scientists, and DevOps teams who want simple, scalable, and reliable mlflow deployments on Kubernetes.

Top reasons to choose this chart include:

* ✅ **Simplicity**: Easy to install and configure—perfect for newcomers and pros alike.
* 👥 **Community-Powered**: Built and maintained by the open-source community.
* ⚙️ **Highly Configurable**: Adapts to a wide variety of use cases and infrastructures.
* 🛡️ **Production-Ready**: Tested in real-world Kubernetes clusters for stability.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Open-source is at the heart of what we do—and we welcome your contributions! Whether you're submitting a bug fix, enhancing documentation, or suggesting new features, here’s how you can get involved:

* 📘 Read the [mlflow chart docs](https://community-charts.github.io/docs/category/mlflow) for instructions and configurations.
* 🔧 Contribute directly via pull requests on [GitHub](https://github.com/community-charts/helm-charts).
* 🐞 Report bugs or suggest features using our [issue tracker](https://github.com/community-charts/helm-charts/issues).

Thank you for supporting the mlflow Helm chart and being an essential part of the GitHub Community Charts ecosystem. Together, we’re making Helm deployments easier, better, and more accessible for everyone.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")
* [Cloud Databases](/blog/tags/cloud-databases.md "Expert guides and best practices for connecting to managed cloud databases and caches on AWS, Azure, GCP, and other leading cloud providers.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-23-mlflow-chart-version-1-3-1-released.md)


---

# mlflow chart version 1.3.2 released

July 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **mlflow Helm chart version 1.3.2** is now available as of **2025-07-24**, bringing you **mlflow app version 3.1.4**. This release delivers usability enhancements and community-driven improvements to make deploying mlflow on Kubernetes even smoother and more efficient.

## What’s New in Helm Chart 1.3.2[​](#whats-new-in-helm-chart-132 "Direct link to What’s New in Helm Chart 1.3.2")

With this release, both the Helm chart and the application itself have been upgraded to offer better functionality and integration:

* 🚀 **Updated**: Container image upgraded to `burakince/mlflow:3.1.4`
  <br />
  <!-- -->
  → View on [Docker Hub](https://hub.docker.com/r/burakince/mlflow)

To see all technical changes, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.2).

<!-- -->

## Get Started with mlflow 1.3.2[​](#get-started-with-mlflow-132 "Direct link to Get Started with mlflow 1.3.2")

Deploying mlflow has never been easier! Whether you're just getting started or customizing for production, our [installation docs](https://community-charts.github.io/docs/category/mlflow) guide you through every step:

* Easy setup with default values
* Advanced configuration options
* Production-ready deployment tips

Start building today with the official [mlflow documentation](https://community-charts.github.io/docs/category/mlflow).

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, this open-source Helm chart simplifies your mlflow setup on Kubernetes. Here’s why it stands out:

* ✅ **User-Friendly**: Fast, simple installation
* 🛠️ **Highly Configurable**: Adaptable for local dev or enterprise scale
* 📢 **Community-Maintained**: Built and improved by passionate contributors
* 🔒 **Stable and Secure**: Tested for Kubernetes reliability

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We're an open-source community—and that means your input matters! Whether you're reporting bugs or adding new features, here’s how to get involved:

* Dive into the [mlflow chart docs](https://community-charts.github.io/docs/category/mlflow)
* Contribute on [GitHub](https://github.com/community-charts/helm-charts)
* [Report issues](https://github.com/community-charts/helm-charts/issues) or request new features
* Spread the word and help others discover our work!

Thank you for being a part of the mlflow and Helm chart journey. Let’s keep improving Kubernetes deployments—together!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-24-mlflow-chart-version-1-3-2-released.md)


---

# mlflow chart version 1.4.0 released

August 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest **mlflow Helm chart version 1.4.0**, now available as of August 2, 2025. This version ships with **mlflow app version 3.1.4** and includes updates to help you deploy and manage mlflow more easily and securely in Kubernetes environments.

<!-- -->

## What’s New in mlflow Helm Chart 1.4.0[​](#whats-new-in-mlflow-helm-chart-140 "Direct link to What’s New in mlflow Helm Chart 1.4.0")

This release brings notable improvements and added flexibility for cloud-native ML workflows:

* ✅ **New Feature**: Support for reading AWS credentials (`AWS Access Key ID` and `AWS Secret Access Key`) from an existing Kubernetes secret.

For a full list of updates, check the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.4.0).

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Deploying mlflow on Kubernetes has never been simpler. Our [mlflow Helm documentation](https://community-charts.github.io/docs/category/mlflow) provides everything you need—whether you're just getting started or customizing for production.

Here’s what you’ll find:

* Instructions for quick installation using default settings.
* Guides for advanced configuration tailored to your infrastructure.
* Best practices to ensure stable and secure deployments.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

Developed and maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the mlflow Helm chart is your go-to solution for running mlflow in Kubernetes. It’s designed to be:

* 🚀 **Easy to Deploy**: Spin up your ML platform with minimal effort.
* 🧩 **Highly Flexible**: Configure to meet your team’s specific needs.
* 🤝 **Community-Driven**: Built in collaboration with contributors worldwide.
* 🔒 **Production-Ready**: Tested for reliability and scalability at every update.

## Join Our Community[​](#join-our-community "Direct link to Join Our Community")

We're an open-source community, and your involvement helps mlflow and our charts thrive. Here’s how to participate:

* 📘 Review our [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to explore available options.
* 🛠️ Contribute code or improvements via pull requests to the [GitHub repo](https://github.com/community-charts/helm-charts).
* 🐞 Report bugs quickly and easily through our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Share feature ideas and enhancements—we’re all ears!

Thank you for being part of the mlflow and Helm chart community. Let’s continue building better tools together for the Kubernetes and ML ecosystems.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-02-mlflow-chart-version-1-4-0-released.md)


---

# mlflow chart version 1.4.1 released

August 6, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.4.1**, available as of August 6, 2025. This update comes with **app version 3.2.0** and introduces enhancements, new features, and valuable contributions from our growing community to make deploying mlflow on Kubernetes even more seamless.

## What’s New in mlflow 1.4.1[​](#whats-new-in-mlflow-141 "Direct link to What’s New in mlflow 1.4.1")

This release includes important updates to both the Helm chart and the underlying mlflow application. Here’s a quick look at what’s new:

- 🔄 **Updated**: The container image `burakince/mlflow` has been upgraded to **version 3.2.0**<br /><!-- --> → [View Image on Docker Hub](https://hub.docker.com/r/burakince/mlflow)

Check out the full changelog and details in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.4.1).

<!-- -->

## How to Get Started with mlflow 1.4.1[​](#how-to-get-started-with-mlflow-141 "Direct link to How to Get Started with mlflow 1.4.1")

Getting up and running with mlflow 1.4.1 is easy. Our [official Helm documentation](https://community-charts.github.io/docs/category/mlflow) offers a complete guide to help you deploy quickly and confidently.

Here’s what you’ll find:

* Instructions for quick installation using default values
* Customization options for various deployment needs
* Tips and best practices for running mlflow in production

Explore the documentation and start your deployment today.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

Supported and maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the mlflow Helm chart is purpose-built to streamline the deployment process on Kubernetes. Here’s why it stands out:

* ✅ **User-Friendly**: Simplified setup and configuration
* 🌐 **Driven by Community**: Actively updated with community contributions
* ⚙️ **Highly Configurable**: Adaptable to a variety of use cases
* 🛡️ **Reliable**: Tested thoroughly for Kubernetes environments

Whether you're deploying in dev or production, this chart provides the dependability you need.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’re always looking for contributors to help improve the mlflow Helm chart and other community-maintained charts.

Here’s how to get involved:

* 📘 Read the [mlflow chart documentation](https://community-charts.github.io/docs/category/mlflow)
* 💡 Contribute via pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report issues or bugs in the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* ✨ Request new features directly on [GitHub](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the open-source ecosystem. Together, we’re building better tools for deploying machine learning workflows on Kubernetes.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-06-mlflow-chart-version-1-4-1-released.md)


---

# mlflow chart version 1.5.0 released

August 10, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the official release of the **mlflow Helm chart version 1.5.0**, published on 2025-08-10. This version includes **mlflow application version 3.2.0** and brings valuable feature enhancements and community-driven contributions to help simplify and improve your mlflow deployments on Kubernetes.

## What’s New in mlflow 1.5.0[​](#whats-new-in-mlflow-150 "Direct link to What’s New in mlflow 1.5.0")

This release enhances security, flexibility, and transparency through the following updates:

* ✅ **Support for existing secrets** to authenticate PostgreSQL database credentials<br /><!-- -->→ [View on GitHub](https://github.com/community-charts/helm-charts/issues/200)

* ✅ **Support for existing secrets** to manage admin authentication credentials

* ✅ **New telemetry flag** allowing you to enable or disable telemetry data collection

For full details, visit the official [1.5.0 release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.5.0) on GitHub.

<!-- -->

## Getting Started with mlflow 1.5.0[​](#getting-started-with-mlflow-150 "Direct link to Getting Started with mlflow 1.5.0")

Getting started is easy with our step-by-step [installation guides](https://community-charts.github.io/docs/category/mlflow). Whether you’re running a small test cluster or a production-scale pipeline, the documentation has everything you need:

* 📦 Quick installs with default settings
* 🎛️ Custom configuration examples
* 🛡️ Best practices for production-ready deployments

Explore the full documentation at [community-charts.github.io](https://community-charts.github.io/docs/category/mlflow) and deploy your mlflow stack with confidence.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the mlflow Helm chart offers a reliable, Kubernetes-native way to manage your ML lifecycle. Benefits include:

* ⚙️ Easy setup with flexible configuration
* 🤝 Built and improved by a growing open-source community
* 🌐 Integrates with popular Kubernetes setups
* 🧪 Regularly tested for production readiness

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The mlflow Helm chart thrives thanks to an active open-source community. We’d love your help in making it even better. You can:

* 📖 Dive into the [mlflow chart documentation](https://community-charts.github.io/docs/category/mlflow) for details
* ✍️ Contribute via pull requests to the [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or suggest features using our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you for being part of our journey. Let’s build an even more powerful mlflow deployment experience—together!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-10-mlflow-chart-version-1-5-0-released.md)


---

# mlflow chart version 1.6.0 released

August 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the mlflow Helm chart — version 1.6.0 — available as of August 25, 2025. This release includes the updated mlflow application version 3.2.0 and brings a variety of improvements designed to make your Kubernetes deployments more seamless and secure.

## What’s new in mlflow chart 1.6.0[​](#whats-new-in-mlflow-chart-160 "Direct link to What’s new in mlflow chart 1.6.0")

Version 1.6.0 introduces several key changes and fixes thanks to contributions from our vibrant open-source community. Highlights include:

* 🔁 Auth and LDAP Auth external secret loading now handled via init containers

  * Addresses: [Issue #200](https://github.com/community-charts/helm-charts/issues/200), [Issue #217](https://github.com/community-charts/helm-charts/issues/217)

* 🔒 Improved security handling by removing empty security context definitions

  * Fixes: [Issue #219](https://github.com/community-charts/helm-charts/issues/219)

For the full list of updates and technical details, check out the official [mlflow 1.6.0 release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.6.0) on GitHub.

<!-- -->

## Get started with mlflow 1.6.0[​](#get-started-with-mlflow-160 "Direct link to Get started with mlflow 1.6.0")

Deploying mlflow in your Kubernetes environment is easier than ever. Our updated [installation guide](https://community-charts.github.io/docs/category/mlflow) covers everything you need to get up and running:

* One-step install with default configurations
* How to customize settings for your specific needs
* Best practices for stable and secure production setups

Start exploring mlflow Helm chart features and deployment strategies by visiting the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow).

## Why choose the mlflow Helm chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why choose the mlflow Helm chart?")

Backed by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) initiative, the mlflow Helm chart is built to provide a production-ready, flexible, and easy-to-use deployment strategy:

* ⚙️ Simple, intuitive setup with Helm
* 🤝 Actively maintained by a passionate open-source community
* 🧩 Highly configurable to fit a range of Kubernetes environments
* 🛡️ Stable and secure architecture for reliable ML workflows

## Join the community[​](#join-the-community "Direct link to Join the community")

We’d love for you to be part of the growing mlflow Helm chart community! There are many ways to get involved:

* 📚 Learn how the chart works in the [official documentation](https://community-charts.github.io/docs/category/mlflow)
* 🔧 Contribute code or fixes via pull requests to the [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or issues through our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Propose new features and enhancements

Thank you for being part of the mlflow journey. With support from our community, we’re making MLOps on Kubernetes more accessible and powerful for everyone.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-25-mlflow-chart-version-1-6-0-released.md)


---

# mlflow chart version 1.6.1 released

August 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.6.1**, published on 2025-08-25 and powered by **mlflow app version 3.3.1**. This update introduces several enhancements, improved dependency versions, and continued support from the open-source community to make deploying MLflow on Kubernetes even easier.

## What’s new in version 1.6.1[​](#whats-new-in-version-161 "Direct link to What’s new in version 1.6.1")

This release includes updates to both the Helm chart and its dependencies, ensuring greater reliability and smoother integration for Kubernetes users:

* 🔄 **Image Update**: Upgraded Docker image to `burakince/mlflow:3.3.1`<br /><!-- -->➤ [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)

* ⬆️ **PostgreSQL Dependency**: Upgraded Bitnami PostgreSQL chart from `16.7.21` to `16.7.26`<br /><!-- -->➤ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

* ⬆️ **MySQL Dependency**: Upgraded Bitnami MySQL chart from `14.0.0` to `14.0.3`<br /><!-- -->➤ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/mysql)

🔗 For the complete list of changes, review the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.6.1).

<!-- -->

## Get started with mlflow 1.6.1[​](#get-started-with-mlflow-161 "Direct link to Get started with mlflow 1.6.1")

Deploying mlflow on Kubernetes has never been easier. Check out our [installation guides](https://community-charts.github.io/docs/category/mlflow) to get up and running quickly:

* Install using default configurations for a fast setup
* Customize values to match your specific use case
* Follow best practices for production environments

📘 Visit the [mlflow docs](https://community-charts.github.io/docs/category/mlflow) for full configuration options and deployment guidance.

## Why use the mlflow Helm chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why use the mlflow Helm chart?")

Maintained by the open-source community via the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, this Helm chart streamlines the mlflow deployment process:

* ✅ **User-Friendly**: Deploy with minimal config effort
* 💡 **Community-Powered**: Frequent improvements and feedback-driven updates
* ⚙️ **Flexible**: Adaptable to various Kubernetes setups
* 📦 **Stable**: Tested for resilience in production-grade clusters

## Join the mlflow community[​](#join-the-mlflow-community "Direct link to Join the mlflow community")

The GitHub Community Charts initiative thrives on collaboration. Whether you're new to Kubernetes or a seasoned devops pro, your contributions are highly valued:

* 🔍 Read more about chart configuration in our [official docs](https://community-charts.github.io/docs/category/mlflow)
* 💻 Submit a PR on our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Report issues or request features via our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you for being part of the mlflow and Helm chart community. Together, we’re building better tools for deploying machine learning solutions at scale.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")
* [CI/CD](/blog/tags/ci-cd.md "Discover expert CI/CD strategies, automation workflows, and top tools for continuous integration and continuous deployment to accelerate your software delivery pipeline.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-25-mlflow-chart-version-1-6-1-released.md)


---

# mlflow chart version 1.6.2 released

August 28, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the new version of the mlflow Helm chart has landed! **Version 1.6.2**, released on 2025-08-28, includes important updates and enhancements that make deploying mlflow on Kubernetes even smoother. This release includes **app version 3.3.2** and reflects continued feedback and contributions from our amazing open-source community.

## What's New in mlflow chart 1.6.2[​](#whats-new-in-mlflow-chart-162 "Direct link to What's New in mlflow chart 1.6.2")

Here’s what’s included in the latest release:

* 🔄 **Updated**: Docker image bumped to `burakince/mlflow` version 3.3.2
  <br />
  <!-- -->
  👉 [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)
* 🛠️ **Updated**: PostgreSQL dependency upgraded from `16.7.26` to `16.7.27`
  <br />
  <!-- -->
  👉 [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Want to explore everything in this release? Check out the full [changelog on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.6.2).

<!-- -->

## Getting Started with mlflow chart 1.6.2[​](#getting-started-with-mlflow-chart-162 "Direct link to Getting Started with mlflow chart 1.6.2")

Ready to get hands-on with the latest features? Our comprehensive [installation guide](https://community-charts.github.io/docs/category/mlflow) walks you through:

* Installing with default settings in minutes
* Customizing configurations for your environment
* Best practices for staging and production workloads

Deploying mlflow in Kubernetes has never been easier. Visit the [documentation hub](https://community-charts.github.io/docs/category/mlflow) and start building today.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

The mlflow Helm chart is built for reliability, flexibility, and community collaboration. Maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), it offers:

* ✅ Simple installation and upgrade workflows
* 🌱 Ongoing development from a vibrant open-source community
* ⚙️ Customizable configurations for various Kubernetes setups
* 🔒 Proven stability across cloud-native platforms

Whether you're running experiments in dev or scaling up in production, this chart has you covered.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’re always looking for contributors, feedback, and ideas to improve mlflow and our charts. Here’s how you can get involved:

* 📘 Learn more in the [official documentation](https://community-charts.github.io/docs/category/mlflow)
* 💻 Contribute on [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report issues or bugs in our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 🌟 Suggest new features or improvements and help us grow

Thanks for being part of the mlflow community! Together we’re making Kubernetes-native machine learning workflows more accessible than ever.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-28-mlflow-chart-version-1-6-2-released.md)


---

# mlflow chart version 1.6.3 released

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to announce the launch of the latest release — the **mlflow Helm chart version 1.6.3**, published on September 18, 2025. This version includes the updated **app version 3.4.0**, bringing performance improvements and enhanced Kubernetes integration to streamline your mlflow deployments.

## What’s New in mlflow 1.6.3[​](#whats-new-in-mlflow-163 "Direct link to What’s New in mlflow 1.6.3")

Version 1.6.3 delivers important updates both to the Helm chart and the mlflow application. Highlights from this release:

* ✅ **Updated**: Image version upgraded to `burakince/mlflow:3.4.0`
  <br />
  <!-- -->
  → [Docker Hub: burakince/mlflow](https://hub.docker.com/r/burakince/mlflow)

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.6.3) on GitHub.

<!-- -->

## Get Started with mlflow 1.6.3[​](#get-started-with-mlflow-163 "Direct link to Get Started with mlflow 1.6.3")

Looking to get up and running quickly? Our comprehensive [mlflow installation guides](https://community-charts.github.io/docs/category/mlflow) walk you through every step:

* Fast deployment using default settings.
* Advanced configuration for custom use cases.
* Proven tips for production-grade setups.

Dive into the documentation and start deploying mlflow with confidence today.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, this Helm chart makes deploying mlflow to Kubernetes both efficient and reliable. Benefits include:

* 🚀 **Streamlined Setup**: Deploy mlflow in just a few commands.
* 🤝 **Community-Led**: Built and improved by open-source contributors.
* ⚙️ **High Customizability**: Tailor deployments to your unique needs.
* 🔒 **Production-Proven**: Tested in diverse Kubernetes environments.

Whether you're experimenting locally or managing large-scale ML workflows, the mlflow Helm chart adapts to your goals.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We welcome contributors of all kinds! If you’re passionate about open source or want to give back, here’s how you can help:

* 📘 Learn how it works: Review the [mlflow chart docs](https://community-charts.github.io/docs/category/mlflow)
* 🛠️ Fork and improve: Contribute via [GitHub pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs: Open issues on our [GitHub tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Share ideas: Propose features or enhancements [right here](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the mlflow and Kubernetes open-source community. Let’s continue building great tools together!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-18-mlflow-chart-version-1-6-3-released.md)


---

# mlflow chart version 1.7.0 released

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to introduce the latest update to the mlflow Helm chart—version 1.7.0—released on September 18, 2025. This chart includes the upgraded **mlflow app version 3.4.0**, packed with new features and improvements inspired by community feedback.

## What's new in version 1.7.0[​](#whats-new-in-version-170 "Direct link to What's new in version 1.7.0")

This release brings several updates to enhance your Kubernetes deployment experience:

* ✅ **Backend store support for MSSQL** has been added, empowering broader database compatibility.
  <br />
  <!-- -->
  → [View the related GitHub issue](https://github.com/burakince/mlflow/issues/288)

For the full list of changes in this release, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.7.0).

<!-- -->

## Get started with mlflow 1.7.0[​](#get-started-with-mlflow-170 "Direct link to Get started with mlflow 1.7.0")

Deploying mlflow on Kubernetes is now easier than ever. Our comprehensive guides walk you through:

* Quick installation using default settings.
* Custom configuration based on your specific needs.
* Production-ready deployment tips and best practices.

Explore the documentation to start your journey:<br /><!-- -->📘 [mlflow Helm chart docs](https://community-charts.github.io/docs/category/mlflow)

## Why use the mlflow Helm chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why use the mlflow Helm chart?")

The mlflow Helm chart, developed and maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), offers a fast and reliable way to run mlflow on Kubernetes. With each version, we focus on:

* 🚀 **Simplicity**: Easy to install, configure, and manage.
* 🤝 **Community Power**: Built and enhanced by contributors like you.
* 🛠️ **Customization**: Plenty of configuration options to suit all use cases.
* 🔒 **Stability**: Tested in real-world Kubernetes environments.

## Get involved and contribute[​](#get-involved-and-contribute "Direct link to Get involved and contribute")

We’re proud to be a community-driven project and would love your help! There are many ways to contribute:

* 🔍 Learn about configuration and features in our [official docs](https://community-charts.github.io/docs/category/mlflow).
* 🧱 Submit improvements or new features via [pull requests](https://github.com/community-charts/helm-charts).
* 🐛 Report issues or bugs in the [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Propose enhancements by [submitting a feature request](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being a part of the mlflow and Kubernetes open-source community. Let’s keep building better charts—together!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-18-mlflow-chart-version-1-7-0-released.md)


---

# mlflow chart version 1.7.1 released

September 20, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the **mlflow Helm chart, version 1.7.1**, is now available as of September 20, 2025. This update includes **mlflow app version 3.4.0** and introduces new features focused on flexibility and user-driven improvements—making your Kubernetes deployments even more seamless.

<!-- -->

## Highlights of the 1.7.1 Release[​](#highlights-of-the-171-release "Direct link to Highlights of the 1.7.1 Release")

This version includes updates to both the Helm chart and underlying application:

* 🔧 **Chart Upgrade**: Enhanced support for configurable init container images, allowing greater flexibility in tailored deployments.

To review all changes in detail, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.7.1) on GitHub.

## Getting Started with mlflow 1.7.1[​](#getting-started-with-mlflow-171 "Direct link to Getting Started with mlflow 1.7.1")

Ready to launch mlflow with the latest chart? Our [documentation](https://community-charts.github.io/docs/category/mlflow) walks you through every step, whether you’re deploying locally or in production. You’ll find guides for:

* Fast start with default settings.
* Full customization for advanced use cases.
* Best practices for managing production workloads.

Start exploring now and deploy your mlflow chart with confidence.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, this Helm chart brings the full power of **mlflow** to your **Kubernetes** infrastructure. Here’s why it stands out:

* 🚀 **Easy Deployment**: Install mlflow in minutes with Helm.
* 🤝 **Community-Driven**: Actively maintained with regular updates and improvements.
* ⚙️ **Highly Configurable**: Supports a range of deployment scenarios.
* 💡 **Production-Ready**: Trusted and tested for real-world Kubernetes environments.

## Join Our Community[​](#join-our-community "Direct link to Join Our Community")

We welcome you to contribute and help evolve this open-source project! Whether you're submitting a pull request, opening an issue, or just sharing feedback, your input helps shape the future of mlflow deployments in Kubernetes.

Here’s how to get involved:

* 📘 Visit the [documentation](https://community-charts.github.io/docs/category/mlflow) to customize and configure.
* ⭐ Join us on [GitHub](https://github.com/community-charts/helm-charts) to contribute.
* 🐛 Report any issues [here](https://github.com/community-charts/helm-charts/issues).
* 💡 Suggest new features by opening a [feature request](https://github.com/community-charts/helm-charts/issues/new).

Thanks for being a part of the mlflow community. Let's keep building better deployments—together.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-20-mlflow-chart-version-1-7-1-released.md)


---

# mlflow chart version 1.7.2 released

October 17, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **mlflow Helm chart version 1.7.2**, available as of 2025-10-17. This release includes several improvements and now ships with **mlflow app version 3.5.0**, enhancing performance and compatibility for Kubernetes deployments.

## What’s New in mlflow Chart 1.7.2[​](#whats-new-in-mlflow-chart-172 "Direct link to What’s New in mlflow Chart 1.7.2")

This update brings important changes to both the Helm chart and its dependencies. Here's what's included in version 1.7.2:

* ✅ **Updated mlflow image** to version 3.5.0<br /><!-- -->→ [Docker Hub: burakince/mlflow](https://hub.docker.com/r/burakince/mlflow)

* 📦 **Updated PostgreSQL dependency** from version 16.7.27 to 18.0.15<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For full details, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.7.2).

<!-- -->

## Get Started with mlflow 1.7.2[​](#get-started-with-mlflow-172 "Direct link to Get Started with mlflow 1.7.2")

Ready to deploy mlflow using Helm? Our documentation has you covered with everything from basic setup to production best practices:

* 🛠️ Quick installation using default settings
* ⚙️ Custom configuration options to match your environment
* 💡 Best practices for reliable Kubernetes deployments

Browse the full [mlflow installation guide](https://community-charts.github.io/docs/category/mlflow) to get started quickly.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

Maintained by the [GitHub Community Charts project](https://github.com/community-charts/helm-charts), our mlflow Helm chart is built to simplify your machine learning workflows on Kubernetes. Key advantages include:

* 🚀 Fast and easy setup
* 🤝 Maintained and improved by the open-source community
* 🔧 Highly configurable to suit a variety of use cases
* 🧪 Battle-tested across diverse Kubernetes environments

## Contribute to the Community[​](#contribute-to-the-community "Direct link to Contribute to the Community")

We’re proud to be a part of the open-source community — and we’d love your help to make this project even better. Whether you're contributing code, reporting issues, or suggesting new features, here's how to join in:

* 🔍 Learn how the chart works in our [mlflow chart docs](https://community-charts.github.io/docs/category/mlflow)
* 🙌 Contribute improvements on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs and track issues on our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💬 Share ideas for enhancements and new features

Thanks for supporting the mlflow Helm chart project. We look forward to growing this community with you — one chart at a time.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-17-mlflow-chart-version-1-7-2-released.md)


---

# mlflow chart version 1.7.3 released

October 23, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the **mlflow Helm chart — v1.7.3**, featuring **mlflow app version 3.5.1**. Available as of October 23, 2025, this release introduces new functionality and community-driven refinements to make deploying mlflow on Kubernetes even easier.

## What's New in 1.7.3[​](#whats-new-in-173 "Direct link to What's New in 1.7.3")

Here’s what’s included in this chart release:

* 🔄 **Updated**: Docker image version for burakince/mlflow upgraded to 3.5.1<br /><!-- -->→ [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)

* 🗃️ **Updated**: PostgreSQL dependency bumped from 18.0.15 to 18.1.1<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

To review all the details and contributions, visit the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.7.3).

<!-- -->

## How to Install mlflow 1.7.3[​](#how-to-install-mlflow-173 "Direct link to How to Install mlflow 1.7.3")

Getting started with the Helm chart is simple. Whether you’re experimenting locally or rolling out mlflow in a robust cloud-native environment, our [installation docs](https://community-charts.github.io/docs/category/mlflow) guide you every step of the way.

Highlights include:

* 🚀 Quick installation using default settings
* ⚙️ Customization options for different Kubernetes environments
* 🛡️ Tips for optimizing production deployments

Check out the full [mlflow Helm chart documentation](https://community-charts.github.io/docs/category/mlflow) to explore configuration options and start your deployment.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

The mlflow Helm chart, maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, offers a powerful yet flexible way to run mlflow on Kubernetes. Here’s why users love it:

* ✅ Easy setup — get up and running in minutes
* 🔧 Highly configurable for diverse machine learning workflows
* 🌍 Backed by a passionate open-source community
* 📦 Regularly updated for security and reliability

If mlflow is part of your MLOps toolchain, this chart helps ensure smoother operations on Kubernetes.

## Join Our Community[​](#join-our-community "Direct link to Join Our Community")

The GitHub Community Charts project thrives because of passionate contributors like you. Whether you’re improving documentation, proposing enhancements, or reporting issues — your input makes a difference.

Here’s how to get involved:

* 📘 Explore the [docs](https://community-charts.github.io/docs/category/mlflow) to learn about configuration options.
* 🛠️ Contribute directly via [pull requests](https://github.com/community-charts/helm-charts).
* 🐞 Report bugs or request features on our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being a part of the mlflow and Kubernetes open-source community. Together, we’re making MLOps more accessible and powerful for everyone.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-23-mlflow-chart-version-1-7-3-released.md)


---

# mlflow chart version 1.7.4 released

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the **mlflow Helm chart (1.7.4)** is now available as of 2025-11-08. This release features **mlflow app version 3.6.0**, delivering a more seamless experience when deploying mlflow in Kubernetes environments.

## What’s new in version 1.7.4[​](#whats-new-in-version-174 "Direct link to What’s new in version 1.7.4")

Version 1.7.4 introduces updates focused on improving stability and compatibility. This includes an upgrade to the latest mlflow image along with enhancements to key dependencies:

* ✅ **Updated**: Upgraded Docker image to `burakince/mlflow:3.6.0`
  <br />
  <!-- -->
  ➤ [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)
* 🔄 **Updated**: PostgreSQL dependency bumped from `18.1.1` to `18.1.7`
  <br />
  <!-- -->
  ➤ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of updates and detailed changelog, check out the official [1.7.4 release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.7.4).

<!-- -->

## Getting started with mlflow 1.7.4[​](#getting-started-with-mlflow-174 "Direct link to Getting started with mlflow 1.7.4")

Ready to dive in? Setting up mlflow using the latest Helm chart is simple. Our [installation documentation](https://community-charts.github.io/docs/category/mlflow) covers everything you need to get started:

* 🚀 Quick installation with out-of-the-box defaults
* ⚙️ Tailoring configurations for your environment
* 📦 Tips for running mlflow in production on Kubernetes

Visit the [official mlflow chart docs](https://community-charts.github.io/docs/category/mlflow) to explore configuration options and deployment best practices.

## Why use the mlflow Helm chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why use the mlflow Helm chart?")

Crafted and supported by the open-source community, the mlflow Helm chart is purpose-built for seamless Kubernetes integration. Here's why it stands out:

* 🧩 **Simple setup**: Deploy mlflow efficiently with Helm’s templated configuration system
* 💬 **Open-source collaboration**: Benefit from frequent updates driven by real-world feedback
* 🔧 **Customizable deployment**: Fine-tune the chart to fit your workflow or cloud infrastructure
* ✅ **Kubernetes-ready**: Built and tested for robust performance on Kubernetes

## Join our open-source community[​](#join-our-open-source-community "Direct link to Join our open-source community")

The mlflow Helm chart is maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), a dedicated group of developers, DevOps engineers, and contributors. Whether you're here to explore or actively contribute, we’d love to have you involved:

* 📘 Check the [mlflow chart documentation](https://community-charts.github.io/docs/category/mlflow)
* 🔧 Contribute improvements, fixes, or enhancements on [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Submit bugs or suggest ideas via our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thanks for being part of the community. Together, we’re making kubernetes-native mlflow easier to deploy, maintain, and scale!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-08-mlflow-chart-version-1-7-4-released.md)


---

# mlflow chart version 1.8.0 released

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.8.0**, available as of 2025-11-08. This release includes the latest **app version 3.6.0** and brings valuable improvements focused on performance, customization, and Kubernetes-native deployments.

## What’s New in mlflow Helm chart 1.8.0[​](#whats-new-in-mlflow-helm-chart-180 "Direct link to What’s New in mlflow Helm chart 1.8.0")

This version of the chart includes important updates designed to offer greater flexibility when running mlflow on Kubernetes. Highlights include:

* ✅ **Resource Configuration for Init Containers**: You can now define compute resources for the `dbchecker` and `ini-file-initializer` init containers.
  <br />
  <!-- -->
  See the discussion on [GitHub Issue #265](https://github.com/community-charts/helm-charts/issues/265)

These changes allow for more efficient use of resources and better alignment with production-grade deployments.

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.0).

<!-- -->

## Get Started with mlflow 1.8.0[​](#get-started-with-mlflow-180 "Direct link to Get Started with mlflow 1.8.0")

Deploying mlflow on Kubernetes has never been easier. Our step-by-step [installation guides](https://community-charts.github.io/docs/category/mlflow) walk you through everything you need to get up and running. Learn how to:

* Perform a basic install with default values
* Customize the chart to fit your specific use case
* Apply best practices for robust, production-ready deployments

Check out the full [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to get started.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

The mlflow Helm chart is built and maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) project with the goal of making mlflow easy, scalable, and reliable to run in Kubernetes.

Key benefits include:

* 🚀 **Simple Deployment**: Install mlflow with a single command
* 🤝 **Community-Driven**: Developed and improved by contributors from around the world
* 🔧 **Highly Configurable**: Easily adapt to any environment, from dev to production
* 🛠 **Proven Stability**: Built for modern Kubernetes workflows

## Join the Community[​](#join-the-community "Direct link to Join the Community")

mlflow Helm is part of a vibrant open-source community. Whether you're a developer, DevOps engineer, or enthusiast, there are many ways to contribute:

* Browse configuration options in the [official mlflow docs](https://community-charts.github.io/docs/category/mlflow)
* Help improve the chart by submitting [pull requests](https://github.com/community-charts/helm-charts)
* Report bugs or share ideas in the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* Ask questions and collaborate with others deploying mlflow

Thank you for being part of the journey. Together, we’re making cloud-native mlflow deployments better for everyone!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-08-mlflow-chart-version-1-8-0-released.md)


---

# mlflow chart version 1.8.1 released

December 7, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **mlflow Helm chart version 1.8.1**, now available as of 2025-12-07. This version includes support for **mlflow application version 3.7.0** and brings helpful improvements and upgrades to the chart—making your deployments on Kubernetes even smoother.

## What’s New in mlflow 1.8.1[​](#whats-new-in-mlflow-181 "Direct link to What’s New in mlflow 1.8.1")

The 1.8.1 update includes key changes to both the Helm chart and its dependencies:

* 🛠️ **Updated**: Upgraded Docker image to `burakince/mlflow:3.7.0`
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)
* 🏗️ **Updated**: Bumped PostgreSQL chart dependency from `18.1.7` to `18.1.13`
  <br />
  <!-- -->
  → [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of updates and enhancements, check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.1) on GitHub.

<!-- -->

## Get Started with mlflow 1.8.1[​](#get-started-with-mlflow-181 "Direct link to Get Started with mlflow 1.8.1")

Ready to dive in? The [mlflow installation guide](https://community-charts.github.io/docs/category/mlflow) will help you get started quickly. You'll find:

* Simple steps for installing the chart with default settings
* Instructions for customizing values to fit your specific needs
* Recommendations for production-ready configurations

Visit the [documentation](https://community-charts.github.io/docs/category/mlflow) and get started today.

## Why Use the mlflow Helm Chart?[​](#why-use-the-mlflow-helm-chart "Direct link to Why Use the mlflow Helm Chart?")

The mlflow Helm chart—maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team—is designed to streamline the process of running mlflow on Kubernetes. Here’s why users love it:

* ✅ **Simplified Deployment**: Install and configure mlflow in minutes
* 🌱 **Community-Powered**: Continuously improved by open-source contributors
* 🔧 **Highly Configurable**: Tailor deployments to your project’s needs
* 🔐 **Kubernetes-Ready**: Engineered for stability and reliability

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The mlflow Helm chart is an open-source project—built with and for the community. Your feedback and contributions help shape its future.

* 📘 Learn more in the [official documentation](https://community-charts.github.io/docs/category/mlflow)
* 💡 Contribute code, improvements or fixes on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Found a bug? [Submit an issue](https://github.com/community-charts/helm-charts/issues)
* 🚀 Have an idea? [Request a feature](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the mlflow and Kubernetes ecosystem. We’re grateful for your continued support and collaboration!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-07-mlflow-chart-version-1-8-1-released.md)


---

# mlflow chart version 1.8.2 released

May 31, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the release of the **mlflow Helm chart version 1.8.2** on May 31, 2026, featuring **app version 3.12.0**! This update introduces a range of new features, enhancements, and community-driven improvements designed to simplify deploying mlflow on Kubernetes.

## What's New in mlflow 1.8.2 chart[​](#whats-new-in-mlflow-182-chart "Direct link to What's New in mlflow 1.8.2 chart")

This release includes significant updates to the Helm chart (version 1.8.2) along with the underlying application (version 3.12.0). Here’s a summary of the key changes:

* **Changed**: Updated the burakince/mlflow image version to 3.12.0
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/burakince/mlflow)
* **Changed**: Updated the dependency on PostgreSQL from version 18.1.13 to 18.6.10
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a complete list of changes, please check the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.2) on GitHub.

<!-- -->

## Getting Started with mlflow 1.8.2 chart[​](#getting-started-with-mlflow-182-chart "Direct link to Getting Started with mlflow 1.8.2 chart")

Are you ready to deploy mlflow 1.8.2? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/mlflow) offer step-by-step instructions to help you get started, including:

* Quick installation using default configurations.
* Customizing settings to best suit your environment.
* Best practices for ensuring successful production deployments.

Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to explore a variety of options and start deploying mlflow today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), provides a straightforward and reliable way to deploy mlflow on Kubernetes. Here are some key benefits:

* **Ease of Use**: Simplified installation and configuration processes.
* **Community-Driven**: Regular updates and enhancements from our dedicated contributors.
* **Flexibility**: Configurable options to accommodate diverse use cases.
* **Reliability**: Thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we warmly welcome your contributions! Whether you're fixing bugs, enhancing documentation, or suggesting new features, here’s how you can get involved:

* **Explore the Chart**: Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for configuration details.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your continued support of mlflow and GitHub Community Charts. Together, let’s make Kubernetes deployments easier and more efficient!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-05-31-mlflow-chart-version-1-8-2-released.md)


---

# Mlflow Chart Version 1.8.3 Released

May 31, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **mlflow Helm chart version 1.8.3** on May 31, 2026, featuring **app version 3.12.0**. This update introduces a range of new features, enhancements, and community-driven improvements designed to streamline your deployment of mlflow on Kubernetes.

## What's New in Mlflow 1.8.3 Chart[​](#whats-new-in-mlflow-183-chart "Direct link to What's New in Mlflow 1.8.3 Chart")

This release includes updates to both the Helm chart (version 1.8.3) and the underlying application (version 3.12.0). Here's a summary of the key changes:

* **Fixed**: Liveness and readiness probes now consistently use /health, regardless of staticPrefix.
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/290)

To explore the complete list of changes, please visit the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.3) on GitHub.

<!-- -->

## Getting Started with Mlflow 1.8.3 Chart[​](#getting-started-with-mlflow-183-chart "Direct link to Getting Started with Mlflow 1.8.3 Chart")

Are you ready to deploy mlflow 1.8.3? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) provide step-by-step instructions to ensure a smooth start, including:

* Quick installation with default configurations.
* Customization options to tailor settings to your environment.
* Best practices for successful production deployments.

Head over to the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to discover all the available options and deploy mlflow today.

## Why Choose the Mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the Mlflow Helm Chart?")

The mlflow Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed for straightforward and reliable deployment of mlflow on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy simplified installation and configuration processes.
* **Community-Driven**: Benefit from regular updates and improvements from our contributors.
* **Flexibility**: Utilize configurable options to meet various use cases.
* **Reliability**: Trust in a solution that is tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we wholeheartedly welcome your contributions! Whether you are fixing bugs, enhancing documentation, or suggesting new features, here's how you can get involved:

* **Explore the Chart**: Delve into the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement ideas through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting mlflow and GitHub Community Charts. Together, let's continue to make Kubernetes deployments easier and more efficient!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-05-31-mlflow-chart-version-1-8-3-released.md)


---

# mlflow chart version 1.8.4 launched

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the launch of the **mlflow Helm chart version 1.8.4** on June 2, 2026, which includes **app version 3.13.0**. This update introduces a range of new features, enhancements, and valuable community-driven improvements to make deploying mlflow on Kubernetes even more seamless.

## What’s New in mlflow 1.8.4 chart[​](#whats-new-in-mlflow-184-chart "Direct link to What’s New in mlflow 1.8.4 chart")

This release highlights updates to the Helm chart (version 1.8.4) alongside the underlying application (version 3.13.0). Here’s a brief overview of the changes:

* **Changed**: Updated the burakince/mlflow image version to 3.13.0
  <!-- -->
  * [Explore the Upstream Project](https://hub.docker.com/r/burakince/mlflow)
* **Changed**: Updated the postgresql dependency from 18.6.10 to 18.7.0
  <!-- -->
  * [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of changes, visit the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.4) on GitHub.

<!-- -->

## Getting Started with mlflow 1.8.4 chart[​](#getting-started-with-mlflow-184-chart "Direct link to Getting Started with mlflow 1.8.4 chart")

Are you ready to deploy mlflow 1.8.4? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) offer step-by-step instructions to help you get started, including:

* A quick installation process with default configurations.
* Customizing settings to align with your environment.
* Best practices for production-ready deployments.

Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to explore all the options available and deploy mlflow today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to simplify and enhance the deployment of mlflow on Kubernetes. Here are some key benefits:

* **Ease of Use**: Experience simplified installation and configuration.
* **Community-Driven**: Enjoy regular updates and enhancements driven by contributors.
* **Flexibility**: Access configurable options to accommodate various use cases.
* **Reliability**: Count on proven stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

Join us at GitHub Community Charts! This is a collaborative effort, and we value your contributions. Whether you are fixing bugs, enhancing documentation, or proposing new features, here’s how you can participate:

* **Explore the Chart**: Delve into our [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for detailed configuration information.
* **Contribute**: Submit your pull requests on our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encounter a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting mlflow and GitHub Community Charts. Together, let’s continue to enhance the ease of Kubernetes deployments!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-02-mlflow-chart-version-1-8-4-released.md)


---

# MLflow Chart Version 1.8.5 Released

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **MLflow Helm chart version 1.8.5** on June 2, 2026, featuring **app version 3.13.0**. This update brings a wealth of new features, enhancements, and community-driven improvements designed to streamline your MLflow deployment on Kubernetes.

## What's New in MLflow 1.8.5 Chart[​](#whats-new-in-mlflow-185-chart "Direct link to What's New in MLflow 1.8.5 Chart")

This release includes updates to both the Helm chart (version 1.8.5) and the underlying application (version 3.13.0). Here are some of the key changes:

* **Fixed**: Resolved broken screenshot URL(s) in the MLflow chart.

For a comprehensive list of changes, you can view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.5) on GitHub.

<!-- -->

## Getting Started with MLflow 1.8.5 Chart[​](#getting-started-with-mlflow-185-chart "Direct link to Getting Started with MLflow 1.8.5 Chart")

Are you ready to deploy MLflow 1.8.5? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) offer step-by-step instructions to help you get started, which include:

* Quick installation with default configurations.
* Customization options tailored to your environment.
* Best practices for successful production deployments.

Visit the [MLflow documentation](https://community-charts.github.io/docs/category/mlflow) to explore all available options and deploy MLflow today.

## Why Choose the MLflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the MLflow Helm Chart?")

The MLflow Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying MLflow on Kubernetes a straightforward and reliable experience. Here are a few reasons to choose it:

* **Ease of Use**: Simplified installation and configuration processes.
* **Community-Driven**: Regular updates and enhancements from dedicated contributors.
* **Flexibility**: Configurable options that meet diverse use cases.
* **Reliability**: Thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we invite you to be a part of it! Whether you're interested in fixing bugs, enhancing documentation, or proposing new features, there are many ways to contribute:

* **Explore the Chart**: Dive into the [MLflow documentation](https://community-charts.github.io/docs/category/mlflow) for configuration details.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of MLflow and GitHub Community Charts. Together, let's make Kubernetes deployments easier and more accessible!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-02-mlflow-chart-version-1-8-5-released.md)


---

# mlflow chart version 1.8.6 released

June 18, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **mlflow Helm chart version 1.8.6** on 2026-06-18, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements that make deploying mlflow on Kubernetes easier and more efficient.

## What's New in mlflow 1.8.6 chart[​](#whats-new-in-mlflow-186-chart "Direct link to What's New in mlflow 1.8.6 chart")

The latest release includes updates to the Helm chart (version 1.8.6) as well as the underlying application (version 3.14.0). Here are the highlights:

* **Changed**: Updated the burakince/mlflow image version to 3.14.0
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/burakince/mlflow)
* **Changed**: Upgraded the postgresql dependency from 18.7.0 to 18.7.5
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a detailed overview of all changes, check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.6) on GitHub.

<!-- -->

## Getting Started with mlflow 1.8.6 chart[​](#getting-started-with-mlflow-186-chart "Direct link to Getting Started with mlflow 1.8.6 chart")

Are you ready to deploy mlflow 1.8.6? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) offer step-by-step instructions to help you hit the ground running, including:

* Quick installations using default configurations.
* Customizing settings for your specific environment.
* Best practices for successful production deployments.

Dive into the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) to uncover all available options and start deploying mlflow today.

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to simplify and enhance the deployment of mlflow on Kubernetes. Here are some key advantages:

* **Ease of Use**: Streamlined installation and configuration process.
* **Community-Driven**: Receive regular updates and enhancements from enthusiastic contributors.
* **Flexibility**: Configurable options tailored for various use cases.
* **Reliability**: Thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

We invite you to be a part of the GitHub Community Charts project! Your contributions, whether fixing bugs, enhancing documentation, or proposing new features, are invaluable. Here’s how you can contribute:

* **Explore the Chart**: Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for detailed configuration options.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions on our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting mlflow and GitHub Community Charts. Together, let's make Kubernetes deployments smoother and more accessible!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-18-mlflow-chart-version-1-8-6-released.md)


---

# mlflow Helm Chart Version 1.9.0 Released

June 20, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **mlflow Helm chart version 1.9.0** on June 20, 2026, which includes the **app version 3.14.0**. This update introduces new features, enhancements, and improvements inspired by our vibrant community, making it easier than ever to deploy mlflow on Kubernetes.

## What's New in mlflow 1.9.0 Chart[​](#whats-new-in-mlflow-190-chart "Direct link to What's New in mlflow 1.9.0 Chart")

This release encompasses updates to both the Helm chart (version 1.9.0) and the underlying application (version 3.14.0). Here’s a summary of the key changes:

* **Added**: An optional oauth2-proxy sidecar for OIDC/OAuth2 authentication in front of MLflow, complete with configurable provider settings, secret management, and automatic Ingress port forwarding.
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/321)
* **Added**: An oidcAuth block for built-in OIDC authentication via the mlflow-oidc-auth plugin, including Redis cache and PostgreSQL user-database support.
  <!-- -->
  * [GitHub PR](https://github.com/community-charts/helm-charts/pull/328)

For a comprehensive list of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.9.0) on GitHub.

<!-- -->

## Getting Started with mlflow 1.9.0 Chart[​](#getting-started-with-mlflow-190-chart "Direct link to Getting Started with mlflow 1.9.0 Chart")

Eager to deploy mlflow 1.9.0? Our [installation guides](https://community-charts.github.io/docs/category/mlflow) offer step-by-step instructions to help you get started, including:

* Quick installation with default configurations.
* Customization options tailored to your environment.
* Best practices for successful production deployments.

Explore all the available options and start deploying mlflow today by visiting the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow).

## Why Choose the mlflow Helm Chart?[​](#why-choose-the-mlflow-helm-chart "Direct link to Why Choose the mlflow Helm Chart?")

The mlflow Helm chart, lovingly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is created to facilitate easy and reliable deployment of mlflow on Kubernetes. Here are some of the advantages:

* **Ease of Use**: Simplified installation and configuration process.
* **Community-Driven**: Regular updates and enhancements from passionate contributors.
* **Flexibility**: Configurable settings to suit a variety of use cases.
* **Reliability**: Tested for stability and performance in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

We invite you to be part of the GitHub Community Charts! Your contributions are invaluable, whether you're fixing bugs, enhancing documentation, or proposing new features. Here’s how you can contribute:

* **Explore the Chart**: Visit the [mlflow documentation](https://community-charts.github.io/docs/category/mlflow) for detailed configuration information.
* **Contribute**: Share your expertise by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting mlflow and GitHub Community Charts. Together, let’s continue to simplify Kubernetes deployments!

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-20-mlflow-chart-version-1-9-0-released.md)


---

# n8n chart version 1.10.0 now available

June 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **n8n Helm chart version 1.10.0**, launched on 2025-06-27 and powered by **application version 1.99.1**. This update introduces new features, usability enhancements, and community-requested improvements that make deploying n8n on Kubernetes easier and more flexible than ever.

## What’s New in Version 1.10.0[​](#whats-new-in-version-1100 "Direct link to What’s New in Version 1.10.0")

This release includes updates to both the Helm chart and the underlying application. Highlights from the changelog include:

* ✅ **Form Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/147)
* ✅ **MCP Server Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/148)
* ✅ **New flag introduced to enable or disable service as needed**

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.10.0) on GitHub.

<!-- -->

## Start Using n8n 1.10.0 Today[​](#start-using-n8n-1100-today "Direct link to Start Using n8n 1.10.0 Today")

Getting started with the new chart version is simple. Our [step-by-step installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* Quick setup using default settings
* Custom configuration tailored to your environment
* Best practices for stable production deployments

Visit the [n8n Docs](https://community-charts.github.io/docs/category/n8n) to learn more and launch your instance today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The official Helm chart for n8n, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is built to streamline your Kubernetes workflows. Key benefits include:

* 🚀 **User-Friendly Setup**: Simplified deployment and configuration
* 🤝 **Community-Driven**: Regularly updated by contributors around the world
* 🛠️ **Highly Configurable**: Easily adapt to your needs and architecture
* 🔒 **Proven Stability**: Built and tested for Kubernetes environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

GitHub Community Charts thrives because of users like you! Here’s how you can get involved:

* 📚 Check out the [documentation](https://community-charts.github.io/docs/category/n8n) for full configuration guidance
* ✨ Contribute via pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or problems in our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features or improvements through a [feature request](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the n8n community. Together, we’re making automation and deployment more accessible, powerful, and reliable!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-27-n8n-chart-version-1-10-0-released.md)


---

# n8n chart version 1.11.0 released

June 28, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of **n8n Helm chart version 1.11.0**, available as of **2025-06-28**, featuring the upgraded **app version 1.99.1**. This new version includes key updates and enhancements designed to make deploying n8n on Kubernetes easier and more flexible.

## What’s New in Version 1.11.0[​](#whats-new-in-version-1110 "Direct link to What’s New in Version 1.11.0")

This release introduces updates across the Helm chart and the core n8n application. Highlights include:

* 🛑 **Deprecated**: The root-level affinity field is now deprecated. Please use the affinity field within the `main`, `worker`, and `webhook` blocks instead. This change improves configuration flexibility and consistency.
  <!-- -->
  * [View Pull Request](https://github.com/community-charts/helm-charts/pull/150)
* ✅ **Added**: New `affinity` fields added to the `main`, `worker`, and `webhook` specification blocks.
  <!-- -->
  * [View Pull Request](https://github.com/community-charts/helm-charts/pull/150)

For the full list of updates, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.11.0).

<!-- -->

## Getting Started with n8n 1.11.0[​](#getting-started-with-n8n-1110 "Direct link to Getting Started with n8n 1.11.0")

Ready to deploy? Explore our [installation guides](https://community-charts.github.io/docs/category/n8n) for step-by-step instructions including:

* Quick installs with default configurations
* Customizing deployments for your environment
* Production-ready recommendations

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get started today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the n8n Helm chart is a reliable solution for deploying n8n in Kubernetes environments. Benefits include:

* 🚀 **Easy to Deploy**: Simplifies deployment and configuration
* 🤝 **Built by the Community**: Actively maintained and improved
* 🔧 **Highly Configurable**: Adapts to many use cases with flexible settings
* 🛡️ **Proven Stability**: Continuously tested for production environments

## Join Our Community[​](#join-our-community "Direct link to Join Our Community")

We welcome feedback, ideas, and contributions! Here's how you can get involved:

* 📘 Learn more from the [n8n documentation](https://community-charts.github.io/docs/category/n8n)
* 🔧 Contribute code or improvements via [pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or issues on our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Share your feature requests with us [here](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the n8n and GitHub Community Charts ecosystem. Together, we’re shaping the future of open-source workflow automation in Kubernetes!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-28-n8n-chart-version-1-11-0-released.md)


---

# n8n chart version 1.12.0 released

June 30, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the **n8n Helm chart, v1.12.0**, is now available as of 2025-06-30. This release includes the updated **n8n application version 1.99.1** and brings powerful new features and improvements that make deploying n8n on Kubernetes even easier.

## What’s New in the 1.12.0 Release[​](#whats-new-in-the-1120-release "Direct link to What’s New in the 1.12.0 Release")

The n8n chart version 1.12.0 introduces meaningful enhancements based on community feedback. Here's what’s been added in this release:

* ✔️ **Persistence support**<br /><!-- -->Enable persistent storage for more reliable deployments.<br />[See issue #94](https://github.com/community-charts/helm-charts/issues/94)

* ✔️ **hostAliases support**<br /><!-- -->Configure custom host-to-IP mappings within your pods.<br />[See issue #125](https://github.com/community-charts/helm-charts/issues/125)

For a full breakdown of updates, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.12.0) on GitHub.

<!-- -->

## Get Started with the n8n Helm Chart[​](#get-started-with-the-n8n-helm-chart "Direct link to Get Started with the n8n Helm Chart")

Ready to upgrade or deploy n8n for the first time? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) will walk you through:

* Quick setup using default configurations
* Customizing deployments for your specific needs
* Following best practices for production environments

Visit the [official docs](https://community-charts.github.io/docs/category/n8n) to start deploying n8n today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The n8n Helm chart, maintained by the [GitHub Community Charts project](https://github.com/community-charts/helm-charts), offers a reliable and flexible way to run n8n on Kubernetes. Here’s what makes it stand out:

* 🚀 **Simple Setup**: Get up and running quickly with minimal effort
* 💬 **Community Driven**: Built and improved by passionate contributors
* 🔧 **Highly Configurable**: Supports a wide range of deployment scenarios
* ✅ **Battle-Tested**: Proven in real-world Kubernetes environments

## Contribute and Collaborate[​](#contribute-and-collaborate "Direct link to Contribute and Collaborate")

We’re proud to be part of an open-source community, and we’d love for you to get involved. Here’s how you can contribute:

* 📖 Explore the [n8n documentation](https://community-charts.github.io/docs/category/n8n)
* 💻 Submit pull requests to the [Helm charts GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or issues [here](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you for supporting n8n and the GitHub Community Charts initiative. Together, we’re simplifying cloud-native automation—one chart at a time!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-30-n8n-chart-version-1-12-0-released.md)


---

# n8n chart version 1.12.1 now available

July 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart — **v1.12.1**, featuring **app version 1.100.1** — is now live as of 2025-07-01! This release introduces several improvements aimed at delivering a smoother, more flexible n8n deployment experience on Kubernetes.

## What’s included in the 1.12.1 release[​](#whats-included-in-the-1121-release "Direct link to What’s included in the 1.12.1 release")

The 1.12.1 chart update brings enhancements to both the Helm chart and the associated n8n application. Here’s what’s new:

* ✅ **Updated**: n8nio/n8n image upgraded to version 1.100.1
  <br />
  <!-- -->
  → View on [GitHub](https://github.com/n8n-io/n8n)
* ✅ **Updated**: Redis dependency bumped from 21.2.5 to 21.2.6
  <br />
  <!-- -->
  → View on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* ✅ **Updated**: PostgreSQL dependency upgraded from 16.7.13 to 16.7.14
  <br />
  <!-- -->
  → View on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of updates, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.12.1) on GitHub.

<!-- -->

## How to get started with n8n 1.12.1[​](#how-to-get-started-with-n8n-1121 "Direct link to How to get started with n8n 1.12.1")

Ready to deploy? Our [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* Quick-start installation using default values
* How to tailor your configuration for specific needs
* Recommended practices for stable production environments

Head over to the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to begin your deployment journey.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart is designed to make Kubernetes deployments as smooth as possible. Benefits include:

* 🚀 **Simple Setup**: Easy to install and configure
* 🔧 **Highly Configurable**: Adaptable to many different environments
* 🤝 **Built by the Community**: Contributions from users around the world
* 🔒 **Production Ready**: Battle-tested in Kubernetes clusters

## Join the community[​](#join-the-community "Direct link to Join the community")

We’re a community-driven project—and we’d love your help! Whether you want to contribute features, improve documentation, or report bugs, there are many ways to get involved:

* 📘 Browse the [n8n docs](https://community-charts.github.io/docs/category/n8n) for setup and configuration details
* ✍️ Submit pull requests in our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs on our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest ideas and enhancements [here](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the n8n and GitHub Community Charts journey. Let’s keep making Kubernetes deployments better—together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-01-n8n-chart-version-1-12-1-released.md)


---

# n8n chart version 1.12.2 released

July 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.12.2,** available as of 2025-07-01, powered by the latest **application version 1.100.1**. This update brings valuable enhancements and community-driven fixes, making it even easier and more reliable to run n8n on Kubernetes.

## What's New in n8n 1.12.2 chart[​](#whats-new-in-n8n-1122-chart "Direct link to What's New in n8n 1.12.2 chart")

This release contains important improvements in both the Helm chart (v1.12.2) and the underlying n8n app (v1.100.1). Key highlight:

* 🛠️ **Fix**: Corrects volumeName handling for both main and worker pods when a custom value is provided.
  <!-- -->
  * [GitHub Issue #154](https://github.com/community-charts/helm-charts/issues/154)

To see every change included in this release, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.12.2).

<!-- -->

## Get Started with n8n 1.12.2[​](#get-started-with-n8n-1122 "Direct link to Get Started with n8n 1.12.2")

Deploying the latest version is simple! Our comprehensive [documentation](https://community-charts.github.io/docs/category/n8n) guides you through:

* Quick and easy default installation.
* Configuring the chart for your environment.
* Following best practices for production-grade deployments.

Whether you're just getting started or upgrading your current setup, everything you need is in the [n8n docs](https://community-charts.github.io/docs/category/n8n).

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The official n8n Helm chart, maintained by the open-source contributors at [GitHub Community Charts](https://github.com/community-charts/helm-charts), offers:

* ✅ **Simplicity**: Deploy n8n on Kubernetes with minimal effort.
* 💡 **Community-Driven**: Shaped by feedback and contributions from real users.
* 🔧 **Highly Configurable**: Tailor deployments to your specific needs.
* 🔒 **Reliability**: Built and tested for stable production use cases.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’d love for you to be a part of the GitHub Community Charts project! There are many ways to get involved:

* 🧭 Explore the [n8n chart docs](https://community-charts.github.io/docs/category/n8n).
* 🛠️ Contribute improvements via [pull requests](https://github.com/community-charts/helm-charts).
* 🐞 Report bugs and track issues on our [issue board](https://github.com/community-charts/helm-charts/issues).
* 💡 Submit feature requests in the [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being part of the n8n and Kubernetes ecosystem. Let’s keep building great tools—together.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-01-n8n-chart-version-1-12-2-released.md)


---

# n8n Helm chart 1.12.3 now available

July 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that version 1.12.3 of the **n8n Helm chart** is now live as of July 2, 2025, featuring **app version 1.100.1**. This release introduces new features, key improvements, and refinements inspired by feedback from our community—making it even easier to deploy n8n on Kubernetes.

## What’s new in version 1.12.3[​](#whats-new-in-version-1123 "Direct link to What’s new in version 1.12.3")

This release includes updates to both the Helm chart (v1.12.3) and the core application (v1.100.1). Here's a summary of the changes:

* ✅ Removed limitation: Support for flexible binary data bucket region configuration
  <!-- -->
  * See the full details in the [GitHub PR](https://github.com/community-charts/helm-charts/pull/159)

For a complete breakdown of updates, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.12.3).

<!-- -->

## Getting started with Helm chart 1.12.3[​](#getting-started-with-helm-chart-1123 "Direct link to Getting started with Helm chart 1.12.3")

Ready to get started with the latest n8n chart? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through everything you need to know, including:

* Step-by-step setup using default values
* Advanced configuration to tailor your deployment
* Production-ready best practices for Kubernetes

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to begin your deployment journey.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart is designed to take the complexity out of Kubernetes deployments. Here’s why it stands out:

* 🧩 Easy Deployment: Simple, quick setup to get n8n running
* 🌍 Community-Powered: Built with contributions from users like you
* ⚙️ Flexible Options: Configure to suit diverse environments
* ✅ Stable & Reliable: Trusted and tested for production workloads

## Join our community[​](#join-our-community "Direct link to Join our community")

The n8n Helm chart is a collaborative open-source project, and your involvement makes it stronger. Whether you’re contributing code, sharing ideas, or reporting issues—here’s how to get involved:

* Learn more in the [official documentation](https://community-charts.github.io/docs/category/n8n)
* Make a difference with a [pull request](https://github.com/community-charts/helm-charts)
* Help us improve by [reporting an issue](https://github.com/community-charts/helm-charts/issues)
* Share your ideas via our [feature request form](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being a part of the n8n community. Let’s keep building great things together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-02-n8n-chart-version-1-12-3-released.md)


---

# n8n chart 1.13.0 update is here

July 6, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the n8n Helm chart — **version 1.13.0**, published on July 6, 2025! While the app version is currently undefined, this update introduces several valuable improvements that enhance the experience of deploying n8n on Kubernetes.

## What’s new in version 1.13.0[​](#whats-new-in-version-1130 "Direct link to What’s new in version 1.13.0")

The Helm chart (v1.13.0) includes multiple additions, fixes, and enhancements based on community feedback. Here's a quick overview of the highlights:

* ✅ **Fixed:** Resolved an issue with MCP connections handling multiple webhooks<br /><!-- -->→ [View GitHub Issue](https://github.com/community-charts/helm-charts/issues/165)

* 🆕 **Added:** New field for defining service labels

* 🆕 **Added:** Option to enable or disable MCP Webhooks

* 🔁 **Changed:** Main pod labels now use main.name and main.fullname for better consistency

* 🆕 **Added:** Configurable runtimeClassName for main, worker, and webhook pods

Find the complete list and technical details in our official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.0).

<!-- -->

## Quick start with Helm chart 1.13.0[​](#quick-start-with-helm-chart-1130 "Direct link to Quick start with Helm chart 1.13.0")

Thinking of updating or deploying n8n with the latest chart? Our comprehensive [documentation](https://community-charts.github.io/docs/category/n8n) offers everything you need to get going:

* One-command installation with default values
* Simple steps for custom configuration
* Guidelines for production-grade deployments in Kubernetes environments

Whether you're running on Minikube, EKS, or another cloud provider, our guides have you covered.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Our open-source Helm chart is built to streamline DevOps workflows and CI/CD pipelines for the n8n automation platform in Kubernetes. It offers:

* 🚀 Easy setup and upgrades
* 🤝 Actively maintained by a supportive open-source community
* ⚙️ Fully customizable to suit complex environments
* 🛡️ Robust and production-ready templates

Hosted and maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), our goal is to help developers and teams deploy automated workflows with confidence.

## Join the community[​](#join-the-community "Direct link to Join the community")

We’d love for you to be part of the journey! There are many ways you can contribute and connect:

* 📘 Read the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get familiar with features and options
* 🛠️ Submit a pull request or explore open issues on our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or request new features via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the open-source community—let's keep making Kubernetes deployments for automation easier and more powerful!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-06-n8n-chart-version-1-13-0-released.md)


---

# n8n chart version 1.13.10 available now

August 7, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the latest release of the **n8n Helm chart, version 1.13.10**, is now available as of 2025-08-07, introducing **n8n app version 1.105.4**. This update includes important enhancements and improvements, making it even easier to deploy and manage n8n on Kubernetes.

## What's new in Helm chart 1.13.10[​](#whats-new-in-helm-chart-11310 "Direct link to What's new in Helm chart 1.13.10")

This version includes an updated application version and key refinements aimed at improving stability and usability:

* 🛠 **Updated**: Docker image version upgraded to `n8nio/n8n:1.105.4`
  * View the app on [GitHub](https://github.com/n8n-io/n8n)

To see the complete release changelog, check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.10).

<!-- -->

## Getting started with version 1.13.10[​](#getting-started-with-version-11310 "Direct link to Getting started with version 1.13.10")

Ready to deploy the latest version of n8n? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through everything you need:

* Quick start installation using default values
* How to configure and customize the deployment
* Best practices for production environments

Take a deep dive into the [n8n Helm chart documentation](https://community-charts.github.io/docs/category/n8n) and start building with confidence.

## Why choose the n8n Helm chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why choose the n8n Helm chart?")

Developed and maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), the n8n Helm chart aligns with modern DevOps practices for Kubernetes deployments:

* ✅ **Simple and flexible**: Easy configuration for a wide range of use cases
* 🔄 **Actively maintained**: Community-driven enhancements and updates
* ⚙️ **Fully customizable**: Tailor to your operational and security requirements
* 🧪 **Tested reliability**: Designed for consistent performance on Kubernetes

Whether you're automating data flows or integrating cloud services, this chart simplifies your DevOps workflow.

## Contribute to the community[​](#contribute-to-the-community "Direct link to Contribute to the community")

n8n Helm chart is an open-source project powered by people like you. Here's how to get involved:

* 📘 Review the [n8n chart docs](https://community-charts.github.io/docs/category/n8n) to explore its configuration
* 🔧 Submit your improvements via pull requests to our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Found a bug? Report it on the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Have an idea? We'd love to hear it—share on the [feature request board](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being a part of the growing open-source community. Let’s continue shaping the future of automation infrastructure—together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-07-n8n-chart-version-1-13-10-released.md)


---

# n8n chart version 1.13.2 released

July 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.13.2**, available as of **July 8, 2025**, featuring **app version 1.101.1**. This update brings valuable enhancements and community-driven refinements to help you deploy n8n with confidence on Kubernetes.

## What’s New in n8n 1.13.2[​](#whats-new-in-n8n-1132 "Direct link to What’s New in n8n 1.13.2")

This latest chart release delivers improvements to both the Helm chart and its core dependencies. Here’s what’s new:

* 🔄 **n8n Image Updated**: Upgraded to version `1.101.1`
  <br />
  <!-- -->
  → [View n8n on GitHub](https://github.com/n8n-io/n8n)
* ⬆️ **Redis Dependency Updated**: From `21.2.6` to `21.2.7`
  <br />
  <!-- -->
  → [View Redis Chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* ⬆️ **PostgreSQL Dependency Updated**: From `16.7.14` to `16.7.15`
  <br />
  <!-- -->
  → [View PostgreSQL Chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of updates and technical notes, check out the [official release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.2).

<!-- -->

## Get Started with n8n 1.13.2[​](#get-started-with-n8n-1132 "Direct link to Get Started with n8n 1.13.2")

Thinking about giving it a try? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) make deployment simple, whether you're just starting out or running n8n in a production environment.

Here’s what you’ll find:

* Easy one-command installation
* Custom configuration examples
* Best practices for scalable, secure Kubernetes deployments

Explore the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get started today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), this Helm chart empowers you to run n8n reliably on your Kubernetes clusters. It’s built with DevOps best practices in mind and offers:

* 🧩 Easy setup and customization
* 🤝 Active community support
* 🔧 Flexible, production-ready configurations
* ✅ Regular updates and proven stability

Whether you're automating workflows for personal use or deploying n8n at scale, this chart is designed to save time and reduce complexity.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We love collaborating with contributors and welcome your involvement! Whether it’s improving documentation, fixing bugs, or requesting features, your input helps us grow and improve.

Here’s how you can contribute:

* 💡 Learn more in the [n8n configuration guide](https://community-charts.github.io/docs/category/n8n)
* 🔧 Submit improvements on [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report issues or bugs in our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 🌟 Suggest new features and enhancements

Thank you for being part of the open-source ecosystem. Let’s keep making Kubernetes automation easier—together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-08-n8n-chart-version-1-13-2-released.md)


---

# n8n chart version 1.13.3 released

July 15, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest update of the **n8n Helm chart—version 1.13.3**—is now available as of July 15, 2025! This release ships with **n8n application version 1.102.3**, bringing improvements and fresh updates to streamline your Kubernetes deployments.

## What’s New in Helm Chart 1.13.3[​](#whats-new-in-helm-chart-1133 "Direct link to What’s New in Helm Chart 1.13.3")

Here’s a look at what’s included in this release of the n8n Helm chart (v1.13.3):

* 🔄 **Updated:** Application image bumped to `n8nio/n8n:1.102.3`<br /><!-- -->→ See the [n8n project on GitHub](https://github.com/n8n-io/n8n)

* 📦 **Upgraded:** Redis dependency updated from 21.2.7 → 21.2.11<br /><!-- -->→ View on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 💾 **Upgraded:** PostgreSQL dependency updated from 16.7.15 → 16.7.19<br /><!-- -->→ View on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Curious about all the changes? Head over to the official [n8n 1.13.3 release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.3).

<!-- -->

## Getting Started with n8n 1.13.3[​](#getting-started-with-n8n-1133 "Direct link to Getting Started with n8n 1.13.3")

Ready to deploy the latest n8n chart? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* ✅ Quick setup with recommended defaults
* ⚙️ Customizing values to match your environment
* 📈 Deployment strategies for production scenarios

Get started today by visiting our [n8n documentation](https://community-charts.github.io/docs/category/n8n)—built to make your Helm experience effortless.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), the n8n Helm chart offers:

* 🚀 Easy installation and upgrades on Kubernetes
* 🌍 Community contributions and transparent development
* 🛠️ Configurable options to match unique workflows
* 🔒 Production-ready deployments with top-tier dependencies like Redis and PostgreSQL

Whether you're running workflows for automation, integration, or DevOps, the chart brings flexibility and stability to your stack.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Our chart is open-source and community-driven—we’d love to have you on board!

* 📘 Learn configuration options in our [official docs](https://community-charts.github.io/docs/category/n8n)
* 🤝 Contribute to the project on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or request features via our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you for being part of the open-source journey. Let’s keep building better tools—together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-15-n8n-chart-version-1-13-3-released.md)


---

# n8n chart version 1.13.4 released

July 17, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **n8n Helm chart version 1.13.4**, available as of **July 17, 2025**. This version includes **app version 1.102.4**, bringing useful updates and improvements that make deploying and managing n8n on Kubernetes even more reliable and flexible.

## What’s New in Chart 1.13.4[​](#whats-new-in-chart-1134 "Direct link to What’s New in Chart 1.13.4")

This release updates both the Helm chart and core application, enhancing stability and compatibility:

* 🔄 **Image Updated**: Upgraded container image to `n8nio/n8n:1.102.4`
  <br />
  <!-- -->
  → Explore the [upstream project](https://github.com/n8n-io/n8n)
* 🧱 **Redis Dependency Bumped**: Upgraded Redis chart from version `21.2.11` to `21.2.12`
  <br />
  <!-- -->
  → See the [ArtifactHub package page](https://artifacthub.io/packages/helm/bitnami/redis)

For full details, check out the official [v1.13.4 release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.4) on GitHub.

<!-- -->

## Get Started with n8n 1.13.4[​](#get-started-with-n8n-1134 "Direct link to Get Started with n8n 1.13.4")

Want to deploy n8n using Helm? We've got everything you need to get up and running quickly:

* 🛠️ Simple default installation
* ⚙️ Flexible configuration to fit every environment
* 🚀 Proven deployment tips for production readiness

Visit our [n8n installation docs](https://community-charts.github.io/docs/category/n8n) to get started today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Backed by the open-source community, the n8n Helm chart is your go-to tool for Kubernetes-native deployments of n8n:

* ✅ Effortless configuration with built-in defaults
* 🌐 Community-maintained with regular updates
* 🔧 Fully customizable to suit any workflow
* 🔒 Trusted for stability in cloud-native platforms

Maintained by the team at [GitHub Community Charts](https://github.com/community-charts/helm-charts), this chart is ideal for both production and development environments.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The success of this project relies on contributors like you! Here’s how you can get involved:

* 📚 Learn more in our [n8n chart documentation](https://community-charts.github.io/docs/category/n8n)
* 🛠️ Contribute via [pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs or issues on our [GitHub tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features or enhancements with a [feature request](https://github.com/community-charts/helm-charts/issues/new)

Thank you for supporting n8n and the open-source community powering Kubernetes. Together, we’re building better automation for everyone.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-17-n8n-chart-version-1-13-4-released.md)


---

# n8n chart version 1.13.5 released

July 23, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.13.5**, available now as of July 23, 2025! This version includes the latest **app version 1.103.2**, along with several key improvements to help you streamline your workflows and enhance Kubernetes deployment experiences.

<!-- -->

## Highlights of n8n 1.13.5[​](#highlights-of-n8n-1135 "Direct link to Highlights of n8n 1.13.5")

This release brings a series of updates to both the Helm chart and its core application to support better performance, reliability, and maintainability:

* ✅ **App Version Updated**: Upgraded Docker image to `n8nio/n8n:1.103.2`.<br /><!-- -->→ [View upstream project](https://github.com/n8n-io/n8n)

* 🔄 **Redis Dependency Updated**: Bumped Redis chart from `21.2.12` to `21.2.13`.<br /><!-- -->→ [Check on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 📦 **PostgreSQL Enhancement**: Updated PostgreSQL chart from `16.7.19` to `16.7.21`.<br /><!-- -->→ [Check on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of updates and technical notes, see the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.5).

## Get Started with n8n on Kubernetes[​](#get-started-with-n8n-on-kubernetes "Direct link to Get Started with n8n on Kubernetes")

Deploying n8n on your Kubernetes cluster has never been easier! Our updated [installation guide](https://community-charts.github.io/docs/category/n8n) will walk you through:

* 🚀 Quick setup using default values.
* ⚙️ Custom configurations tailored to your environment.
* 🛡️ Best practices for stable, production-ready installations.

Explore the documentation now and start automating with n8n in just a few steps!

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), the n8n Helm chart delivers:

* 🧩 Easy installation & upgrades with Helm.
* 🤝 Community contributions driving constant improvements.
* 🔧 Flexible, configurable deployments.
* 🧪 Tested reliability within Kubernetes environments.

Whether you're setting up a small internal automation tool or a business-critical workflow engine, the n8n helm chart makes it efficient and resilient.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We're always looking for passionate contributors to help improve our Helm charts and documentation. Here’s how you can get involved:

🔍 Explore our [n8n Helm docs](https://community-charts.github.io/docs/category/n8n)<br /><!-- -->🛠 Contribute via [GitHub pull requests](https://github.com/community-charts/helm-charts)<br /><!-- -->🐞 Report bugs or request features in our [Issue Tracker](https://github.com/community-charts/helm-charts/issues)

Together, we’re building a better open-source future for automation on Kubernetes. Thank you for being part of the journey!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [Redis](/blog/tags/redis.md "Configure your applications with Redis for caching, queueing, and real-time data, including managed Redis on major cloud providers.")
* [Postgres](/blog/tags/postgres.md "Learn how to configure applications with PostgreSQL for reliable data storage, including guides for managed PostgreSQL on AWS, Google Cloud, and Azure.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-23-n8n-chart-version-1-13-5-released.md)


---

# n8n Helm chart 1.13.6 now available

July 28, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.13.6**, available as of **July 28, 2025**, and featuring **app version 1.104.1**. This update brings helpful improvements and new features that further streamline deploying n8n in your Kubernetes environments.

<!-- -->

## What’s New in n8n Chart 1.13.6[​](#whats-new-in-n8n-chart-1136 "Direct link to What’s New in n8n Chart 1.13.6")

This release updates both the Helm chart to version **1.13.6** and aligns with the latest **n8n application version 1.104.1**.

Highlights include:

* 🆕 **Image update**: Upgraded to the latest `n8nio/n8n:1.104.1` image
  <!-- -->
  * See more at the [n8n upstream project](https://github.com/n8n-io/n8n)

For complete details, check out the [chart release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.6).

## How to Deploy n8n with Helm[​](#how-to-deploy-n8n-with-helm "Direct link to How to Deploy n8n with Helm")

Getting started with the new chart version is simple. Follow our [step-by-step documentation](https://community-charts.github.io/docs/category/n8n) to deploy n8n on Kubernetes effectively:

* Install quickly using default settings
* Customize configurations to fit your environment
* Apply best practices for production use

Whether you're setting up a test environment or launching into production, our guides are here to support a smooth deployment.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart is a powerful tool designed to simplify Kubernetes deployments. Here’s why users love it:

* 🚀 **Easy Setup**: Get started with minimal effort
* 🔧 **Highly Configurable**: Flexible options support various workflows
* 🤝 **Community Powered**: Built and improved by open-source contributors
* 🛡️ **Kubernetes Ready**: Tested and optimized for reliable deployments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We welcome your contributions of any kind! Whether you’re submitting a bug fix, adding a new feature, or improving the docs, the community thrives with your involvement.

Here’s how to participate:

* 📖 Review the [n8n configuration docs](https://community-charts.github.io/docs/category/n8n)
* 💻 Contribute via [Pull Requests](https://github.com/community-charts/helm-charts)
* 🐞 Found an issue? [Report it here](https://github.com/community-charts/helm-charts/issues)
* 💡 Got an idea? [Request a feature](https://github.com/community-charts/helm-charts/issues/new)

Thanks to the entire community for making this chart a success. Let’s keep building great tools for the Kubernetes ecosystem together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-28-n8n-chart-version-1-13-6-released.md)


---

# n8n chart version 1.13.7 now available

July 31, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest n8n Helm chart — version **1.13.7**, published on **July 31, 2025**, featuring **n8n app version 1.104.2**. This update delivers important improvements and community-driven enhancements, making it even easier to deploy and manage n8n on Kubernetes.

## What’s new in version 1.13.7[​](#whats-new-in-version-1137 "Direct link to What’s new in version 1.13.7")

This version focuses on keeping your deployments up to date with the latest application version and ensuring seamless Kubernetes integration. Here’s what’s included in this release:

* 🔄 **Updated**: n8nio/n8n image upgraded to version 1.104.2
  <br />
  <!-- -->
  ➝ [Explore the upstream project](https://github.com/n8n-io/n8n)

Check out the full changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.7) for a detailed breakdown.

<!-- -->

## Get started with the n8n 1.13.7 chart[​](#get-started-with-the-n8n-1137-chart "Direct link to Get started with the n8n 1.13.7 chart")

Ready to upgrade or deploy n8n using the new Helm chart? Our comprehensive [setup documentation](https://community-charts.github.io/docs/category/n8n) guides you through everything you need:

* 🚀 Quick and easy installation with defaults
* ⚙️ Custom configuration for different environments
* 🛠️ Production-ready best practices

Whether you're just starting out or scaling to production, we've got you covered.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Managed by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart brings powerful capabilities to automation workflows on Kubernetes. Some of the core benefits include:

* ✅ Simple, user-friendly deployment with Helm
* 🌍 Backed by a vibrant open-source community
* 🔧 Flexible chart values for a variety of use cases
* 🧪 Regularly tested in real Kubernetes setups

This chart is built to ensure your automation tools run smoothly and efficiently.

## Contribute & collaborate[​](#contribute--collaborate "Direct link to Contribute & collaborate")

The n8n Helm chart is driven by a passionate open-source community — and you’re invited to be part of it! Whether you're writing documentation, adding features, or helping debug, every contribution is valued.

Here’s how to get involved:

* 📘 Explore the full [n8n Helm docs](https://community-charts.github.io/docs/category/n8n)
* 🛠️ Contribute via [pull requests on GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs or request features in the [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you to all our contributors and users for making n8n on Kubernetes better with every release!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-31-n8n-chart-version-1-13-7-released.md)


---

# n8n chart version 1.13.8 released

August 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest stable version of the **n8n Helm chart — version 1.13.8**, published on August 4, 2025! This release includes **n8n app version 1.105.2**, with valuable upgrades and refinements to improve your workflow automation experience on Kubernetes.

## What’s new in Helm chart 1.13.8?[​](#whats-new-in-helm-chart-1138 "Direct link to What’s new in Helm chart 1.13.8?")

In this version, both the chart and its dependencies have been refreshed to deliver a more secure and reliable deployment experience.

* ✅ **Updated**: n8n image version is now 1.105.2
  <br />
  <!-- -->
  → Check out the upstream repo: [n8n GitHub](https://github.com/n8n-io/n8n)
* 🔁 **Updated**: Redis dependency upgrade from 21.2.13 to 21.2.14
  <br />
  <!-- -->
  → View it on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For a complete breakdown, see the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.8) on GitHub.

<!-- -->

## Get started with n8n 1.13.8[​](#get-started-with-n8n-1138 "Direct link to Get started with n8n 1.13.8")

Want to deploy n8n on your Kubernetes cluster with the latest improvements? We’ve got everything you need in our helpful [docs](https://community-charts.github.io/docs/category/n8n):

* 🚀 Step-by-step installation using default values.
* ⚙️ Configuring the chart to meet your specific needs.
* 🛡️ Production-ready considerations and best practices.

Set up n8n effortlessly and start building powerful, automated workflows—all within your Kubernetes environment.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the n8n Helm chart offers:

* 🔧 Easy setup with minimal configuration required
* 🤝 Regular updates and improvements powered by community collaboration
* 🧩 Configurable design to fit dev, staging, or production use cases
* 🪨 A stable and resilient platform for your automation workflows

With support from the Kubernetes and open-source community, the n8n chart helps bring scalable automation to your infrastructure.

## Join the community[​](#join-the-community "Direct link to Join the community")

Got a feature suggestion or idea to improve the chart? We'd love to hear from you! Here's how to get involved:

* 📚 Read our full [n8n chart documentation](https://community-charts.github.io/docs/category/n8n)
* 🤓 Contribute to the Helm chart via [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or missing features on our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Propose new improvements or integrations anytime

Thank you to all contributors who help keep n8n running smoothly in cloud-native environments. Let’s build better, automated systems—together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-04-n8n-chart-version-1-13-8-released.md)


---

# n8n chart version 1.13.9 released

August 5, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce that the latest version of the n8n Helm chart, **v1.13.9**, is now available! Released on August 5, 2025, this update ships with **app version 1.105.3**, delivering performance updates and community-driven improvements to streamline your Kubernetes workflow automation.

## What’s New in Chart v1.13.9[​](#whats-new-in-chart-v1139 "Direct link to What’s New in Chart v1.13.9")

This version brings the following update:

* Updated container image to **n8nio/n8n:1.105.3**
  * Source: [n8n GitHub Repository](https://github.com/n8n-io/n8n)

For a complete list of changes, see the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.9) on GitHub.

<!-- -->

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Ready to deploy n8n using Helm? Whether you’re new to Kubernetes or scaling across environments, our step-by-step [installation guides](https://community-charts.github.io/docs/category/n8n) make it easy:

* Perform a quick start with default settings.
* Customize configurations to fit your specific needs.
* Follow best practices for production-ready deployments.

Explore the full [n8n documentation](https://community-charts.github.io/docs/category/n8n) and start building workflows effortlessly.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), this Helm chart is built to simplify and enhance the Kubernetes deployment experience for n8n. Key advantages include:

* 🚀 **Simple Setup**: Get up and running in just a few commands.
* 🔄 **Community-Powered**: Continuously improved by open-source contributors.
* ⚙️ **Highly Configurable**: Adaptable for a wide range of environments.
* 🧪 **Proven Stability**: Tested with modern Kubernetes infrastructures.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The n8n Helm chart thrives thanks to active contributions from people like you! Here’s how you can get involved:

* Read the [documentation](https://community-charts.github.io/docs/category/n8n) to understand available options.
* Contribute code, guides, or improvements via [pull requests](https://github.com/community-charts/helm-charts).
* Report bugs or request features through our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* Share your deployment experience or ideas with the community.

Thank you for supporting n8n and the open-source Helm community. Let’s keep building great things—together.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-05-n8n-chart-version-1-13-9-released.md)


---

# n8n chart version 1.14.0 released

August 11, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart—**v1.14.0**—is now available as of 2025-08-11, featuring **app version 1.105.4**. This release delivers valuable enhancements and community-driven fixes to streamline your n8n deployments on Kubernetes.

<!-- -->

## What’s New in Chart v1.14.0[​](#whats-new-in-chart-v1140 "Direct link to What’s New in Chart v1.14.0")

This update includes important refinements to the chart and application, with a primary focus on improved persistence management:

* ✅ **Persistence Fix**: Resolved an issue preventing Persistent Volume Claims (PVCs) from being created when using multiple main node replicas with ReadWriteMany-enabled storage.
  <!-- -->
  * [View GitHub Issue](https://github.com/community-charts/helm-charts/issues/203)

Explore the full changelog by visiting the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.14.0) on GitHub.

## Set Up with Helm in Minutes[​](#set-up-with-helm-in-minutes "Direct link to Set Up with Helm in Minutes")

Getting started with the n8n Helm chart is quick and easy. Our comprehensive [installation documentation](https://community-charts.github.io/docs/category/n8n) walks you through:

* Fast setup using default values.
* Advanced configuration for team-specific needs.
* Tips for scaling and securing production environments.

Whether you’re experimenting or launching at scale, we’ve got the tooling and flexibility to support your Kubernetes journey.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the community via [GitHub Community Charts](https://github.com/community-charts/helm-charts), this Helm chart is built to simplify and strengthen your n8n experience in Kubernetes:

* 🔧 **Easy to Customize**: Tailor settings without hassle.
* 🤝 **Built by the Community**: Constantly improved by open-source contributors.
* 🔄 **Flexible Deployments**: Handles a variety of use cases and environments.
* ✅ **Production-Ready**: Battle-tested for stability and reliability.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We invite you to be part of this open-source journey. Whether you're a DevOps pro or just getting started, your contributions help shape better Kubernetes tooling for everyone:

* 🔍 [Explore the Documentation](https://community-charts.github.io/docs/category/n8n)
* 🤓 [Contribute on GitHub](https://github.com/community-charts/helm-charts)
* 🐛 [Report an Issue](https://github.com/community-charts/helm-charts/issues)
* 💡 [Request a Feature](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the Helm and Kubernetes community. Let’s keep building and collaborating to make deployment smoother for all!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-11-n8n-chart-version-1-14-0-released.md)


---

# n8n chart version 1.14.1 released

August 11, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the n8n Helm chart has been updated to version **1.14.1**, featuring **app version 1.106.3**, as of 2025-08-11. This release introduces enhanced capabilities, fresh dependency upgrades, and continued support from the open-source community—all helping you streamline n8n deployments on Kubernetes.

## What’s new in version 1.14.1[​](#whats-new-in-version-1141 "Direct link to What’s new in version 1.14.1")

This release includes updates to both the chart and underlying application. Here’s what’s changed:

* ✅ **Updated** image to `n8nio/n8n:1.106.3`<br /><!-- -->→ Check out the [n8n source code](https://github.com/n8n-io/n8n)

* ✅ **Upgraded** Redis dependency from `21.2.14` to `22.0.1`<br /><!-- -->→ View details on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* ✅ **Updated** PostgreSQL dependency from `16.7.21` to `16.7.24`<br /><!-- -->→ Explore the chart on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Get the full breakdown in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.14.1).

<!-- -->

## Getting started with Helm chart 1.14.1[​](#getting-started-with-helm-chart-1141 "Direct link to Getting started with Helm chart 1.14.1")

Ready to upgrade or deploy n8n for the first time? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* Quick start deployments with sensible defaults
* Customizing configurations to fit your workflow
* Production-ready setup and scaling tips

Whether you're launching n8n on a dev cluster or in a high-availability setup, this release has you covered.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart delivers a robust and flexible way to run your automation workflows on Kubernetes. Here’s why developers and teams trust it:

* 🧭 Simple, fast installation
* 💬 Backed by an active open-source community
* 🛠️ Designed for customization and extensibility
* 🔒 Built with stability and reliability in mind

Harness the power of DevOps best practices to boost your workflow automation through a production-ready Kubernetes deployment.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

n8n continues to grow thanks to dedicated supporters like you. Want to get involved? Here’s how to contribute:

* 📘 Review the [n8n configuration docs](https://community-charts.github.io/docs/category/n8n)
* 🔧 Submit your improvements via [GitHub pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs and issues through our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features you’d love to see implemented

Thanks for being a part of the journey. Together, we’re making open-source Kubernetes deployments easier and more powerful than ever!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-11-n8n-chart-version-1-14-1-released.md)


---

# n8n chart version 1.14.2 now available

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to announce the release of the n8n Helm chart **version 1.14.2**, featuring **app version 1.107.3**! This update brings valuable enhancements and community-led improvements that streamline your Kubernetes deployment experience.

## What’s new in version 1.14.2[​](#whats-new-in-version-1142 "Direct link to What’s new in version 1.14.2")

This Helm chart update introduces several important changes that improve compatibility, performance, and ease of use:

* 🔄 Updated to use the latest `n8nio/n8n` container image version: **1.107.3**<br /><!-- -->→ [Upstream project on GitHub](https://github.com/n8n-io/n8n)

* 🛠️ Upgraded Redis Helm dependency from `22.0.1` to `22.0.4`<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 🗄️ Upgraded PostgreSQL Helm dependency from `16.7.24` to `16.7.26`<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

See the full list of changes in our official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.14.2).

<!-- -->

## Get started with n8n 1.14.2 on Kubernetes[​](#get-started-with-n8n-1142-on-kubernetes "Direct link to Get started with n8n 1.14.2 on Kubernetes")

It’s easier than ever to deploy and manage n8n in your Kubernetes environment. Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* Quick setup with default configurations
* Custom environment tuning and advanced configuration
* Best practices for production-grade deployments

Explore all deployment options in the [official documentation](https://community-charts.github.io/docs/category/n8n).

## Why choose the n8n Helm chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why choose the n8n Helm chart?")

Maintained by the GitHub Community Charts project, the n8n Helm chart helps DevOps and automation teams get up and running effortlessly with Kubernetes-native workflows. Key advantages:

* 🚀 Easy installation and upgrades
* 🤝 Actively maintained by a growing open-source community
* 🔧 Flexible configuration for various use cases
* 🔒 Reliably tested in real Kubernetes environments

## Join the community[​](#join-the-community "Direct link to Join the community")

The GitHub Community Charts team welcomes developers, sysadmins, and automation enthusiasts to collaborate and improve together. Here’s how you can get involved:

* 📖 Dive into the [n8n chart docs](https://community-charts.github.io/docs/category/n8n)
* 🧪 Submit pull requests or help fix bugs on our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Found an issue? [Report it here](https://github.com/community-charts/helm-charts/issues)
* 💡 Have ideas or feature requests? [Open a new issue](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the n8n journey with GitHub Community Charts. Let’s keep building powerful workflows—simpler, faster, and together.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-19-n8n-chart-version-1-14-2-released.md)


---

# n8n chart version 1.14.3 released

August 20, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.14.3**, officially available as of August 20, 2025. This version includes the latest **n8n application version 1.107.4** and delivers key improvements for deploying n8n on Kubernetes with greater ease and flexibility.

## What’s New in Chart Version 1.14.3[​](#whats-new-in-chart-version-1143 "Direct link to What’s New in Chart Version 1.14.3")

Version 1.14.3 introduces updates to both the Helm chart and the application:

* 🔄 **Updated** the `n8nio/n8n` container image to version 1.107.4
  <!-- -->
  * Check out the [n8n project on GitHub](https://github.com/n8n-io/n8n) for upstream details.

To review all modifications included in this release, please see the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.14.3).

<!-- -->

## Getting Started with n8n Helm Chart[​](#getting-started-with-n8n-helm-chart "Direct link to Getting Started with n8n Helm Chart")

Ready to launch n8n with the latest chart? Our [comprehensive installation guide](https://community-charts.github.io/docs/category/n8n) provides everything you need to get started:

* Simple default installations for quick testing.
* Advanced configuration options for custom environments.
* Deployment best practices to support production workloads.

Visit the official [n8n chart documentation](https://community-charts.github.io/docs/category/n8n) and start building automated workflows on Kubernetes today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n chart is built to simplify and streamline Kubernetes deployments. Here’s why developers and teams choose it:

* ✅ **User-Friendly**: Easy to install, configure, and scale.
* 🌐 **Community-Focused**: Powered by contributions from open-source enthusiasts worldwide.
* 🛠️ **Highly Configurable**: Fine-tune your deployment to match your project requirements.
* 🔒 **Stable and Secure**: Built for reliable performance inside Kubernetes clusters.

## Contribute to the Community[​](#contribute-to-the-community "Direct link to Contribute to the Community")

GitHub Community Charts thrives thanks to the contributions of open-source supporters like you. Whether you’re fixing bugs, enhancing configs, or proposing new ideas — we’d love your help.

Get started by exploring the following:

* 📘 Dive into the [n8n chart documentation](https://community-charts.github.io/docs/category/n8n) to learn about configurable values.
* 📥 Open a pull request in our [GitHub repository](https://github.com/community-charts/helm-charts).
* 🐛 Report bugs or suggest updates via our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Share your feature ideas to help shape future releases.

Thank you for being a part of the n8n and GitHub Community Charts ecosystem. Together, let's keep empowering automation, one Kubernetes deployment at a time.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-20-n8n-chart-version-1-14-3-released.md)


---

# n8n chart version 1.15.0 released

August 24, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart—**v1.15.0**—is now available as of August 24, 2025. This release includes **app version 1.107.4**, bringing new features, enhancements, and community-suggested improvements to streamline your n8n deployment on Kubernetes.

## What’s New in Version 1.15.0[​](#whats-new-in-version-1150 "Direct link to What’s New in Version 1.15.0")

This update enhances both the n8n Helm chart and the application it deploys. Here's a summary of what's included:

* ✅ **Editor URL support improved** – Ensures smoother password reset and signup flows by properly defining the Editor URL<br />[Issue #210](https://github.com/community-charts/helm-charts/issues/210)

* 🔐 **PostgreSQL** – Added support for enabling SSL connections to PostgreSQL databases<br />[Issue #211](https://github.com/community-charts/helm-charts/issues/211)

* 🔒 **Redis** – Now supports secure Redis connections via TLS<br />[Issue #214](https://github.com/community-charts/helm-charts/issues/214)

* 🛠️ **External Redis port fix** – Corrected configuration of external Redis port values<br />[Issue #215](https://github.com/community-charts/helm-charts/issues/215)

For the full list of changes, be sure to check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.0) on GitHub.

<!-- -->

## Deploy n8n v1.15.0 on Kubernetes[​](#deploy-n8n-v1150-on-kubernetes "Direct link to Deploy n8n v1.15.0 on Kubernetes")

Ready to get started? Our [step-by-step deployment guide](https://community-charts.github.io/docs/category/n8n) will walk you through every step, whether you're a beginner or looking to scale up for production:

* 🧪 Quick installation using defaults
* ⚙️ Custom configuration options
* 🚀 Production-ready best practices

Head to the [n8n Helm chart docs](https://community-charts.github.io/docs/category/n8n) to dive in.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart delivers a fast and reliable way to deploy your workflows in Kubernetes environments. Here's what makes it special:

* 🧩 **Simple & Configurable** – Designed for flexibility without complexity
* 🌍 **Built by the Community** – Open-source contributions help drive feature updates
* 🔄 **Keeps n8n Updated** – Quickly get the latest stable app releases
* 📦 **Battle-Tested** – Proven to work reliably across Kubernetes setups

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Whether you're a developer, DevOps engineer, or open-source enthusiast, your help makes this project better! There are many ways to contribute:

* 📖 Learn more in the [docs](https://community-charts.github.io/docs/category/n8n)
* 💡 Submit improvements via pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs and help troubleshoot via our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💬 Share feature ideas to shape future releases

Thanks for being part of the open-source journey—let’s keep building better tools together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-24-n8n-chart-version-1-15-0-released.md)


---

# n8n chart version 1.15.1 released

August 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the **n8n Helm chart, version 1.15.1**, is now available as of August 25, 2025. This update includes **n8n app version 1.107.4** and brings improved Redis configuration and valuable contributions from our open-source community.

## What’s new in Helm chart 1.15.1[​](#whats-new-in-helm-chart-1151 "Direct link to What’s new in Helm chart 1.15.1")

Version 1.15.1 of the Helm chart includes key enhancements that make deploying and managing n8n more streamlined on Kubernetes. This release highlights:

* ✅ **Added**: Default Bitnami Redis Master port for better connectivity and configuration alignment.

You can view the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.1).

<!-- -->

## Get started with the n8n 1.15.1 chart[​](#get-started-with-the-n8n-1151-chart "Direct link to Get started with the n8n 1.15.1 chart")

Deploying n8n on Kubernetes has never been easier. Whether you're setting up a quick test environment or building for production, our comprehensive guides help you every step of the way. Check out the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for:

* Quick-start instructions with minimal setup.
* Best practices for custom configurations.
* Tips for running n8n reliably in any environment.

Explore deployment options and choose the setup that fits your needs.

## Why choose this Helm chart?[​](#why-choose-this-helm-chart "Direct link to Why choose this Helm chart?")

Maintained by the GitHub Community Charts team, this Helm chart for n8n is trusted by developers and DevOps professionals around the world. Here's why:

* 🚀 **Simple to deploy**: Designed for ease with sensible defaults.
* 🤝 **Backed by community**: Continuously improved through open collaboration.
* 🔧 **Highly configurable**: Supports flexible deployment scenarios.
* 🔒 **Kubernetes-ready**: Built and tested for production environments.

## Join the community[​](#join-the-community "Direct link to Join the community")

The strength of n8n and this Helm chart lies in the power of its community. Whether you’re looking to contribute code, document a workaround, or suggest improvements, there are many ways to get involved:

* Browse our [configuration docs](https://community-charts.github.io/docs/category/n8n).
* Contribute via pull requests on [GitHub](https://github.com/community-charts/helm-charts).
* Report bugs or open feature requests in our [issue tracker](https://github.com/community-charts/helm-charts/issues).

We appreciate your support and look forward to evolving the n8n chart together. Happy automating!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-25-n8n-chart-version-1-15-1-released.md)


---

# n8n chart version 1.15.10 released

September 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the latest version of the n8n Helm chart — **v1.15.10** — is now available as of 2025-09-24. This release includes **n8n app version 1.112.5** and introduces enhancements inspired by our open-source community to streamline your Kubernetes workflow automation.

## Highlights of chart version 1.15.10[​](#highlights-of-chart-version-11510 "Direct link to Highlights of chart version 1.15.10")

This release updates both the Helm chart and the application image. Here’s what’s new in this version:

* 📦 **Updated application image** to `n8nio/n8n:1.112.5`
  <br />
  <!-- -->
  ↳ [Visit n8n on GitHub](https://github.com/n8n-io/n8n)

Check out the full list of changes in the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.10) on GitHub.

<!-- -->

## How to get started with n8n 1.15.10[​](#how-to-get-started-with-n8n-11510 "Direct link to How to get started with n8n 1.15.10")

Ready to deploy or upgrade? Our [documentation portal](https://community-charts.github.io/docs/category/n8n) offers everything you need:

* Step-by-step installation with default or custom settings
* Examples for scaling and configuration
* Guides for production-ready setups

Whether you're just getting started or optimizing your existing setup, the docs will guide you every step of the way.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

The n8n Helm chart, maintained by the [Community Charts project on GitHub](https://github.com/community-charts/helm-charts), is built to make running n8n in Kubernetes environments as simple and efficient as possible.

Here are a few key advantages:

* 🔧 **Easy setup**: Deploy with minimal effort in just a few commands
* 🌍 **Community-driven**: Contributions and insights from developers around the world
* ✨ **Highly flexible**: Customize deployments to fit your specific needs
* 🔒 **Stable and production-ready**: Continuously tested in real-world Kubernetes clusters

## Join the community[​](#join-the-community "Direct link to Join the community")

We love open source, and we’d love your help! Whether you’re fixing bugs, contributing improvements, or offering ideas, here’s how you can get involved:

* 📝 [Read the docs](https://community-charts.github.io/docs/category/n8n) and learn how it works
* 🤝 [Contribute on GitHub](https://github.com/community-charts/helm-charts)
* 🐞 [Report any issues](https://github.com/community-charts/helm-charts/issues)
* 💡 [Submit feature requests](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the journey. Your support helps bring powerful, automated workflows to Kubernetes users everywhere!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-24-n8n-chart-version-1-15-10-released.md)


---

# n8n chart version 1.15.11 released

September 26, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.15.11**, available as of 2025-09-26. This update includes **application version 1.112.6**, bringing fresh enhancements and community contributions to help you run n8n even more smoothly on Kubernetes.

## What’s New in Helm Chart 1.15.11[​](#whats-new-in-helm-chart-11511 "Direct link to What’s New in Helm Chart 1.15.11")

This latest release updates both the Helm chart and the n8n application itself:

* ✅ **Updated**: Upgraded the container image to `n8nio/n8n:1.112.6`
  * Refer to the [upstream project](https://github.com/n8n-io/n8n) for core app changes.

For full details, check out the complete [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.11).

<!-- -->

## Getting Started with n8n 1.15.11[​](#getting-started-with-n8n-11511 "Direct link to Getting Started with n8n 1.15.11")

Ready to deploy? The enhanced chart allows a flexible and straightforward installation workflow. Visit our [n8n installation guide](https://community-charts.github.io/docs/category/n8n) to get started with:

* A quick start using default values
* Custom configuration tailored to your environment
* Deployment tips for production-grade setups

Get up and running with n8n in minutes using our comprehensive documentation.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The officially maintained Helm chart from [GitHub Community Charts](https://github.com/community-charts/helm-charts) streamlines your Kubernetes deployment. Here's why it's a great choice:

* 🚀 **User-Friendly**: Easy to set up and maintain
* 🤝 **Community-Powered**: Shaped by real-world use and open-source feedback
* ⚙️ **Fully Configurable**: Fine-tune your deployment to fit any use case
* 🔒 **Reliable**: Frequently tested to ensure stability in Kubernetes clusters

Whether deploying for the first time or managing large automations, this Helm chart gives you the tools you need to succeed.

## Join Our Community[​](#join-our-community "Direct link to Join Our Community")

We believe in open-source collaboration and would love for you to be part of the journey. There are many ways to get involved:

* 🔍 Dive into the [n8n docs](https://community-charts.github.io/docs/category/n8n) to learn more about chart options
* ✍️ Contribute via pull requests on our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Found a bug? [Report an issue](https://github.com/community-charts/helm-charts/issues)
* 💡 Have ideas for improvement? [Submit a feature request](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the n8n and GitHub Community Charts ecosystem. Together, we’re making deploying open-source automation in Kubernetes easier than ever.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-26-n8n-chart-version-1-15-11-released.md)


---

# n8n chart version 1.15.12 released

October 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.15.12**, available as of 2025-10-03. This latest chart ships with **application version 1.113.3** and includes several improvements driven by our amazing open-source community.

Whether you're just starting out or managing production workloads, this update makes it even easier to deploy n8n on Kubernetes with flexibility and confidence.

## What’s New in Chart Version 1.15.12[​](#whats-new-in-chart-version-11512 "Direct link to What’s New in Chart Version 1.15.12")

This release brings updates to both the Helm chart and the underlying n8n application:

* 🔄 **Updated**: n8n image version bumped to 1.113.3
  <br />
  <!-- -->
  👉 [View upstream project](https://github.com/n8n-io/n8n)

For full details of what’s included in this update, check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.12) on GitHub.

<!-- -->

## Deploying n8n with Helm[​](#deploying-n8n-with-helm "Direct link to Deploying n8n with Helm")

Getting up and running with the new version is simple. Visit our [documentation portal](https://community-charts.github.io/docs/category/n8n) for resources that guide you through:

* Installing with default configuration
* Tweaking custom values for your environment
* Optimizing your setup for production use

These docs are designed to help you succeed – whether you're deploying on AWS, Azure, or your own cluster.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Built and maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart offers a dependable and convenient way to deploy n8n on Kubernetes.

Here's why developers and DevOps teams rely on it:

* ✅ **Simple Setup**: Install n8n quickly with a single command
* 🌱 **Open Source**: Developed by the community, for the community
* ⚙️ **Configurable**: Adaptable to any workload or infrastructure
* 🔒 **Proven Stability**: Validated in diverse Kubernetes environments

## Contribute to the Community[​](#contribute-to-the-community "Direct link to Contribute to the Community")

Our charts thrive with your help! Whether you want to contribute code, submit feedback, or just stay in the loop, there are lots of ways to get involved:

* 🤓 Review the [n8n Helm chart docs](https://community-charts.github.io/docs/category/n8n)
* 🛠️ Contribute on [GitHub](https://github.com/community-charts/helm-charts)
* 🪲 Report bugs or request new features using our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thanks for supporting the n8n community and helping us improve Kubernetes workflows for everyone. Happy deploying!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-03-n8n-chart-version-1-15-12-released.md)


---

# n8n chart version 1.15.13 released

October 7, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.15.13**, available as of October 7, 2025. This update includes **n8n application version 1.114.3**, delivering valuable enhancements, dependency updates, and continued support from our amazing open-source community.

<!-- -->

## What’s new in n8n chart 1.15.13[​](#whats-new-in-n8n-chart-11513 "Direct link to What’s new in n8n chart 1.15.13")

This release brings updates to ensure improved performance and compatibility within your Kubernetes environments. Key updates include:

* 🔄 **Application Version Updated**: Upgraded n8nio/n8n Docker image to 1.114.3<br /><!-- -->→ [View on GitHub](https://github.com/n8n-io/n8n)

* 📦 **Redis Dependency**: Updated from 22.0.7 to 23.0.10<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 🗄️ **PostgreSQL Dependency**: Updated from 16.7.27 to 18.0.7<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Check out the complete changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.13).

## Get started with n8n 1.15.13[​](#get-started-with-n8n-11513 "Direct link to Get started with n8n 1.15.13")

Whether you're deploying n8n for the first time or upgrading your existing setup, we've got you covered with step-by-step documentation:

* 🚀 Quick install using default settings
* 🛠️ Comprehensive guide to configuration options
* 🏗️ Best practices for production deployments

Visit the [n8n installation docs](https://community-charts.github.io/docs/category/n8n) to get started today.

## Why use the official n8n Helm chart?[​](#why-use-the-official-n8n-helm-chart "Direct link to Why use the official n8n Helm chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, this Helm chart makes running n8n on Kubernetes smooth and reliable. Highlights include:

* ✅ Simple installation and upgrade paths
* 📅 Ongoing community-led updates and maintenance
* ⚙️ Flexible configuration to fit any Kubernetes environment
* 🔒 Focused on reliability and cloud-native best practices

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The n8n Helm chart is a collaborative effort driven by passionate contributors like you. There are many ways to get involved:

* 📖 Learn more in the [n8n documentation](https://community-charts.github.io/docs/category/n8n)
* 🌟 Contribute code or documentation on our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report issues or suggest enhancements via our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you to everyone who helps make Kubernetes deployments easier with open-source!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-07-n8n-chart-version-1-15-13-released.md)


---

# n8n chart version 1.15.14 released

October 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce that the latest version of the n8n Helm chart — **v1.15.14** — is now available as of 2025-10-08. This release includes **n8n app version 1.114.4** and brings a fresh round of enhancements and updates powered by community contributions to make your Kubernetes deployment experience even smoother.

## What’s New in This Release[​](#whats-new-in-this-release "Direct link to What’s New in This Release")

The Helm chart version 1.15.14 introduces important updates to both the application and its key dependencies. Here's what's included:

* 🔄 **Updated**: Upgraded base image to `n8nio/n8n:1.114.4`
  <br />
  <!-- -->
  → [n8n GitHub Repository](https://github.com/n8n-io/n8n)
* 🧠 **Updated**: Redis Helm chart bumped from `23.0.10` to `23.1.1`
  <br />
  <!-- -->
  → [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🗃 **Updated**: PostgreSQL Helm chart bumped from `18.0.7` to `18.0.8`
  <br />
  <!-- -->
  → [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the complete changelog and technical details, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.14).

<!-- -->

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Ready to upgrade or install n8n 1.15.14? Our comprehensive [setup guides](https://community-charts.github.io/docs/category/n8n) will walk you through everything:

* Simple installation using default settings.
* Custom configurations to adapt to your environment.
* Tips and best practices for running n8n in production.

Kickstart your deployment by visiting the [official docs](https://community-charts.github.io/docs/category/n8n) today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Designed and maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), this Helm chart streamlines the process of deploying n8n on Kubernetes.

Here’s why developers and teams love using it:

* 🚀 **Quick Setup**: Get up and running in minutes.
* 🤝 **Community-Powered**: Driven by contributions and real-world experiences.
* ⚙️ **Customizable**: Tailor deployments for development, staging, or production.
* 🔒 **Reliable**: Thoroughly tested in Kubernetes environments.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The n8n Helm chart thrives on collaboration. Whether you're a seasoned contributor or new to open source, your input helps improve the experience for everyone.

Here’s how to get involved:

* 📖 Learn with our [documentation](https://community-charts.github.io/docs/category/n8n)
* 🔧 Contribute via [GitHub Pull Requests](https://github.com/community-charts/helm-charts)
* 🐛 Report issues [on GitHub](https://github.com/community-charts/helm-charts/issues)
* 💡 Propose features or enhancements [through our issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the community and helping make n8n easier to deploy and manage on Helm and Kubernetes. Let’s keep building together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-08-n8n-chart-version-1-15-14-released.md)


---

# n8n chart version 1.15.15 released

October 14, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **n8n Helm chart version 1.15.15**, officially available as of 2025-10-14. This update comes with the powerful **app version 1.115.2** and includes several improvements that enhance performance, stability, and ease of deployment on Kubernetes.

<!-- -->

## What’s new in n8n Helm chart 1.15.15[​](#whats-new-in-n8n-helm-chart-11515 "Direct link to What’s new in n8n Helm chart 1.15.15")

This version introduces vital upgrades to core dependencies and delivers an up-to-date n8n application image designed for smoother automation workflows. Here’s a summary of the changes:

* ✅ **Upgraded n8n image to 1.115.2**
  * See the upstream project on [GitHub](https://github.com/n8n-io/n8n)
* 📦 **Redis dependency updated** from 23.1.1 to 23.1.3
  <!-- -->
  * View on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🛠️ **PostgreSQL dependency updated** from 18.0.8 to 18.0.14
  <!-- -->
  * Learn more on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Check out the full changelog on our [GitHub release page](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.15).

## Get started with n8n chart 1.15.15[​](#get-started-with-n8n-chart-11515 "Direct link to Get started with n8n chart 1.15.15")

Ready to deploy? The updated chart offers a seamless way to get n8n running on your Kubernetes cluster. Visit our [documentation hub](https://community-charts.github.io/docs/category/n8n) for:

* Quick installation guides with minimal configuration
* Customization options to fit your environment
* Best practices for running n8n in production

Whether you’re a first-time user or upgrading from a previous version, it’s easy to get started.

## Why use the official n8n Helm chart?[​](#why-use-the-official-n8n-helm-chart "Direct link to Why use the official n8n Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, this chart brings the flexibility of n8n and the power of Kubernetes together. Benefits include:

* ⚙️ **Flexible configuration** for a variety of use cases
* 🤝 **Community-powered development** with frequent updates
* 📦 **Streamlined installation and upgrades**
* 🔒 **Built-in stability** with Kubernetes-native best practices

Built with developers and DevOps teams in mind, this open-source chart is ideal for automating your workflows reliably at scale.

## Join the community[​](#join-the-community "Direct link to Join the community")

We’re building n8n charts together — and your voice matters! Here’s how you can be part of growing the ecosystem:

* 🙋‍♀️ Read setup instructions in the [documentation](https://community-charts.github.io/docs/category/n8n)
* 🛠 Help improve the project by sending pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or issues using the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features and enhancements via a [feature request](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the open-source community. We look forward to your feedback and contributions that help make Kubernetes deployments better for everyone.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [Redis](/blog/tags/redis.md "Configure your applications with Redis for caching, queueing, and real-time data, including managed Redis on major cloud providers.")
* [Postgres](/blog/tags/postgres.md "Learn how to configure applications with PostgreSQL for reliable data storage, including guides for managed PostgreSQL on AWS, Google Cloud, and Azure.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-14-n8n-chart-version-1-15-15-released.md)


---

# n8n chart version 1.15.16 released

October 15, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the **n8n Helm chart version 1.15.16** is now available, featuring **application version 1.115.3**. This release comes with meaningful improvements and important updates to make deploying n8n on Kubernetes even more seamless and scalable.

## What’s new in n8n chart 1.15.16[​](#whats-new-in-n8n-chart-11516 "Direct link to What’s new in n8n chart 1.15.16")

This release includes updates to both the Helm chart (v1.15.16) and the n8n application (v1.115.3). Here’s what’s changed:

* 🔄 **Application Version Upgrade**: Updated to n8nio/n8n image version 1.115.3
  <br />
  <!-- -->
  → [View on GitHub](https://github.com/n8n-io/n8n)
* 🔧 **Dependency Update**: Upgraded PostgreSQL from version 18.0.14 to 18.0.15
  <br />
  <!-- -->
  → [View on Artifact Hub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Check out the full details in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.16) on GitHub.

<!-- -->

## Get started with n8n 1.15.16[​](#get-started-with-n8n-11516 "Direct link to Get started with n8n 1.15.16")

Looking to install the new version? We've got you covered with clear, step-by-step [installation guides](https://community-charts.github.io/docs/category/n8n) to help you:

* Launch with default settings in just a few commands
* Apply custom configurations tailored to your Kubernetes environment
* Follow best practices for robust production deployments

Visit the [n8n chart docs](https://community-charts.github.io/docs/category/n8n) for everything you need to get up and running.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart simplifies the deployment process for n8n in Kubernetes environments. Here's why users trust it:

* 🚀 Easy to deploy with quick-start configurations
* 🤝 Built and improved by a passionate open-source community
* ⚙ Fully customizable to adapt to your workflows
* 🔒 Reliable and tested for real-world Kubernetes setups

## Join the community[​](#join-the-community "Direct link to Join the community")

We’re proud to have an open and collaborative community supporting the n8n Helm chart. Whether you're a developer, DevOps engineer, or Kubernetes enthusiast, your involvement makes a difference.

* 📘 Learn how to configure features in the [official docs](https://community-charts.github.io/docs/category/n8n)
* ✏ Contribute code or fixes directly in our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs and help us improve on our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest enhancements or new features—your feedback matters!

Thank you for supporting n8n and the GitHub Community Charts project. Let’s keep building better workflows together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-15-n8n-chart-version-1-15-16-released.md)


---

# n8n chart version 1.15.17 released

October 22, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.15.17**, featuring **app version 1.116.2** as of October 22, 2025. This update delivers key enhancements, updated dependencies, and community-driven improvements to streamline your n8n experience on Kubernetes.

## What’s new in version 1.15.17[​](#whats-new-in-version-11517 "Direct link to What’s new in version 1.15.17")

The latest release incorporates updates to both the Helm chart and the n8n application to ensure better performance and compatibility:

- 📦 **Updated**: n8nio/n8n image to `1.116.2`<br /><!-- -->↳ [Upstream Project](https://github.com/n8n-io/n8n)<br /><!-- -->- 🚀 **Updated**: Redis dependency from `23.1.3` to `23.2.1`<br /><!-- -->↳ [Redis on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)<br /><!-- -->- 🗃️ **Updated**: PostgreSQL dependency from `18.0.15` to `18.1.1`<br /><!-- -->↳ [PostgreSQL on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full breakdown of changes, check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.17).

<!-- -->

## Start using the n8n Helm chart[​](#start-using-the-n8n-helm-chart "Direct link to Start using the n8n Helm chart")

Getting started with version 1.15.17 is easy! Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* Standard installation using default values
* Custom configuration to tailor deployments to your needs
* Deploying n8n securely and efficiently in production environments

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get started today.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), the n8n Helm chart is your go-to solution for deploying workflows in Kubernetes environments.

Here’s why users love it:

* ✅ **User-friendly**: Simple and quick to install
* 🌍 **Open-source and community-supported**: Regular updates and fixes
* ⚙️ **Highly configurable**: Customizable settings to match your workflow
* 🛡️ **Production ready**: Battle-tested and reliable

## Join the community[​](#join-the-community "Direct link to Join the community")

The n8n Helm chart is powered by a passionate open-source community—and we’d love for you to be part of it! You can:

* 📘 Dive into our [documentation](https://community-charts.github.io/docs/category/n8n) for configuration tips
* 🤝 [Contribute](https://github.com/community-charts/helm-charts) to the GitHub Community Charts project
* 🐞 [Report bugs](https://github.com/community-charts/helm-charts/issues) or request features

We appreciate your continued support for n8n and the open-source ecosystem. Let’s build a better Kubernetes deployment experience, together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-22-n8n-chart-version-1-15-17-released.md)


---

# n8n chart version 1.15.18 released

October 28, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the updated **n8n Helm chart version 1.15.18**, featuring **app version 1.117.2**, now available as of 2025-10-28. This release includes important updates and enhancements that make deploying n8n on Kubernetes even more seamless for developers and teams.

<!-- -->

## What’s New in n8n 1.15.18[​](#whats-new-in-n8n-11518 "Direct link to What’s New in n8n 1.15.18")

This release updates both the Helm chart and its dependencies to offer improved performance and compatibility:

* ✅ **Application Update**: Upgraded n8nio/n8n image to version 1.117.2<br /><!-- -->→ [View on GitHub](https://github.com/n8n-io/n8n)

* 🔄 **Redis Chart**: Bumped from version 23.2.1 to 23.2.2<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 🔄 **PostgreSQL Chart**: Updated from version 18.1.1 to 18.1.3<br /><!-- -->→ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

To explore all changes in detail, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.18).

## Get Started with n8n on Kubernetes[​](#get-started-with-n8n-on-kubernetes "Direct link to Get Started with n8n on Kubernetes")

Ready to try out this version? Whether you're just starting or scaling with Kubernetes, our [installation guides](https://community-charts.github.io/docs/category/n8n) will walk you through:

* Installing the chart with default values.
* Customizing your deployment to match your environment.
* Applying best practices for production workloads.

Join a growing community automating workflows with the power of [n8n and Kubernetes](https://community-charts.github.io/docs/category/n8n).

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), this chart brings a reliable and flexible way to run n8n in the cloud:

* 🧩 Simple Setup: Helm chart simplifies deployment within minutes.
* 💚 Community Support: Driven by contributions and collaboration.
* 🔧 Configurable: Tailor your configuration to meet unique needs.
* 🔒 Reliable: Built for stability and production-readiness on Kubernetes.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’d love your help shaping the future of the n8n Helm chart! Here’s how you can get involved:

* Read the [n8n chart documentation](https://community-charts.github.io/docs/category/n8n) to learn how it works.
* Share code by submitting [pull requests](https://github.com/community-charts/helm-charts).
* Report issues or bugs [on GitHub](https://github.com/community-charts/helm-charts/issues).
* Suggest new features or improvements directly via the [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thanks for being part of the open-source DevOps journey. Together, we’re making workflow automation with n8n even better on Kubernetes.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-28-n8n-chart-version-1-15-18-released.md)


---

# n8n chart version 1.15.19 released

October 29, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the **n8n Helm chart version 1.15.19** is now available as of October 29, 2025. This version ships with **app version 1.117.3**, bringing smoother performance, enhanced stability, and valuable improvements driven by our open-source community.

## Highlights of the 1.15.19 Release[​](#highlights-of-the-11519-release "Direct link to Highlights of the 1.15.19 Release")

This version introduces updates to the Helm chart and the associated n8n application to ensure a better deployment experience on Kubernetes.

* ✅ **Updated**: Container image bumped to `n8nio/n8n:1.117.3`
  * Source: [n8n GitHub repository](https://github.com/n8n-io/n8n)

For the full list of changes, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.19) on GitHub.

<!-- -->

## Get Started with n8n 1.15.19 on Kubernetes[​](#get-started-with-n8n-11519-on-kubernetes "Direct link to Get Started with n8n 1.15.19 on Kubernetes")

Want to launch n8n using the latest chart? Our [installation guide](https://community-charts.github.io/docs/category/n8n) will walk you through:

* Rapid setup using default values
* Customized deployments tailored to your infrastructure
* Tips for scaling and production-ready configurations

Whether you're just getting started or managing critical workflows, the documentation has everything you need.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Built and maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, this Helm chart makes deploying and managing n8n on Kubernetes efficient and dependable.

💡 Key benefits:

* User-friendly installation and upgrades
* Growing community with regular contributions
* Seamless customisation options
* Production-ready and continuously tested

If you're integrating n8n into your Kubernetes workflow on platforms like AWS or Azure, this chart offers a scalable and robust deployment method.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Community involvement is at the core of the n8n Helm chart's success. Here’s how you can contribute:

* 📖 Dive into the [n8n chart docs](https://community-charts.github.io/docs/category/n8n) to learn more
* 🤝 Send improvements via [pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Report and track issues in our [GitHub tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features to enhance the user experience

Thanks for being part of the journey. Together, we’re making cloud-native automation easier for everyone!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-29-n8n-chart-version-1-15-19-released.md)


---

# n8n Helm chart 1.15.2 now available

August 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the n8n Helm chart! Version **1.15.2** is now live as of August 27, 2025, and includes **app version 1.108.2**. This update introduces several enhancements, dependency upgrades, and ongoing community contributions to make Kubernetes deployments even smoother.

## What’s new in version 1.15.2[​](#whats-new-in-version-1152 "Direct link to What’s new in version 1.15.2")

Here’s a breakdown of the key changes included in this release:

* ✅ Updated the base container image to `n8nio/n8n` version **1.108.2**<br /><!-- -->→ [View upstream project](https://github.com/n8n-io/n8n)

* 🔧 Bumped Redis dependency from `22.0.4` to `22.0.6`<br /><!-- -->→ [Redis chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 🔧 Upgraded PostgreSQL dependency from `16.7.26` to `16.7.27`<br /><!-- -->→ [PostgreSQL chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full list of updates, check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.2) on GitHub.

<!-- -->

## How to get started[​](#how-to-get-started "Direct link to How to get started")

Ready to upgrade or install n8n with Helm? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through every step, including:

* Quick-start instructions for first-time users
* Customization options to fit your specific environment
* Best practices for reliable production deployments

Whether you're deploying on AWS, Azure, or any other Kubernetes provider, our Helm chart makes it simple.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts), the n8n chart provides a reliable and flexible way to run n8n in Kubernetes. Here’s what you get:

* 🛠 Easy setup and configuration
* 🌱 Active community with frequent updates
* 🔌 Highly configurable to suit any use case
* 🔒 Production-ready with proven stability

## Join the community[​](#join-the-community "Direct link to Join the community")

We believe that great software is built together. If you’d like to contribute to the n8n Helm chart or help grow the community, here’s how you can get involved:

* 👀 Browse the [n8n chart documentation](https://community-charts.github.io/docs/category/n8n)
* 💬 Join the discussion and contribute via [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs or request features through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you to all contributors helping improve the n8n Helm chart. Let’s keep building better Kubernetes experiences—together.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-27-n8n-chart-version-1-15-2-released.md)


---

# n8n chart version 1.15.20 released

November 6, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart—**v1.15.20**—is now available as of November 6, 2025. This release includes **app version 1.118.2**, bringing powerful enhancements, dependency updates, and community-driven improvements to help you deploy n8n more easily on Kubernetes.

## What’s New in Version 1.15.20[​](#whats-new-in-version-11520 "Direct link to What’s New in Version 1.15.20")

In this release, we’ve updated both the Helm chart and key dependencies to enhance performance, stability, and compatibility:

* 🔄 **Updated**: n8n image bumped to version 1.118.2
  <br />
  <!-- -->
  → [View Source](https://github.com/n8n-io/n8n)
* 📦 **Updated**: Redis chart updated from 23.2.2 to 23.2.6
  <br />
  <!-- -->
  → [Redis on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🗄️ **Updated**: PostgreSQL chart updated from 18.1.3 to 18.1.4
  <br />
  <!-- -->
  → [PostgreSQL on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Want full details? Check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.20) on GitHub.

<!-- -->

## Get Started with the n8n 1.15.20 Helm Chart[​](#get-started-with-the-n8n-11520-helm-chart "Direct link to Get Started with the n8n 1.15.20 Helm Chart")

Ready to deploy? We’ve got you covered with comprehensive [setup documentation](https://community-charts.github.io/docs/category/n8n) that walks you through:

* Quick deployment using default settings
* Customizing configurations for your specific environment
* Recommended practices for production setups

Explore the full n8n Helm guide to get started quickly and confidently on Kubernetes.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The n8n Helm chart, maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), is trusted by developers and DevOps teams for good reason:

* 🚀 **Simplified Deployment**: Get up and running on Kubernetes effortlessly
* 🤝 **Community Powered**: Regular updates and enhancements driven by contributors
* 🔧 **Highly Configurable**: Tailor it to match your application's needs
* ✅ **Stability First**: Tested and ready for production environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We're proud to be part of a growing open-source ecosystem around Kubernetes. Whether you're submitting a bugfix or helping refine documentation, your contributions help power this project.

Here’s how to get involved:

* Browse the [n8n chart docs](https://community-charts.github.io/docs/category/n8n) for details and configuration options
* Fork, improve, and contribute at our [GitHub repository](https://github.com/community-charts/helm-charts)
* Found an issue? [Report it here](https://github.com/community-charts/helm-charts/issues)
* Have an idea? [Request features](https://github.com/community-charts/helm-charts/issues/new) and help us evolve

Thanks for being part of the journey! Together, we’re making enterprise-ready n8n workflows more accessible and scalable across cloud-native environments.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-06-n8n-chart-version-1-15-20-released.md)


---

# n8n Helm chart 1.15.3 now available

September 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.15.3**, is now available! This release comes with **application version 1.109.1**, offering improved stability, refined configurations, and fresh updates from the community.

## Highlights of v1.15.3[​](#highlights-of-v1153 "Direct link to Highlights of v1.15.3")

This version introduces key updates to both the Helm chart and the application image.

* 📦 Updated n8n image to version **1.109.1**
  <br />
  <!-- -->
  → See the upstream project on [GitHub](https://github.com/n8n-io/n8n)
* 🔧 Bumped Redis dependency from `22.0.6` to `22.0.7`
  <br />
  <!-- -->
  → View the chart on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

Ready to dive deeper? View the [complete changelog](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.3) on GitHub.

<!-- -->

## Get Started with the n8n 1.15.3 Helm Chart[​](#get-started-with-the-n8n-1153-helm-chart "Direct link to Get Started with the n8n 1.15.3 Helm Chart")

Whether you're deploying n8n for the first time or updating your current setup, we've got comprehensive guidance available:

* 🚀 Quick-start installation with easy defaults.
* 🛠 How to tailor configurations for your use case.
* ✅ Best practices for production-ready Kubernetes environments.

Explore our step-by-step [installation guides](https://community-charts.github.io/docs/category/n8n) and get your automation platform running in minutes.

## Why Use the Official n8n Helm Chart?[​](#why-use-the-official-n8n-helm-chart "Direct link to Why Use the Official n8n Helm Chart?")

Developed and maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, this chart helps you manage n8n deployments on Kubernetes with ease.

Here’s what you can expect:

* ☁️ Seamless Kubernetes compatibility
* 🔄 Frequent updates and contributions from the open-source community
* ⚙️ Flexible configurations for custom workloads
* 🧪 Community-tested for reliability and resilience

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We're proud to be part of a vibrant open-source ecosystem, and we’d love for you to get involved! Whether you’re a Helm expert or just getting started, there are plenty of ways to contribute:

* 📝 Read the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration tips.
* 🤝 Submit pull requests or improvements on [GitHub](https://github.com/community-charts/helm-charts).
* 🐛 Report bugs via our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Share ideas and request new features.

Thank you for being part of the community. Let’s keep building and improving n8n together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-02-n8n-chart-version-1-15-3-released.md)


---

# n8n chart version 1.15.4 released

September 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.15.4**, published on 2025-09-04. This update includes **app version 1.109.2**, delivering helpful enhancements, image updates, and contributions from our amazing open-source community.

Whether you're automating workflows or scaling self-hosted instances across Kubernetes clusters, this chart makes deploying and managing n8n both smoother and smarter.

## What’s new in version 1.15.4[​](#whats-new-in-version-1154 "Direct link to What’s new in version 1.15.4")

Here’s what’s included in this release:

* 🔄 **Updated**: Application image upgraded to `n8nio/n8n:1.109.2`
  * See the [n8n GitHub repository](https://github.com/n8n-io/n8n) for full details.

For the complete list of changes, check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.4) on GitHub.

<!-- -->

## Getting started with n8n 1.15.4[​](#getting-started-with-n8n-1154 "Direct link to Getting started with n8n 1.15.4")

Ready to deploy the latest version? Our comprehensive [n8n installation guides](https://community-charts.github.io/docs/category/n8n) walk you through every step:

* Quick install commands to get up and running fast.
* Customization tips for tailoring your configuration.
* Production-ready best practices for Kubernetes environments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to learn more and start building automated workflows on your terms.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), this Helm chart is built to make Kubernetes-based deployments of n8n seamless and reliable.

Here’s why developers and DevOps teams love it:

* ✅ **Simple setup**: Easy to install and upgrade with values you can control.
* 🌍 **Community-powered**: Maintained and improved by developers like you.
* 🛠️ **Highly configurable**: Flexible options for a variety of use cases.
* 🔐 **Production-ready**: Trusted and tested in Kubernetes-native stacks.

## Join the community[​](#join-the-community "Direct link to Join the community")

We’d love to have you on board! Whether you’re filing issues, sharing feedback, or proposing enhancements, your contributions help push the chart forward.

Ways to get involved:

* 📚 Read the [n8n chart documentation](https://community-charts.github.io/docs/category/n8n)
* ✅ Submit PRs to our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐛 Report problems via the [issues page](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest updates from the [feature request form](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the n8n and Kubernetes open-source community. Let’s keep building great things together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-04-n8n-chart-version-1-15-4-released.md)


---

# n8n chart version 1.15.5 released

September 9, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart — **v1.15.5** — is now available as of 2025-09-09! This update includes **app version 1.110.1**, delivering important improvements and updates driven by our vibrant open-source community.

## What’s New in Helm Chart 1.15.5[​](#whats-new-in-helm-chart-1155 "Direct link to What’s New in Helm Chart 1.15.5")

The v1.15.5 release brings the following update:

* 🔄 **Updated**: The Docker image has been bumped to `n8nio/n8n:1.110.1`, aligning the chart with the latest stable version of the application
  <br />
  <!-- -->
  → [Upstream Source](https://github.com/n8n-io/n8n)

For a full breakdown of changes, refer to our [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.5).

<!-- -->

## Get Started with n8n Helm Chart 1.15.5[​](#get-started-with-n8n-helm-chart-1155 "Direct link to Get Started with n8n Helm Chart 1.15.5")

Whether you're trying n8n for the first time or upgrading your existing deployment, our comprehensive [installation guide](https://community-charts.github.io/docs/category/n8n) has everything you need to get up and running. It covers:

* Quickstart deployment with default settings
* Custom configurations for advanced use cases
* Tips and best practices for production environments

Head over to the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to dive deeper and start automating with ease.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

Maintained by the open-source community, the n8n Helm chart simplifies deployment of n8n on Kubernetes. Here’s why it’s a great choice:

* 🚀 **Easy to Install**: Spin up workflows effortlessly on any Kubernetes environment.
* 🌎 **Community-Powered**: Built and continuously improved by passionate contributors.
* ⚙️ **Configurable**: Tailor deployment to suit your team’s needs with flexible values.
* ✅ **Production-Ready**: Regularly tested for reliability and performance.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The n8n Helm chart is part of the [GitHub Community Charts](https://github.com/community-charts/helm-charts) initiative — open to all and improved by people like you. Here’s how to get involved:

* 📘 Read the [full documentation](https://community-charts.github.io/docs/category/n8n)
* 🧑‍💻 Contribute via pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs on our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* ✨ Suggest features or enhancements [here](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the growing n8n and Kubernetes ecosystem. We look forward to your feedback and continued support!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-09-n8n-chart-version-1-15-5-released.md)


---

# n8n chart version 1.15.6 released

September 16, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **n8n Helm chart version 1.15.6** is now available as of 2025-09-16, featuring **app version 1.111.0**. This release includes fresh updates and enhancements that streamline your automation workflows on Kubernetes.

## What’s New in 1.15.6[​](#whats-new-in-1156 "Direct link to What’s New in 1.15.6")

This chart update brings you the latest improvements from the n8n community and upstream maintainers:

* ⬆️ **Upgraded**: n8nio/n8n Docker image to version 1.111.0
  <br />
  <!-- -->
  ↳ See the [n8n upstream project](https://github.com/n8n-io/n8n)

For the complete changelog, view the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.6) on GitHub.

<!-- -->

## Get Started with n8n 1.15.6[​](#get-started-with-n8n-1156 "Direct link to Get Started with n8n 1.15.6")

Deploying n8n 1.15.6 is easier than ever. Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* One-command installs with default values
* Custom configurations for your infrastructure
* Best practices for stable production deployments

Check out the full [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get started today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The n8n Helm chart, developed and maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, is built for reliability and flexibility. Benefits include:

* 🚀 **Quick Setup**: Launch n8n in minutes on Kubernetes
* 🧑‍🤝‍🧑 **Community Support**: Continuous enhancements by open-source contributors
* 🔧 **Customizable**: Tailor deployments to your workflows and environment
* ✅ **Proven Reliability**: Built and tested for Kubernetes environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We welcome contributors of all experience levels! Help shape the future of open-source Kubernetes charts:

* 📘 Learn more in our [documentation](https://community-charts.github.io/docs/category/n8n)
* 🔧 Contribute directly on [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs or 🧠 request new features in our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being a part of the n8n and Kubernetes open-source ecosystem. Let’s keep building powerful automation tools—together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-16-n8n-chart-version-1-15-6-released.md)


---

# n8n chart version 1.15.7 released

September 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.15.7**, officially published on 2025-09-19. This update features **app version 1.111.1**, delivering enhanced stability, usability, and the latest improvements straight from the open-source community.

## What’s New in Helm Chart 1.15.7[​](#whats-new-in-helm-chart-1157 "Direct link to What’s New in Helm Chart 1.15.7")

This release includes both Helm chart enhancements and an updated n8n application version. Here’s a summary of key changes:

* ✅ **Updated**: Upgraded Docker image to `n8nio/n8n:1.111.1`
  * Check out the source on the [Upstream Project](https://github.com/n8n-io/n8n)

For a full breakdown of updates, view the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.7) on GitHub.

<!-- -->

## Getting Started with n8n Helm Chart 1.15.7[​](#getting-started-with-n8n-helm-chart-1157 "Direct link to Getting Started with n8n Helm Chart 1.15.7")

Ready to upgrade or install n8n with the latest chart? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) will help you launch n8n on Kubernetes quickly and confidently:

* 🚀 Quick start with default configurations
* ⚙️ Customize settings to match your use case
* 🛠️ Follow production-ready best practices

Visit our [official documentation](https://community-charts.github.io/docs/category/n8n) to explore all configuration options and deploy n8n in your Kubernetes environment.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), this Helm chart simplifies Kubernetes deployments for n8n users. Benefits include:

* 🧩 **Easy Setup**: Simplified installation in just a few steps
* 🌱 **Community-Powered**: Regular enhancements from contributors worldwide
* 🧰 **Highly Configurable**: Adjust settings to your project’s needs
* 🧪 **Battle-Tested**: Proven stability across Kubernetes environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We believe in open-source collaboration and would love your support! Whether you're writing code or sharing ideas, here’s how you can get involved:

* 📚 Read the [documentation](https://community-charts.github.io/docs/category/n8n) to learn how the chart works
* 🔧 Contribute directly through [pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or suggest improvements in our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you for being part of the n8n and Kubernetes community. Together, we’re making DevOps and workflow automation more accessible for everyone.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-19-n8n-chart-version-1-15-7-released.md)


---

# n8n chart version 1.15.8 released

September 22, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest **n8n Helm chart version 1.15.8** is now available as of September 22, 2025. This release includes the latest **n8n application version 1.112.3**, delivering enhanced stability, new capabilities, and contributions from our awesome community.

## What’s new in n8n 1.15.8[​](#whats-new-in-n8n-1158 "Direct link to What’s new in n8n 1.15.8")

This version brings important updates to both the Helm chart (v1.15.8) and the application (v1.112.3). Here’s what’s included:

* 🔄 **Updated**: Docker image upgraded to `n8nio/n8n:1.112.3`
  <br />
  <!-- -->
  ↳ See full details on the [n8n repository](https://github.com/n8n-io/n8n)

For the complete changelog, visit the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.8) on GitHub.

<!-- -->

## How to Get Started with n8n 1.15.8[​](#how-to-get-started-with-n8n-1158 "Direct link to How to Get Started with n8n 1.15.8")

Ready to set up your n8n instance on Kubernetes? The [n8n installation guides](https://community-charts.github.io/docs/category/n8n) walk you through everything from initial setup to advanced configurations:

* 🚀 Fast installation with sensible defaults
* ⚙️ Full customization to suit your deployment needs
* ✅ Recommended practices for production-ready deployments

Explore all available options by visiting our [documentation](https://community-charts.github.io/docs/category/n8n).

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, this Helm chart makes deploying n8n on Kubernetes easier and more reliable than ever. You’ll benefit from:

* ✅ Easy-to-follow setup and config
* 👥 Backed by a growing open-source community
* 🔧 Flexible settings for many use cases
* 🔒 Built-in reliability tested across environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The n8n chart is powered by passionate contributors. Whether you're a developer, documenter, or advocate, there are plenty of ways to get involved:

* 🔍 Learn the chart by reviewing the [official docs](https://community-charts.github.io/docs/category/n8n)
* 🤝 Contribute enhancements via [pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs or issues on the [GitHub issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest features and improvements to help guide the roadmap

Thanks for being part of the n8n journey. Together, we’re building a better way to automate on Kubernetes.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-22-n8n-chart-version-1-15-8-released.md)


---

# n8n chart version 1.15.9 released

September 23, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to announce the release of the latest Helm chart for n8n: **version 1.15.9**, now available as of September 23, 2025. This version includes **app version 1.112.4**, packed with improvements inspired by contributions from our vibrant open-source community.

## What’s New in Helm Chart 1.15.9[​](#whats-new-in-helm-chart-1159 "Direct link to What’s New in Helm Chart 1.15.9")

This release introduces key updates to both the Helm chart and the n8n application:

* 🔄 **Updated**: n8nio/n8n Docker image now uses version 1.112.4
  <!-- -->
  * [View Upstream Repository](https://github.com/n8n-io/n8n)

For a detailed breakdown, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.9) on GitHub.

<!-- -->

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Deploying n8n version 1.15.9 is easier than ever. Head over to our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) for everything you need to get up and running:

* Get started quickly with default settings
* Tailor configurations to fit your infrastructure
* Follow best practices for seamless production deployments

Whether you're exploring automation or scaling workflows on Kubernetes, our docs have you covered.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The n8n Helm chart, maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, simplifies Kubernetes deployments with:

* ⚙️ **Ease of Use**: One-command installations with sensible defaults
* 🌍 **Community-Driven**: Frequent updates shaped by user feedback
* 🎯 **Customizability**: Fine-tune chart values to match your environment
* 💡 **Stability**: Built and tested to run reliably in Kubernetes clusters

It's the easiest way to run your n8n workflows with confidence in any cloud-native setup.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We're proud to build this chart in partnership with the open-source community — and your input makes it better! Get involved:

* Dive into the [n8n chart docs](https://community-charts.github.io/docs/category/n8n) for tips and configuration help
* Contribute to the project by submitting [pull requests](https://github.com/community-charts/helm-charts)
* Report bugs or suggest new features in our [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you for being part of the n8n and GitHub Community Charts community. Let’s keep simplifying automation on Kubernetes, together.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-23-n8n-chart-version-1-15-9-released.md)


---

# n8n chart version 1.16.0 now available

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.16.0**, launched on November 8, 2025, featuring the latest **app version 1.118.2**. This update includes enhancements that make it even easier to deploy and manage n8n on Kubernetes.

## What’s new in version 1.16.0[​](#whats-new-in-version-1160 "Direct link to What’s new in version 1.16.0")

This version improves the Helm chart configuration to ensure smoother deployments. Here’s a highlight from the changelog:

* ✅ **Fix**: Corrected the default license server URL schema definition
  <!-- -->
  * [View Pull Request](https://github.com/community-charts/helm-charts/pull/260)

To explore everything included in this release, check out the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.0) on GitHub.

<!-- -->

## Get started with the n8n 1.16.0 chart[​](#get-started-with-the-n8n-1160-chart "Direct link to Get started with the n8n 1.16.0 chart")

Deploying n8n on Kubernetes is simpler than ever. Whether you're evaluating the platform or preparing for production, our [official documentation](https://community-charts.github.io/docs/category/n8n) walks you through every step:

* Quick start with default setup
* Advanced configuration and scaling options
* Deployment best practices for production environments

Start your installation today and integrate automated workflows into your Kubernetes cluster with ease.

## Why use the community-maintained Helm chart?[​](#why-use-the-community-maintained-helm-chart "Direct link to Why use the community-maintained Helm chart?")

Built and maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the n8n Helm chart is the most flexible and reliable way to run n8n on Kubernetes:

* 🧩 **Configurable**: Tailor your install to match your infrastructure and use case
* 🚀 **Effortless**: Quick setup with smart defaults
* 🤝 **Community-Driven**: Actively maintained with regular updates
* 🔄 **Stable**: Continuously tested for compatibility with Kubernetes

Whether you’re building simple automations or complex workflows, you’ll benefit from a streamlined deployment experience.

## Join the open-source community[​](#join-the-open-source-community "Direct link to Join the open-source community")

We thrive thanks to community contributions. Here's how you can get involved:

* 📚 Explore the [n8n documentation](https://community-charts.github.io/docs/category/n8n)
* 🛠 Submit pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 [Report issues](https://github.com/community-charts/helm-charts/issues) or request new features
* 💬 Participate in discussions and help shape future chart releases

Thank you for using n8n and contributing to the GitHub Community Charts project. Together, we’re building a better automation ecosystem on Kubernetes!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-08-n8n-chart-version-1-16-0-released.md)


---

# n8n chart version 1.16.1 released

November 11, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.16.1**, now available as of November 11, 2025. This update includes **app version 1.119.1**, bringing fresh enhancements and performance improvements to help you easily deploy and manage n8n on Kubernetes.

## What’s New in Helm Chart 1.16.1[​](#whats-new-in-helm-chart-1161 "Direct link to What’s New in Helm Chart 1.16.1")

This release updates both the Helm chart and the underlying app version, incorporating key community contributions and dependency upgrades:

* 🔄 **Updated**: Base image upgraded to `n8nio/n8n:1.119.1`
  <br />
  <!-- -->
  → [View Project on GitHub](https://github.com/n8n-io/n8n)
* 🔧 **Updated**: Redis chart bumped from `23.2.6` to `23.2.12`
  <br />
  <!-- -->
  → [Redis via ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🛠️ **Updated**: PostgreSQL chart upgraded from `18.1.4` to `18.1.8`
  <br />
  <!-- -->
  → [PostgreSQL via ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of changes, check out the [n8n 1.16.1 release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.1) on GitHub.

<!-- -->

## How to Get Started with n8n 1.16.1[​](#how-to-get-started-with-n8n-1161 "Direct link to How to Get Started with n8n 1.16.1")

Deploying the latest version of n8n is easy with our detailed [installation guides](https://community-charts.github.io/docs/category/n8n). Whether you're setting up for development or production, we’ve got you covered:

* ✅ Quick start with default values.
* ⚙️ Custom configurations to suit your environment.
* 🔐 Best practices for secure, production-ready deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get started.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the n8n Helm chart offers a powerful and flexible approach to deploying n8n on Kubernetes:

* 🚀 Fast and simple deployments
* 🎯 Configurable to fit diverse use cases
* 🤝 Community-supported and regularly updated
* 🧪 Stability tested for real-world environments

Whether you're building automated workflows or managing complex integrations, this Helm chart provides the foundation you need.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Want to contribute, get support, or just stay connected? The GitHub Community Charts team welcomes your input and collaboration.

* 📚 Learn more in the [n8n chart documentation](https://community-charts.github.io/docs/category/n8n)
* 🧑‍💻 Submit a pull request on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Found a bug? [Open an issue](https://github.com/community-charts/helm-charts/issues)
* 💡 Share ideas or request new features in our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of our growing open-source community. Together, we’re making Kubernetes deployments better—one chart at a time.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-11-n8n-chart-version-1-16-1-released.md)


---

# n8n chart version 1.16.10 released

December 11, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to announce the release of the **n8n Helm chart version 1.16.10**, published on 2025-12-11! This update includes **n8n app version 1.123.5** and delivers enhanced features, updated dependencies, and community-powered improvements—making your Kubernetes deployments even smoother.

## What’s New in 1.16.10[​](#whats-new-in-11610 "Direct link to What’s New in 1.16.10")

Here's an overview of the key updates in this release:

* 🔄 **Updated Image**: Bumped the `n8nio/n8n` container image to version **1.123.5**
  <br />
  <!-- -->
  → [View upstream project](https://github.com/n8n-io/n8n)
* 🛠️ **Dependency Update**: Upgraded Redis from `24.0.0` to `24.0.4`
  <br />
  <!-- -->
  → [View Redis chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For the full changelog, check out the official release notes on [GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.10).

<!-- -->

## Getting Started with n8n 1.16.10[​](#getting-started-with-n8n-11610 "Direct link to Getting Started with n8n 1.16.10")

Ready to try out the latest version? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through deploying n8n with Helm:

* Quick setup using default values
* Advanced configuration for your specific environment
* Production-ready setup tips

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get started today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The n8n Helm chart, maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, simplifies running n8n on Kubernetes. Here’s why it stands out:

* ⚙️ **User-Friendly**: Get up and running quickly with minimal effort
* 👥 **Community-Driven**: Developed and maintained by open-source contributors
* 🔧 **Highly Configurable**: Adapt the chart to meet your unique workflow needs
* 🧪 **Reliable**: Thoroughly tested for stable production use

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’re building n8n with and for the community. If you’d like to contribute—whether it’s fixing bugs, enhancing docs, or recommending features—we’d love to have your support:

* 📘 [Explore our docs](https://community-charts.github.io/docs/category/n8n) for full chart configurations
* 👩‍💻 [Contribute on GitHub](https://github.com/community-charts/helm-charts) with pull requests
* 🐛 [Open an issue](https://github.com/community-charts/helm-charts/issues) for bugs or feedback
* 💡 [Propose a feature](https://github.com/community-charts/helm-charts/issues/new) to improve the project

Thanks for being part of the journey with n8n and GitHub Community Charts. Let’s keep empowering developers to streamline their automations in the Kubernetes ecosystem!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-11-n8n-chart-version-1-16-10-released.md)


---

# n8n chart version 1.16.11 released

December 16, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart—**v1.16.11**, featuring **application version 2.0.2**—is now available! Released on 2025-12-16, this update delivers valuable enhancements for deploying n8n on Kubernetes with smoother workflows and better flexibility.

<!-- -->

## Highlights of Helm Chart v1.16.11[​](#highlights-of-helm-chart-v11611 "Direct link to Highlights of Helm Chart v1.16.11")

This release brings key updates to both the Helm chart and the n8n application itself. Here’s what’s new in version 1.16.11:

* 🔄 **Updated**: Upgraded the n8nio/n8n container image to **v2.0.2**<br /><!-- -->→ [See on GitHub](https://github.com/n8n-io/n8n)

* 🧱 **Redis**: Bumped Redis Helm dependency from **v24.0.4** to **v24.0.8**<br /><!-- -->→ [View Redis Chart](https://artifacthub.io/packages/helm/bitnami/redis) on ArtifactHub

* 🗄️ **PostgreSQL**: Updated PostgreSQL Helm dependency from **v18.1.13** to **v18.1.14**<br /><!-- -->→ [View PostgreSQL Chart](https://artifacthub.io/packages/helm/bitnami/postgresql) on ArtifactHub

Want the full list of updates? Check out the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.11).

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Getting up and running with the new release is easy! Our detailed [n8n installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* Installing with default settings using Helm.
* Customizing configurations to suit your environment.
* Optimizing for production-ready setups.

Deploy confidently with helpful documentation and best practices from the community.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the open-source contributors at [GitHub Community Charts](https://github.com/community-charts/helm-charts), this Helm chart streamlines n8n deployments on Kubernetes. Benefits include:

* ✅ **Easy Setup**: Start automating workflows in minutes.
* 🚀 **Community-Driven**: Developed and improved by experts and users.
* ⚙️ **Customizable**: Fine-tune parameters to match your architecture.
* 🔒 **Stable**: Regularly tested across modern Kubernetes environments.

Whether you're creating automations for personal productivity or handling enterprise workflows, this chart gives you the reliability and flexibility you need.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We're always looking for passionate contributors to help grow the project. Get involved and make an impact:

* 📚 Dive into the [n8n docs](https://community-charts.github.io/docs/category/n8n) to learn more.
* 🔧 Submit improvements or fixes through [pull requests](https://github.com/community-charts/helm-charts).
* 🐛 Report issues or bugs via the [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Suggest features to shape future development.

Thanks for being part of the n8n and Kubernetes community. Together, we’re building powerful, accessible automation at scale.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-16-n8n-chart-version-1-16-11-released.md)


---

# n8n chart version 1.16.12 released

December 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest **n8n Helm chart version 1.16.12**, available as of December 18, 2025. This version features the updated **application version 2.0.3**, bringing improved stability and new features that make running n8n on Kubernetes even smoother.

## What’s New in n8n 1.16.12[​](#whats-new-in-n8n-11612 "Direct link to What’s New in n8n 1.16.12")

This release focuses on keeping your deployment up to date with the latest from the n8n team. Here's what’s included in v1.16.12:

* 🔄 **Updated**: Upgraded Docker image to `n8nio/n8n:2.0.3`
  <br />
  <!-- -->
  → [View the upstream project on GitHub](https://github.com/n8n-io/n8n)

To see the full changelog, take a look at the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.12) on GitHub.

<!-- -->

## How to Deploy n8n with the 1.16.12 Chart[​](#how-to-deploy-n8n-with-the-11612-chart "Direct link to How to Deploy n8n with the 1.16.12 Chart")

Getting started is easy! Our complete [installation documentation](https://community-charts.github.io/docs/category/n8n) walks you through:

* Quick-start instructions with out-of-the-box configurations
* Advanced customization options to fit your workflow
* Production-ready deployment tips for better performance and reliability

Start your deployment journey with the [n8n Helm chart documentation](https://community-charts.github.io/docs/category/n8n).

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The n8n Helm chart is a powerful, community-supported tool designed to simplify deploying workflows with Kubernetes. Here’s why users love it:

* ✅ **Simple Installation**: Deploy in minutes with Helm and Kubernetes
* 🤝 **Built by the Community**: Contributions from passionate developers and users
* ⚙️ **Flexible Configuration**: Tailor it to suit your Kubernetes setup
* 💡 **Reliable Experience**: Continuously tested and actively improved

Developed and maintained by the [GitHub Community Charts team](https://github.com/community-charts/helm-charts), this chart makes workflow automation accessible for teams running on Kubernetes.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

This project thrives thanks to contributions from users like you! Whether you're new to Helm or a seasoned Kubernetes pro, you’re welcome to get involved:

* 📚 Dive into the [documentation](https://community-charts.github.io/docs/category/n8n) to learn and share knowledge
* 🛠 Contribute via [pull requests](https://github.com/community-charts/helm-charts) to improve the chart
* 🐛 Found a bug? Report it through our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Have an idea? Suggest new features or enhancements

Thank you for being part of the open-source community. Let’s keep building better automation experiences—together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-18-n8n-chart-version-1-16-12-released.md)


---

# n8n chart version 1.16.13 released

December 23, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the launch of **n8n Helm chart version 1.16.13**, released on December 23, 2025. This chart now supports **app version 2.1.2**, bringing new capabilities, performance updates, and seamless Kubernetes deployment improvements.

## What’s New in Helm Chart 1.16.13[​](#whats-new-in-helm-chart-11613 "Direct link to What’s New in Helm Chart 1.16.13")

This release introduces important component updates and dependency refinements for a more stable and powerful deployment experience. Here's what's included:

* ✅ **Upgraded**: n8n image to version 2.1.2<br /><!-- -->➤ [Upstream GitHub Repository](https://github.com/n8n-io/n8n)

* 🔄 **Updated**: Redis dependency from 24.0.8 to 24.1.0<br /><!-- -->➤ [View Redis on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 🔄 **Updated**: PostgreSQL dependency from 18.1.14 to 18.1.15<br /><!-- -->➤ [View PostgreSQL on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of enhancements and changes, check out the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.13).

<!-- -->

## Getting Started with n8n 1.16.13[​](#getting-started-with-n8n-11613 "Direct link to Getting Started with n8n 1.16.13")

Looking to upgrade or launch your n8n instance? Our official [installation documentation](https://community-charts.github.io/docs/category/n8n) walks you through:

* Quick-start deployment using default values
* Fine-tuning configurations for custom environments
* Production-ready deployment best practices

Whether you're new to n8n or a seasoned Kubernetes user, you'll find everything you need to get up and running smoothly.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart makes deploying workflows on Kubernetes easy and flexible. Key advantages:

* 🔧 **Simple Configuration**: Set up with just a few commands
* 🌍 **Open-Source & Community-Driven**: Constantly evolving with contributions
* ⚙️ **Customizable**: Adapt to your organization’s needs
* 🤝 **Reliable**: Built and tested for production-ready Kubernetes environments

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’re building n8n Helm charts together—and we’d love your help! Here's how you can contribute:

* 📘 Read the [docs](https://community-charts.github.io/docs/category/n8n) to understand configuration options
* 👩‍💻 Submit improvements via [pull requests](https://github.com/community-charts/helm-charts)
* 🐛 Report issues through the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features to enhance the chart for everyone

Thanks for supporting the n8n community and helping us build better Kubernetes experiences—one release at a time!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-23-n8n-chart-version-1-16-13-released.md)


---

# n8n chart version 1.16.14 released

December 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.16.14**, published on December 24, 2025. This latest release includes **application version 2.1.4** and brings several enhancements and updates that improve deploying and managing n8n on Kubernetes.

## Highlights of the n8n 1.16.14 Release[​](#highlights-of-the-n8n-11614-release "Direct link to Highlights of the n8n 1.16.14 Release")

This version introduces key updates to both the Helm chart and the n8n application:

* 🔄 **Updated** n8nio/n8n Docker image to version `2.1.4`
  <br />
  <!-- -->
  → [View upstream repo](https://github.com/n8n-io/n8n)
* 🗃️ **Updated** PostgreSQL chart dependency from `18.1.15` to `18.2.0`
  <br />
  <!-- -->
  → [See ArtifactHub Listing](https://artifacthub.io/packages/helm/bitnami/postgresql)

These updates help ensure greater stability, improved performance, and compatibility with new features.

Check out the complete release changelog on our [GitHub release page](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.14).

<!-- -->

## Get Started with n8n 1.16.14[​](#get-started-with-n8n-11614 "Direct link to Get Started with n8n 1.16.14")

Ready to deploy? Our user-friendly [installation guides](https://community-charts.github.io/docs/category/n8n) are here to help. Whether you're new to Helm or a Kubernetes pro, you’ll find everything you need, including:

* Easy setup with default values
* Custom configuration tips
* Best practices for reliable production deployments

Visit the [n8n docs](https://community-charts.github.io/docs/category/n8n) to start your deployment journey today.

## Why Use the Official n8n Helm Chart?[​](#why-use-the-official-n8n-helm-chart "Direct link to Why Use the Official n8n Helm Chart?")

Backed by the GitHub Community Charts team, this chart is designed to simplify scalable, production-grade installations of n8n on Kubernetes. Here's why users love it:

* ⚙️ **Simple Setup**: Deploy quickly with minimal configuration
* 🧩 **Customizable**: Tune your instance for any workflow or environment
* 🤝 **Community-Powered**: Improvements and fixes driven by contributors
* 📦 **Reliable**: Tested for performance and stability in Kubernetes clusters

## Join the n8n Community[​](#join-the-n8n-community "Direct link to Join the n8n Community")

This chart is maintained by a vibrant and growing open-source community — and you can be a part of it! Whether you’re submitting bug fixes, improving docs, or proposing new features, here’s how to get started:

* Dive into the [n8n chart documentation](https://community-charts.github.io/docs/category/n8n)
* Contribute via [pull requests on GitHub](https://github.com/community-charts/helm-charts)
* Report issues or request new features via the [GitHub issue tracker](https://github.com/community-charts/helm-charts/issues)

We appreciate your support and look forward to building better Kubernetes tools together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-24-n8n-chart-version-1-16-14-released.md)


---

# n8n chart version 1.16.2 released

November 14, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to announce that the latest version of the n8n Helm chart—**v1.16.2**—is now available as of 2025-11-14, featuring **application version 1.119.2**. This release brings enhanced functionality, updated components, and valuable contributions from the open-source community to help streamline your n8n deployments on Kubernetes.

## What’s New in Chart Version 1.16.2[​](#whats-new-in-chart-version-1162 "Direct link to What’s New in Chart Version 1.16.2")

The n8n Helm chart version 1.16.2 includes the following updates and improvements:

* 🔄 **n8n Image Updated**: Upgraded the container image to `n8nio/n8n:1.119.2`
  <br />
  <!-- -->
  ➤ [View Upstream Project](https://github.com/n8n-io/n8n)
* 🛠️ **PostgreSQL Dependency Update**: Bumped Bitnami PostgreSQL Helm dependency from 18.1.8 to 18.1.9
  <br />
  <!-- -->
  ➤ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of changes and technical details, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.2) on GitHub.

<!-- -->

## How to Get Started[​](#how-to-get-started "Direct link to How to Get Started")

Ready to upgrade or deploy n8n with version 1.16.2? Our [step-by-step installation guides](https://community-charts.github.io/docs/category/n8n) make it easy:

* 🚀 Quick install with default settings
* ⚙️ Easily customize configurations for your needs
* 🛡️ Follow best practices for production environments

Explore the full [n8n Helm documentation](https://community-charts.github.io/docs/category/n8n) for everything you need to get started today.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the n8n Helm chart is the easiest way to deploy automation workflows on Kubernetes. Here's why developers and DevOps professionals love it:

* 🧩 Simple and flexible deployment options
* 🙌 Supported and improved by a passionate open-source community
* 🧪 Tested and trusted in Kubernetes production environments
* 🌐 Ideal for both hobby projects and enterprise use cases

## Join Our Community[​](#join-our-community "Direct link to Join Our Community")

We welcome all contributions! Whether you're reporting a bug, improving documentation, or suggesting new features, there are many ways to get involved:

* 📄 Learn configuration options in the [n8n docs](https://community-charts.github.io/docs/category/n8n)
* 🤝 Send a pull request via our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Submit issues and feature ideas on our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the community helping to grow and improve open-source automation tooling like n8n. Let's build together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-14-n8n-chart-version-1-16-2-released.md)


---

# n8n chart version 1.16.3 released

November 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the n8n Helm chart, version 1.16.3, is now available as of November 19, 2025. This update includes the latest **n8n app version 1.120.3**, delivering enhanced performance and features thanks to our supportive community.

## Highlights of the 1.16.3 Release[​](#highlights-of-the-1163-release "Direct link to Highlights of the 1.16.3 Release")

This release refreshes both the Helm chart and the application version to bring you a better deployment experience on Kubernetes. Key changes include:

* 📦 Updated n8n image to version **1.120.3**
  <br />
  <!-- -->
  → [View on GitHub](https://github.com/n8n-io/n8n)
* 🛠️ Bumped PostgreSQL dependency from **18.1.9** to **18.1.10**
  <br />
  <!-- -->
  → [ArtifactHub listing](https://artifacthub.io/packages/helm/bitnami/postgresql)

Explore the full details in our [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.3).

<!-- -->

## Get Started with the Latest Chart[​](#get-started-with-the-latest-chart "Direct link to Get Started with the Latest Chart")

Ready to deploy n8n using version 1.16.3 of our Helm chart? We’ve got you covered with easy-to-follow guides, whether you’re just testing it out or managing a production system.

Visit our [n8n documentation](https://community-charts.github.io/docs/category/n8n) for:

* Quick setup instructions
* Configuration tips to match your workflow
* Production-friendly deployment strategies

Make the most of Kubernetes with our flexible and reliable Helm chart.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the n8n Helm chart streamlines your Kubernetes deployments. Here’s why users love it:

* ✔️ Easy installation and customization
* 🔄 Regular updates powered by the open-source community
* ⚙️ Robust configuration options for diverse use cases
* 🔒 Built for stability in Kubernetes environments

Whether you're running n8n in the cloud or on-premises, our chart helps you stay up-to-date and secure.

## Your Contributions Matter[​](#your-contributions-matter "Direct link to Your Contributions Matter")

The GitHub Community Charts project thrives with your help! If you're passionate about open-source, here’s how you can make an impact:

* 📘 Dive into our [n8n chart docs](https://community-charts.github.io/docs/category/n8n)
* 🛠️ Contribute via [pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs using our [issues page](https://github.com/community-charts/helm-charts/issues)
* 💡 Submit features through [new issues](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of our community. Let’s build better Kubernetes-native solutions together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-19-n8n-chart-version-1-16-3-released.md)


---

# n8n chart version 1.16.4 now available

November 20, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of **n8n Helm chart version 1.16.4**, featuring the latest **app version 1.120.4**, available as of November 20, 2025. This release introduces valuable updates and community-powered improvements to make deploying n8n on Kubernetes even smoother.

## What’s new in version 1.16.4[​](#whats-new-in-version-1164 "Direct link to What’s new in version 1.16.4")

This release updates the Helm chart to version 1.16.4 and bumps the underlying n8n application to version 1.120.4. Changes include:

* ✅ Updated: `n8nio/n8n` image upgraded to version 1.120.4
  <br />
  <!-- -->
  → View the [n8n GitHub repository](https://github.com/n8n-io/n8n)

To view the full changelog, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.4) on GitHub.

<!-- -->

## Start using n8n 1.16.4 today[​](#start-using-n8n-1164-today "Direct link to Start using n8n 1.16.4 today")

Getting started with the latest n8n chart is easy. Our comprehensive [installation documentation](https://community-charts.github.io/docs/category/n8n) includes:

* Step-by-step installation using default values
* Guidance for customizing the deployment to fit your needs
* Best practices for production-grade environments

Dive into the [n8n deployment docs](https://community-charts.github.io/docs/category/n8n) and get started today.

## Why use the n8n Helm chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why use the n8n Helm chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the n8n Helm chart provides a streamlined way to deploy n8n on Kubernetes with:

* 🛠️ Simple and fast setup
* 🌍 A vibrant and supportive open-source community
* 🔧 Flexible configuration options
* 📦 Stability and reliability for CI/CD and automation

## Join the community[​](#join-the-community "Direct link to Join the community")

This chart is driven by contributions from people like you. Whether you're new to Helm or a seasoned Kubernetes user, there are many ways to get involved:

* 👀 Browse the [docs](https://community-charts.github.io/docs/category/n8n) to learn how the chart works
* ✍️ Contribute enhancements via our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Found an issue? [Report it here](https://github.com/community-charts/helm-charts/issues)
* 💡 Have a feature idea? [Share your suggestions](https://github.com/community-charts/helm-charts/issues/new)

Thank you to all contributors and users supporting n8n and the Community Charts project. Together, we’re building a smarter Kubernetes automation experience!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-20-n8n-chart-version-1-16-4-released.md)


---

# n8n chart version 1.16.45 released

June 2, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share that the **n8n Helm chart version 1.16.45** has been officially released as of June 2, 2026, featuring **app version 2.22.6**. This latest update introduces a host of new features, enhancements, and community-driven improvements designed to streamline the deployment of n8n on Kubernetes.

## What's New in n8n 1.16.45 chart[​](#whats-new-in-n8n-11645-chart "Direct link to What's New in n8n 1.16.45 chart")

The release of the n8n chart version 1.16.45 includes notable updates to the Helm chart alongside the underlying application version 2.22.6. Here’s a brief overview of the key changes:

* **Changed**: Updated the n8nio/n8n image version to 2.22.6
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Upgraded the PostgreSQL dependency from version 18.6.8 to 18.7.0
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For more detailed information, please check out the complete [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.45) on GitHub.

<!-- -->

## Getting Started with n8n 1.16.45 chart[​](#getting-started-with-n8n-11645-chart "Direct link to Getting Started with n8n 1.16.45 chart")

Are you ready to deploy n8n 1.16.45? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) offer step-by-step instructions to help you get started, including:

* Quick installation with default configurations.
* Customization options tailored to your specific environment.
* Best practices for effective production deployments.

Explore all available options and start your n8n journey today by visiting the [n8n documentation](https://community-charts.github.io/docs/category/n8n).

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to simplify and ensure reliable deployments of n8n on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy a streamlined installation and configuration process.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our vibrant community.
* **Flexibility**: Access various configurable options to accommodate diverse use cases.
* **Reliability**: Rest assured, as this chart is tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community engagement, and we warmly invite you to contribute! Whether you're interested in fixing bugs, enhancing documentation, or suggesting new features, here’s how you can contribute:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration information.
* **Contribute**: Share your improvements by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a bug? [Let us know](https://github.com/community-charts/helm-charts/issues) so we can address it.
* **Request Features**: Share your ideas for new features through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of n8n and GitHub Community Charts. Together, we can make Kubernetes deployments easier and more accessible!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-02-n8n-chart-version-1-16-45-released.md)


---

# n8n Chart Version 1.16.46 Released

June 2, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the launch of the **n8n Helm Chart Version 1.16.46** on June 2, 2026, featuring **app version 2.23.2**. This release introduces new features, enhancements, and community-driven improvements, designed to simplify your n8n deployment on Kubernetes.

## What's New in the n8n 1.16.46 Chart[​](#whats-new-in-the-n8n-11646-chart "Direct link to What's New in the n8n 1.16.46 Chart")

This release includes updates to both the Helm chart (version 1.16.46) and the underlying application (version 2.23.2). Here’s a look at the key changes:

* **Updated**: n8nio/n8n image version updated to 2.23.2
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Updated**: Redis dependency upgraded from version 25.5.3 to 27.0.0
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For a comprehensive overview of all changes, please check the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.46) on GitHub.

<!-- -->

## Getting Started with the n8n 1.16.46 Chart[​](#getting-started-with-the-n8n-11646-chart "Direct link to Getting Started with the n8n 1.16.46 Chart")

Ready to get n8n 1.16.46 up and running? Our [installation guides](https://community-charts.github.io/docs/category/n8n) offer step-by-step instructions to help you launch n8n quickly and efficiently. You’ll find:

* A quick installation guide with default configurations.
* Instructions for customizing settings to fit your environment.
* Best practices for deploying in a production setting.

Explore our [n8n documentation](https://community-charts.github.io/docs/category/n8n) to discover all the options available and start deploying today!

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, managed by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is created to make deploying n8n on Kubernetes both straightforward and dependable. Here are some key benefits:

* **Ease of Use**: Enjoy a simplified installation and configuration process.
* **Community-Driven**: Benefit from continuous updates and enhancements from our contributors.
* **Flexibility**: Access configurable options to meet a variety of use cases.
* **Reliability**: Rely on a solution thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

At GitHub Community Charts, we believe in the power of community contributions, and we would love your involvement! Whether you are fixing bugs, enhancing documentation, or proposing new features, here’s how you can contribute:

* **Explore the Chart**: Review the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration options.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Together, let's make Kubernetes deployments easier and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-02-n8n-chart-version-1-16-46-released.md)


---

# n8n chart version 1.16.47 released

June 5, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.16.47** on June 5, 2026, which includes the highly anticipated **app version 2.23.3**. This update is packed with new features, enhancements, and valuable community-driven improvements to streamline the deployment of n8n on Kubernetes.

## What's New in the n8n 1.16.47 Chart[​](#whats-new-in-the-n8n-11647-chart "Direct link to What's New in the n8n 1.16.47 Chart")

This release encompasses updates not only to the Helm chart (version 1.16.47) but also to the underlying application (version 2.23.3). Below are the key highlights from the changelog:

* **Changed**: Updated the n8nio/n8n image to version 2.23.3

  * [Upstream Project](https://github.com/n8n-io/n8n)

* **Added**: Set unhealthyPodEvictionPolicy to AlwaysAllow in PodDisruptionBudgets for main, worker, and webhook nodes.

* **Changed**: Adjusted PDB default from minAvailable 1 to maxUnavailable 1 for main, worker, and webhook nodes.

For a comprehensive overview of all changes, be sure to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.47) on GitHub.

<!-- -->

## Getting Started with the n8n 1.16.47 Chart[​](#getting-started-with-the-n8n-11647-chart "Direct link to Getting Started with the n8n 1.16.47 Chart")

Ready to deploy n8n version 1.16.47? Our [installation guides](https://community-charts.github.io/docs/category/n8n) offer detailed, step-by-step instructions to help you get up and running quickly, including:

* Quick installation with default configurations.
* Customization tips to tailor settings to your environment.
* Best practices for successful production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and start deploying n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to make deploying n8n on Kubernetes smooth and dependable. Here are some key benefits:

* **Ease of Use**: Enjoy simplified installation and configuration processes.
* **Community-Driven**: Benefit from regular updates and enhancements from a dedicated contributor network.
* **Flexibility**: Access configurable options designed to meet a variety of use cases.
* **Reliability**: Each version is thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

At GitHub Community Charts, we thrive on community contributions! We would love for you to be a part of our project. Whether you're fixing bugs, enhancing documentation, or suggesting new features, here’s how to get involved:

* **Explore the Chart**: Check out the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration information.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encounter a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and the GitHub Community Charts project. Together, let’s make Kubernetes deployments easier and more enjoyable!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-05-n8n-chart-version-1-16-47-released.md)


---

# n8n chart version 1.16.48 released

June 5, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the release of the **n8n Helm chart version 1.16.48** on June 5, 2026, featuring **app version 2.23.3**. This update introduces a range of new features, enhancements, and community-driven improvements to make your deployment of n8n on Kubernetes even smoother.

## What's New in n8n 1.16.48 chart[​](#whats-new-in-n8n-11648-chart "Direct link to What's New in n8n 1.16.48 chart")

This release encompasses updates to the Helm chart (version 1.16.48) along with the underlying application (version 2.23.3). Here’s a glimpse of the changes included:

* **Fixed**: The unhealthyPodEvictionPolicy is now configurable on PodDisruptionBudgets for main, worker, and webhook nodes (defaults to AlwaysAllow, requires Kubernetes >= 1.26).

For a detailed list of changes, please view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.48) on GitHub.

<!-- -->

## Getting Started with n8n 1.16.48 chart[​](#getting-started-with-n8n-11648-chart "Direct link to Getting Started with n8n 1.16.48 chart")

Ready to deploy n8n 1.16.48? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide comprehensive step-by-step instructions to help you get started:

* Quick installation with default configurations.
* Customization of settings tailored to your environment.
* Best practices for production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all the available options and deploy n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is tailored to streamline your deployment of n8n on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy simplified installation and configuration.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our dedicated community.
* **Flexibility**: Access configurable options to accommodate a variety of use cases.
* **Reliability**: Trust in the stability of tested deployments in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community involvement, and we invite you to contribute! Whether it’s fixing bugs, improving documentation, or suggesting new features, here’s how you can get started:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement ideas via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of n8n and the GitHub Community Charts. Together, let’s make Kubernetes deployments easier and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-05-n8n-chart-version-1-16-48-released.md)


---

# n8n chart version 1.16.49 released

June 5, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the release of the **n8n Helm chart version 1.16.49** on June 5, 2026, featuring **app version 2.23.3**. This update introduces a variety of new features, enhancements, and improvements driven by our vibrant community, designed to make deploying n8n on Kubernetes even easier.

## What’s New in the n8n 1.16.49 Chart[​](#whats-new-in-the-n8n-11649-chart "Direct link to What’s New in the n8n 1.16.49 Chart")

This version includes updates to both the Helm chart (1.16.49) and the underlying application (2.23.3). Here’s a glimpse of what’s included in this release:

* **Added**: Missing webhook URL to worker
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/406)

For a comprehensive look at all the changes, check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.49) on GitHub.

<!-- -->

## Getting Started with the n8n 1.16.49 Chart[​](#getting-started-with-the-n8n-11649-chart "Direct link to Getting Started with the n8n 1.16.49 Chart")

Are you ready to deploy n8n 1.16.49? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide everything you need to hit the ground running, including:

* Quick installation with default settings.
* Customization options to fit your unique environment.
* Best practices to ensure a smooth production deployment.

Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and get n8n deployed today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is your go-to solution for deploying n8n on Kubernetes with ease. Here are some benefits of using our chart:

* **Ease of Use**: Enjoy a streamlined installation and configuration process.
* **Community-Driven**: Benefit from regular updates and enhancements from our contributors.
* **Flexibility**: Take advantage of configurable options designed for various use cases.
* **Reliability**: Deploy with confidence knowing the chart has been tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community contributions, and we welcome your participation! Whether you’re fixing bugs, improving documentation, or proposing new features, there are many ways to get involved:

* **Explore the Chart**: Visit our [n8n documentation](https://community-charts.github.io/docs/category/n8n) for more configuration details.
* **Contribute**: Share your improvements by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Have an idea for improvement? Suggest it through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of n8n and GitHub Community Charts. Together, let’s continue to simplify Kubernetes deployments!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-05-n8n-chart-version-1-16-49-released.md)


---

# n8n chart version 1.16.5 released

November 26, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the **n8n Helm chart (v1.16.5)** is now available as of 2025-11-26. This release includes **n8n application version 1.121.2**, bringing valuable updates, dependency upgrades, and community-backed enhancements to improve your deployment experience on Kubernetes.

## What’s New in n8n Chart v1.16.5[​](#whats-new-in-n8n-chart-v1165 "Direct link to What’s New in n8n Chart v1.16.5")

Here’s a quick look at what’s included in this release:

* 📦 **App Update**: Upgraded to n8n version 1.121.2
  <br />
  <!-- -->
  ➤ [View the upstream project](https://github.com/n8n-io/n8n)
* 🔧 **Redis Helm Chart Updated**: From version 23.2.12 to 24.0.0
  <br />
  <!-- -->
  ➤ [Bitnami Redis on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🗃️ **PostgreSQL Helm Chart Updated**: From version 18.1.10 to 18.1.13
  <br />
  <!-- -->
  ➤ [Bitnami PostgreSQL on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.5).

<!-- -->

## Get Started with n8n 1.16.5[​](#get-started-with-n8n-1165 "Direct link to Get Started with n8n 1.16.5")

Want to upgrade or deploy n8n using the latest Helm chart? Our [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through:

* Installing quickly with default values
* Customizing the configuration for your environment
* Applying production-ready best practices

Explore all deployment options in the [n8n documentation](https://community-charts.github.io/docs/category/n8n) and launch your next automation workflow with ease.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), the n8n Helm chart makes Kubernetes deployments easier and more reliable. Benefits include:

* 🚀 **Simplicity**: Easy to install and configure even for beginners
* 🤝 **Community-Driven**: Backed by active contributors and frequent updates
* 🛠️ **Flexibility**: Tailor it to your specific workflows and environments
* 🧪 **Reliability**: Continuously tested in diverse Kubernetes setups

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We welcome everyone to take part in improving the n8n Helm chart! Whether you're a developer, DevOps engineer, or Kubernetes enthusiast, here's how you can contribute:

* 📘 Browse our [documentation](https://community-charts.github.io/docs/category/n8n) to learn more
* 📥 Submit improvements via pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐛 Report bugs or issues using our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Suggest new features to enhance the chart

Thank you for being part of the n8n and Kubernetes community. Let’s keep building great things—together.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-26-n8n-chart-version-1-16-5-released.md)


---

# n8n chart version 1.16.6 released

November 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart—**version 1.16.6**—is now available, including the updated **app version 1.121.3**. This release brings valuable enhancements and updates designed to make deploying n8n on Kubernetes even easier.

## What’s New in Helm Chart 1.16.6[​](#whats-new-in-helm-chart-1166 "Direct link to What’s New in Helm Chart 1.16.6")

This release includes the following update to align with the latest n8n application release:

* 🔄 **Updated**: n8nio/n8n Docker image to version 1.121.3
  <br />
  <!-- -->
  ➤ [View Upstream Project](https://github.com/n8n-io/n8n)

Check out the complete changelog and additional details in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.6).

<!-- -->

## Get Started with the n8n Chart[​](#get-started-with-the-n8n-chart "Direct link to Get Started with the n8n Chart")

Deploying n8n with Helm has never been easier. Our detailed [installation guides](https://community-charts.github.io/docs/category/n8n) will help you:

* Perform a quick installation using default configurations.
* Customize deployment settings for your specific use case.
* Follow proven practices for production environments.

Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to get up and running in just a few steps.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The n8n Helm chart, maintained by the open-source [GitHub Community Charts project](https://github.com/community-charts/helm-charts), is tailored for seamless Kubernetes deployments. It offers several advantages:

* ⚙️ **Easy to Use**: Deploy and configure n8n efficiently.
* 🌍 **Community-Driven**: Built by contributors from around the globe.
* 🔧 **Highly Configurable**: Flexible options for diverse environments.
* 🔒 **Reliable**: Designed for stable operation in Kubernetes clusters.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We welcome all contributors to help us improve the n8n chart. Whether you're just getting started or you're a seasoned DevOps professional, there are many ways to get involved:

* 🔍 Learn how to configure the chart in our [documentation](https://community-charts.github.io/docs/category/n8n).
* 🤝 Contribute code or improvements on our [GitHub repo](https://github.com/community-charts/helm-charts).
* 🐞 Found a bug? [Report an issue](https://github.com/community-charts/helm-charts/issues).
* 💡 Have an idea? [Request a feature](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and the GitHub Community Charts initiative. We're proud to build with the community—one Helm chart at a time.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-27-n8n-chart-version-1-16-6-released.md)


---

# n8n chart version 1.16.7 released

December 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart—**v1.16.7**—is now available! This release, published on 2025-12-02, includes **application version 1.122.4** and brings several improvements and updates for deploying n8n seamlessly on Kubernetes.

## Highlights of n8n 1.16.7[​](#highlights-of-n8n-1167 "Direct link to Highlights of n8n 1.16.7")

The 1.16.7 chart update focuses on keeping your n8n deployments up to date and reliable. Here’s what’s included:

* 🔄 **Image Updated**: Upgraded `n8nio/n8n` to version **1.122.4** to deliver the latest features and fixes.
  <!-- -->
  * Check out the [upstream project](https://github.com/n8n-io/n8n) for more insights.

Explore the full [changelog on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.7) to see all technical details and contributions.

<!-- -->

## Start Using n8n 1.16.7 Today[​](#start-using-n8n-1167-today "Direct link to Start Using n8n 1.16.7 Today")

Getting started with the updated chart is easy. We’ve prepared detailed [installation guides](https://community-charts.github.io/docs/category/n8n) to help you every step of the way:

* Quick setup using default values.
* Advanced configuration options tailored to various environments.
* Best practices for running n8n in production.

Visit our [n8n documentation](https://community-charts.github.io/docs/category/n8n) for a complete overview and integration tips.

## Why Choose the Community n8n Helm Chart?[​](#why-choose-the-community-n8n-helm-chart "Direct link to Why Choose the Community n8n Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, this chart is built to make your Kubernetes experience simpler and more robust. Here’s why developers choose it:

* 🚀 **Simple Deployment**: Start fast with an opinionated but customizable setup.
* 🤝 **Open-Source Collaboration**: Join a vibrant community that actively improves the chart.
* ⚙️ **Flexible Configuration**: Adaptable to a wide range of workflows and infrastructure setups.
* 🔒 **Battle-Tested**: Validated across production environments by contributors.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We believe in open-source collaboration, and we’d love for you to be a part of it! Here’s how you can get involved:

* Dive into the [n8n chart documentation](https://community-charts.github.io/docs/category/n8n) to learn how it works.
* Contribute your improvements via [pull requests](https://github.com/community-charts/helm-charts).
* Share your feedback or report bugs in our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* Have an idea for a feature? [Open a feature request](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and the GitHub Community Charts initiative. Together, we’re making Kubernetes deployments better for everyone.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-02-n8n-chart-version-1-16-7-released.md)


---

# n8n chart version 1.16.8 released

December 5, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.16.8**, is now available as of December 5, 2025. This release packages **app version 1.122.5** and includes key updates to streamline your workflow automation deployments on Kubernetes.

## What’s New in Version 1.16.8[​](#whats-new-in-version-1168 "Direct link to What’s New in Version 1.16.8")

This update brings improvements to the Helm chart along with the bump to the latest n8n app release. Here's what’s changed:

* 🛠️ **Updated**: n8nio/n8n Docker image upgraded to version 1.122.5
  <br />
  <!-- -->
  → [Upstream Repository](https://github.com/n8n-io/n8n)

Check out the full changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.8) on GitHub.

<!-- -->

## Get Started with n8n Helm Chart[​](#get-started-with-n8n-helm-chart "Direct link to Get Started with n8n Helm Chart")

Deploying n8n 1.16.8 on Kubernetes is easier than ever. Head over to our [documentation portal](https://community-charts.github.io/docs/category/n8n) to explore:

* Quick start guides for rapid deployment
* Flexible configuration options tailored to your setup
* Expert tips for secure and scalable production deployments

Whether you're self-hosting n8n for the first time or upgrading an existing install, our docs have everything you need.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

The official Helm chart from the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project makes it simple to run n8n in your Kubernetes environment. Here’s what makes it stand out:

* ✅ **Streamlined Setup**: Install with minimal effort using Helm
* 🚀 **Community Powered**: Built and improved with the help of open-source contributors
* 🔧 **Highly Configurable**: Tune settings to match your workflows
* 🧪 **Proven Stability**: Trusted in both development and production clusters

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We'd love for you to get involved! This chart is maintained by an open-source community, and your input helps drive it forward. Here’s how you can participate:

* 💡 Learn more in our [n8n chart documentation](https://community-charts.github.io/docs/category/n8n)
* 🤝 Contribute via [pull requests on GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs on our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 🌟 Request features or share feedback with the community

Thank you for being part of the journey. Let’s keep building a better automation experience—together.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-05-n8n-chart-version-1-16-8-released.md)


---

# n8n chart version 1.16.9 released

December 9, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.16.9**, is now available, bundled with the powerful **app version 1.123.4**. Released on December 9, 2025, this update brings improved functionality and streamlined Kubernetes deployment, all thanks to valuable input from our open-source community.

## What’s New in Chart Version 1.16.9[​](#whats-new-in-chart-version-1169 "Direct link to What’s New in Chart Version 1.16.9")

This release includes updates to both the Helm chart and the bundled n8n application. Highlights include:

* 🔄 **Image Update**: Upgraded image to `n8nio/n8n:1.123.4`
  <br />
  <!-- -->
  ↳ See the latest in the [n8n upstream repository](https://github.com/n8n-io/n8n)

For a complete breakdown of the changes, check the official [chart release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.9) on GitHub.

<!-- -->

## Get Started with n8n on Kubernetes[​](#get-started-with-n8n-on-kubernetes "Direct link to Get Started with n8n on Kubernetes")

Ready to deploy n8n using Helm? Our updated [installation docs](https://community-charts.github.io/docs/category/n8n) guide you through:

* Fast setup with default configs
* Fine-tuned custom deployments
* Best practices for stable production rollouts

Whether you're running a small automation setup or powering enterprise workflows, the docs can help you get started in no time.

## Why Use the n8n Helm Chart?[​](#why-use-the-n8n-helm-chart "Direct link to Why Use the n8n Helm Chart?")

Designed for developers, DevOps teams, and automation enthusiasts, the n8n Helm chart provides seamless deployment on Kubernetes environments. Benefits include:

* ✅ **Simple Setup**: Fast, consistent deployments using Helm
* 🌍 **Community-Powered**: Open-source contributions drive continuous improvement
* 🛠️ **Highly Configurable**: Tailor to meet your exact requirements
* 🔐 **Production-Ready**: Built for reliability and scalability

This chart is proudly maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team and contributors like you.

## Contribute to the Community[​](#contribute-to-the-community "Direct link to Contribute to the Community")

We love seeing the community grow! There are many ways to get involved and shape the future of the n8n chart:

* 📚 Review the [docs](https://community-charts.github.io/docs/category/n8n) to understand chart capabilities
* 🛠️ Submit your improvements via [pull requests](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or ask for help in the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Request new features or share automation ideas that benefit others

Thank you for being part of the n8n and Helm community. We can’t wait to see what you build next!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-12-09-n8n-chart-version-1-16-9-released.md)


---

# n8n chart version 1.17.0 released

June 5, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **n8n Helm chart version 1.17.0** on June 5, 2026, featuring **app version 2.23.3**. This update introduces new features, enhancements, and community-driven improvements, making it even easier to deploy n8n on Kubernetes.

## What's New in n8n 1.17.0 chart[​](#whats-new-in-n8n-1170-chart "Direct link to What's New in n8n 1.17.0 chart")

This release includes updates to both the Helm chart (version 1.17.0) and the underlying application (version 2.23.3). Here are the highlights from the changelog:

* **Added**: Introduced a new top-level `revisionHistoryLimit` value that controls the number of old ReplicaSets/revisions retained for rollback.

For a comprehensive list of changes, check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.17.0) on GitHub.

<!-- -->

## Getting Started with n8n 1.17.0 chart[​](#getting-started-with-n8n-1170-chart "Direct link to Getting Started with n8n 1.17.0 chart")

Are you ready to deploy n8n 1.17.0? Our [installation guides](https://community-charts.github.io/docs/category/n8n) offer detailed, step-by-step instructions to help you get started, including:

* Quick installation with default configurations.
* Customizing settings to fit your specific environment.
* Best practices for seamless production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today!

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to simplify the deployment of n8n on Kubernetes with reliability and ease. Here are some key benefits:

* **Ease of Use**: Experience a streamlined installation and configuration process.
* **Community-Driven**: Enjoy regular updates and enhancements from our dedicated contributors.
* **Flexibility**: Access a range of configurable options to suit various use cases.
* **Reliability**: Count on stability, with thorough testing in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we invite your contributions! Whether you’re fixing bugs, enhancing documentation, or suggesting new features, here’s how you can get involved:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration information.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Have you spotted a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your ideas for improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Together, let’s continue to make Kubernetes deployments even easier!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-05-n8n-chart-version-1-17-0-released.md)


---

# n8n chart version 1.17.1 released

June 6, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the news about the release of the **n8n Helm chart version 1.17.1** on June 6, 2026, featuring **app version 2.23.4**. This update introduces a range of new features, enhancements, and community-driven improvements that streamline the deployment of n8n on Kubernetes.

## What's New in n8n 1.17.1 Chart[​](#whats-new-in-n8n-1171-chart "Direct link to What's New in n8n 1.17.1 Chart")

This release includes important updates to the Helm chart (version 1.17.1) and the underlying application (version 2.23.4). Here are the key changes:

* **Changed**: Updated `n8nio/n8n` image version to 2.23.4
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency on Redis from 27.0.0 to 27.0.4
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* **Changed**: Updated dependency on PostgreSQL from 18.7.0 to 18.7.2
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.17.1) on GitHub.

<!-- -->

## Getting Started with n8n 1.17.1 Chart[​](#getting-started-with-n8n-1171-chart "Direct link to Getting Started with n8n 1.17.1 Chart")

Ready to deploy n8n 1.17.1? Our [installation guides](https://community-charts.github.io/docs/category/n8n) offer detailed, step-by-step instructions that will get you onboard quickly, including:

* Quick installation with default configurations.
* Customization options tailored to your environment.
* Best practices for efficient production deployments.

Explore the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to discover all available options and start your n8n journey today!

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to ensure a seamless and dependable deployment of n8n on Kubernetes. Here are the key benefits you'll enjoy:

* **Ease of Use**: Simplified installation and configuration processes.
* **Community-Driven**: Regular improvements and updates courtesy of our dedicated contributors.
* **Flexibility**: Configurable options that cater to various use cases.
* **Reliability**: Endorsed for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we welcome your contributions! Whether you're fixing bugs, enhancing documentation, or proposing new features, here’s how you can participate:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration insights.
* **Contribute**: Submit your pull requests at our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Together, let's continue to simplify Kubernetes deployments!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-06-n8n-chart-version-1-17-1-released.md)


---

# n8n chart version 1.18.0 released

June 7, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.18.0** on June 7, 2026, featuring the updated **app version 2.23.4**. This release introduces new features, enhancements, and various community-driven improvements to make deploying n8n on Kubernetes even easier.

## What's New in the n8n 1.18.0 chart[​](#whats-new-in-the-n8n-1180-chart "Direct link to What's New in the n8n 1.18.0 chart")

This release not only updates the Helm chart to version 1.18.0 but also includes significant changes in the application (version 2.23.4). Here are the highlights from the changelog:

* **Added**: Security context definitions for the wait-for-main init containers and task runner sidecar containers.

* **Security**: Introduced seccompProfile RuntimeDefault to the pod security context (CIS 5.7.2).

* **Security**: Enabled readOnlyRootFilesystem for all containers with tmp, cache, and data emptyDir volumes and for the waitContainerSecurityContext (CIS 5.7.3).

For a complete overview of the changes, check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.18.0) on GitHub.

<!-- -->

## Getting Started with the n8n 1.18.0 chart[​](#getting-started-with-the-n8n-1180-chart "Direct link to Getting Started with the n8n 1.18.0 chart")

Eager to deploy n8n 1.18.0? Our [installation guides](https://community-charts.github.io/docs/category/n8n) offer step-by-step instructions to help you get started, including:

* Quick installation with default configurations.
* Customizing settings to suit your specific environment.
* Best practices for a successful production deployment.

Head over to the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and kick off your n8n deployment today!

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to make deploying n8n on Kubernetes a smooth and reliable experience. Here are some key benefits:

* **Ease of Use**: Simplified installation and configuration processes.
* **Community-Driven**: Regular updates and enhancements from our dedicated contributors.
* **Flexibility**: Configurable options to suit various use cases.
* **Reliability**: Tested for stability across Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

The GitHub Community Charts project thrives on community contributions, and we would love for you to be a part of it! Whether you're interested in fixing bugs, enhancing documentation, or proposing new features, here’s how you can contribute:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration insights.
* **Contribute**: Feel free to submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: We welcome improvement suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your continued support of n8n and GitHub Community Charts. Together, let’s make Kubernetes deployments even more accessible and efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-07-n8n-chart-version-1-18-0-released.md)


---

# n8n chart version 1.19.0 released

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.19.0** on 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and valuable community-driven improvements to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.19.0 chart[​](#whats-new-in-n8n-1190-chart "Direct link to What's New in n8n 1.19.0 chart")

With this release, we have made notable updates to the Helm chart (version 1.19.0) and the application itself (version 2.23.4). Here’s a highlight of what’s included:

* **Added**: Configurable secret key names for external PostgreSQL and Redis existing secrets.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.19.0) on GitHub.

<!-- -->

## Getting Started with n8n 1.19.0 chart[​](#getting-started-with-n8n-1190-chart "Direct link to Getting Started with n8n 1.19.0 chart")

Are you ready to deploy n8n 1.19.0? Our [installation guides](https://community-charts.github.io/docs/category/n8n) are here to provide you with clear, step-by-step instructions, including:

* Quick installation with default configurations.
* Customizing settings tailored to your environment.
* Best practices for effective production deployments.

Explore our [n8n documentation](https://community-charts.github.io/docs/category/n8n) to discover all available options and launch n8n seamlessly.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to facilitate straightforward and reliable deployments of n8n on Kubernetes. Key advantages include:

* **Ease of Use**: Enjoy a simplified installation and configuration process.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our dedicated community.
* **Flexibility**: Access configurable options tailored to diverse use cases.
* **Reliability**: Trust in our chart, tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

Join the vibrant GitHub Community Charts! We warmly welcome your contributions. Whether it’s fixing bugs, enhancing documentation, or suggesting new features, here’s how you can jump in:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration insights.
* **Contribute**: Share your expertise by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encounter a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Have an idea for improvement? Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of n8n and GitHub Community Charts. Together, let’s make Kubernetes deployments easier and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-07-n8n-chart-version-1-19-0-released.md)


---

# n8n chart version 1.20.0 released

June 7, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.20.0** on June 7, 2026, featuring **app version 2.23.4**. This latest update introduces a variety of new features, enhancements, and community-driven improvements designed to streamline your experience with deploying n8n on Kubernetes.

## What's New in the n8n 1.20.0 Chart[​](#whats-new-in-the-n8n-1200-chart "Direct link to What's New in the n8n 1.20.0 Chart")

This release encompasses updates to both the Helm chart (version 1.20.0) and the underlying application (version 2.23.4). Here’s a quick look at the key changes:

* **Changed**: Deprecated the `license.autoNenew` fields in favor of `license.autoRenew`, while maintaining backward compatibility.
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/294)

For a detailed list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.20.0) on GitHub.

<!-- -->

## Getting Started with the n8n 1.20.0 Chart[​](#getting-started-with-the-n8n-1200-chart "Direct link to Getting Started with the n8n 1.20.0 Chart")

Eager to deploy n8n 1.20.0? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide you with step-by-step instructions to kickstart your setup, including:

* Quick installation with default configurations.
* Customizing settings to fit your environment.
* Best practices to ensure smooth production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all your deployment options and get n8n up and running today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is tailored for an easy and reliable deployment on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy a simplified installation and configuration process.
* **Community-Driven**: Benefit from frequent updates and enhancements contributed by our vibrant community.
* **Flexibility**: Access a variety of configurable options to cater to diverse use cases.
* **Reliability**: Count on a solution tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

As a community-driven initiative, GitHub Community Charts thrives on your contributions! Whether you’re fixing bugs, enhancing documentation, or proposing new features, here’s how you can make an impact:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration insights.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encounter a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being a part of the n8n and GitHub Community Charts journey. Together, let’s continue to ease the process of Kubernetes deployments!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-07-n8n-chart-version-1-20-0-released.md)


---

# n8n chart version 1.21.0 released

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce that **n8n Helm chart version 1.21.0** has been released as of 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and community-driven improvements designed to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.21.0 chart[​](#whats-new-in-n8n-1210-chart "Direct link to What's New in n8n 1.21.0 chart")

This release brings important updates to both the Helm chart (version 1.21.0) and the underlying application (version 2.23.4). Here are some highlights from the changelog:

* **Added**: Support for extra manifests through `extraManifests` and `extraTemplateManifests` values.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.21.0) on GitHub.

<!-- -->

## Getting Started with n8n 1.21.0 chart[​](#getting-started-with-n8n-1210-chart "Direct link to Getting Started with n8n 1.21.0 chart")

Are you ready to deploy n8n 1.21.0? Our user-friendly [installation guides](https://community-charts.github.io/docs/category/n8n) provide clear, step-by-step instructions to help you get started, including:

* Quick installation with default configurations.
* Customization options tailored to your specific environment.
* Best practices for successful production deployments.

Explore the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to discover all available options and kick off your n8n deployment today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, curated by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to ensure that deploying n8n on Kubernetes is both straightforward and reliable. Here are some compelling reasons to choose it:

* **Ease of Use**: Effortless installation and configuration make for a smooth experience.
* **Community-Driven**: Benefit from frequent updates and enhancements contributed by our passionate community.
* **Flexibility**: A variety of configurable options cater to diverse use cases.
* **Reliability**: Thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a vibrant, community-driven project, and we warmly invite your contributions! Whether you're interested in fixing bugs, enhancing documentation, or suggesting new features, here’s how you can participate:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration information.
* **Contribute**: Share your improvements by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: We’d love to hear your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Together, let's continue to simplify Kubernetes deployments!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-07-n8n-chart-version-1-21-0-released.md)


---

# n8n chart version 1.22.0 released

June 7, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.22.0** as of June 7, 2026, featuring **app version 2.23.4**. This update introduces a variety of new features, enhancements, and community-driven improvements designed to streamline your experience deploying n8n on Kubernetes.

## What's New in n8n 1.22.0 chart[​](#whats-new-in-n8n-1220-chart "Direct link to What's New in n8n 1.22.0 chart")

This release encompasses updates to the Helm chart (version 1.22.0) and its core application (version 2.23.4). Here’s a snapshot of the key changes made:

* **Fixed**: Removed deprecated N8N\_RUNNERS\_ENABLED environment variable (safe since n8n 1.69+)

  <!-- -->

  * [Issue #412](https://github.com/community-charts/helm-charts/issues/412)
  * [Issue #436](https://github.com/community-charts/helm-charts/issues/436)
  * [Issue #474](https://github.com/community-charts/helm-charts/issues/474)

* **Fixed**: Updated to use n8nio/runners image for the external task runner sidecar instead of n8nio/n8n

  <!-- -->

  * [Issue #329](https://github.com/community-charts/helm-charts/issues/329)
  * [Issue #434](https://github.com/community-charts/helm-charts/issues/434)

* **Fixed**: Adjusted to skip the external task runner sidecar on the main pod when worker.mode is set to queue
  <!-- -->
  * [Issue #414](https://github.com/community-charts/helm-charts/issues/414)

* **Fixed**: Renamed runner sidecar port from http to runner-health to eliminate duplicate port name warnings

* **Fixed**: Moved N8N\_RUNNERS\_STDLIB\_ALLOW and N8N\_RUNNERS\_EXTERNAL\_ALLOW to the task-broker configmap, ensuring n8n enforces the correct Python security policy

* **Added**: Enabled Python runner support via nodes.python.enabled flag (requires n8n 1.111.0+ and taskRunners.mode=external)

* **Added**: Introduced nodes.python.external.packages to install Python packages via uv before the runner starts; N8N\_RUNNERS\_EXTERNAL\_ALLOW is derived automatically from the package list

* **Added**: Included optional PVC persistence for Python installed packages via nodes.python.persistence; ReadWriteMany is required for HPA or multi-node deployments

* **Added**: Integrated pypiRegistry support for installing Python packages from a private PyPI index (URL-only via UV\_DEFAULT\_INDEX or uv.toml config file via UV\_CONFIG\_FILE; mirrors npmRegistry pattern)

For further details, check out the complete [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.0) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.0 chart[​](#getting-started-with-n8n-1220-chart "Direct link to Getting Started with n8n 1.22.0 chart")

Eager to deploy n8n 1.22.0? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) provide step-by-step instructions, including:

* Quick installation with default settings.
* Customization options tailored to your environment.
* Best practices for ensuring successful production deployments.

Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to discover all available options and get n8n up and running today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, managed by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to simplify deploying n8n on Kubernetes reliably and efficiently. Here are the key advantages:

* **Ease of Use**: Streamlined installation and configuration process.
* **Community-Driven**: Regular updates and enhancements contributed by the community.
* **Flexibility**: Configurable options designed to cater to a variety of use cases.
* **Reliability**: Thoroughly tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community contributions, and we wholeheartedly welcome your involvement! Whether you’re fixing bugs, enhancing documentation, or proposing new features, here’s how you can contribute:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration insights.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encounter a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your ideas for improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of n8n and GitHub Community Charts. Together, let’s continue to make Kubernetes deployments easier and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-07-n8n-chart-version-1-22-0-released.md)


---

# n8n chart version 1.22.1 released

June 10, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **n8n Helm chart version 1.22.1** on June 10, 2026, featuring **app version 2.25.6**! This update introduces a variety of new features, enhancements, and community-driven improvements designed to streamline your n8n deployment on Kubernetes.

## What's New in n8n 1.22.1 chart[​](#whats-new-in-n8n-1221-chart "Direct link to What's New in n8n 1.22.1 chart")

With this release, you will find significant updates to both the Helm chart (version 1.22.1) and the underlying application (version 2.25.6). Here’s a detailed look at the changes:

* **Changed**: Updated the n8nio/n8n image version to 2.25.6
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency postgresql from 18.7.2 to 18.7.3
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a complete list of changes, be sure to check the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.1) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.1 chart[​](#getting-started-with-n8n-1221-chart "Direct link to Getting Started with n8n 1.22.1 chart")

Ready to deploy n8n 1.22.1? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide easy-to-follow instructions that will help you get started smoothly, including:

* Quick installation with default configurations.
* Customizing settings to fit your specific environment.
* Best practices for successful production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today!

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is tailored to make deploying n8n on Kubernetes both straightforward and dependable. Here are some key benefits:

* **Ease of Use**: Enjoy simplified installation and configuration.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our enthusiastic community.
* **Flexibility**: Take advantage of configurable options that accommodate diverse use cases.
* **Reliability**: Trust in a solution that has been thoroughly tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we would love for you to contribute! Whether you're interested in fixing bugs, enhancing documentation, or suggesting new features, here's how you can join us:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement ideas via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your continued support of n8n and GitHub Community Charts. Together, let's make Kubernetes deployments even easier and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-10-n8n-chart-version-1-22-1-released.md)


---

# n8n chart version 1.22.2 released

June 11, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the release of the **n8n Helm chart version 1.22.2** on June 11, 2026, which includes **app version 2.25.7**. This latest update introduces new features, enhancements, and community-driven improvements to make deploying n8n on Kubernetes even more seamless.

## What's New in n8n 1.22.2 chart[​](#whats-new-in-n8n-1222-chart "Direct link to What's New in n8n 1.22.2 chart")

This release encompasses updates to both the Helm chart (version 1.22.2) and the underlying application (version 2.25.7). Here’s a brief overview of the changes:

* **Changed**: Updated the n8nio/n8n image to version 2.25.7
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)

For a comprehensive list of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.2) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.2 chart[​](#getting-started-with-n8n-1222-chart "Direct link to Getting Started with n8n 1.22.2 chart")

Are you ready to deploy n8n 1.22.2? Our detailed [installation guides](https://community-charts.github.io/docs/category/n8n) will provide you with step-by-step instructions to get you started, including:

* Quick installation using default configurations.
* Customizing settings to fit your environment perfectly.
* Best practices for robust production deployments.

Explore the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to discover all your deployment options today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to simplify the deployment of n8n on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy a streamlined installation and configuration process.
* **Community-Driven**: Benefit from regular updates and improvements contributed by our vibrant community.
* **Flexibility**: Take advantage of configurable options to suit your diverse use cases.
* **Reliability**: Count on stability and performance tested across Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we invite you to contribute! Whether you're fixing bugs, enhancing documentation, or suggesting new features, here’s how you can join us:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration information.
* **Contribute**: Share your changes by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any issues, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts! Together, let’s continue to enhance the Kubernetes deployment experience!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-11-n8n-chart-version-1-22-2-released.md)


---

# n8n chart version 1.22.3 released

June 17, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share that the **n8n Helm chart version 1.22.3** has just been released on June 17, 2026, complete with **app version 2.26.4**! This latest update brings a host of new features, enhancements, and community-driven improvements designed to simplify your experience deploying n8n on Kubernetes.

## What's New in n8n 1.22.3 chart[​](#whats-new-in-n8n-1223-chart "Direct link to What's New in n8n 1.22.3 chart")

With this release, we have updated both the Helm chart (version 1.22.3) and the underlying application (version 2.26.4). Here’s a summary of the key updates:

* **Changed**: The n8nio/n8n image version has been updated to 2.26.4
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: The redis dependency has been upgraded from version 27.0.4 to 27.0.10
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* **Changed**: The postgresql dependency has been upgraded from version 18.7.3 to 18.7.5
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a detailed list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.3) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.3 chart[​](#getting-started-with-n8n-1223-chart "Direct link to Getting Started with n8n 1.22.3 chart")

Eager to deploy n8n 1.22.3? Our [installation guides](https://community-charts.github.io/docs/category/n8n) offer step-by-step instructions to assist you, including:

* Quick installation with default configurations.
* Customization tips to tailor the setup to your environment.
* Best practices for seamless production deployments.

Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to discover all available options and get n8n up and running today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, proudly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to make deploying n8n on Kubernetes a breeze. Here are some of the benefits:

* **Ease of Use**: Straightforward installation and configuration process.
* **Community-Driven**: Continuous updates and enhancements from passionate contributors.
* **Flexibility**: Configurable options to fit a variety of use cases.
* **Reliability**: Tested for robust performance in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

At GitHub Community Charts, we appreciate each contribution from our community! Whether you're fixing bugs, enhancing documentation, or brainstorming new features, here’s how you can join us:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration insights.
* **Contribute**: Share your changes through pull requests in our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your ideas for improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being a part of the n8n and GitHub Community Charts journey. Together, we can make Kubernetes deployments easier and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-17-n8n-chart-version-1-22-3-released.md)


---

# n8n chart version 1.22.4 released

June 18, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.22.4** on June 18, 2026, featuring **app version 2.26.6**. This significant update introduces fresh features, enhancements, and community-driven improvements, all aimed at making the deployment of n8n on Kubernetes smoother and more efficient.

## What's New in n8n 1.22.4 chart[​](#whats-new-in-n8n-1224-chart "Direct link to What's New in n8n 1.22.4 chart")

This release marks an update to both the Helm chart (version 1.22.4) and the underlying application (version 2.26.6). Here are the key highlights:

* **Changed**: Updated the n8nio/n8n image version to 2.26.6
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)

To explore the complete list of changes, please visit the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.4) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.4 chart[​](#getting-started-with-n8n-1224-chart "Direct link to Getting Started with n8n 1.22.4 chart")

Eager to deploy n8n 1.22.4? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) offer easy-to-follow steps to help you get started, including:

* Quick installation with default configurations.
* Customizing settings to fit your environment perfectly.
* Best practices for robust production deployments.

Check out the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for a deep dive into available options and launch n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, proudly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to facilitate straightforward and reliable deployments of n8n on Kubernetes. Here are some key benefits:

* **Ease of Use**: Enjoy simplified installation and configuration.
* **Community-Driven**: Benefit from regular updates and enhancements from our contributors.
* **Flexibility**: Access configurable options that cater to diverse use cases.
* **Reliability**: Our chart is rigorously tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on contributions from our vibrant community, and we warmly welcome your input! Whether you're correcting bugs, enhancing documentation, or suggesting exciting new features, here’s how you can join us:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration insights.
* **Contribute**: Feel free to submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions for improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Together, let’s continue to simplify Kubernetes deployments!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-18-n8n-chart-version-1-22-4-released.md)


---

# n8n chart version 1.22.5 released

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **n8n Helm chart version 1.22.5** on 2026-06-19, featuring **app version 2.26.6**. This update introduces new features and valuable community-driven enhancements, all focused on simplifying your n8n deployment on Kubernetes.

## What's New in n8n 1.22.5 chart[​](#whats-new-in-n8n-1225-chart "Direct link to What's New in n8n 1.22.5 chart")

In this release, we've worked hard on updates to both the Helm chart (version 1.22.5) and the underlying application (version 2.26.6). Here’s a look at the significant changes:

* **Fixed**: Set the NPM\_CONFIG\_CACHE environment variable in the main container to enable community package installations while keeping readOnlyRootFilesystem enabled.

  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/508)
  * [GitHub Issue](https://github.com/community-charts/community-charts.github.io/issues/102)

* **Fixed**: Resolved issues with community node packages not being accessible in external task runner mode and added --ignore-scripts to prevent postinstall script errors.

* **Added**: Introduced optional PVC persistence for community node packages via nodes.external.persistence.

* **Fixed**: Ensured that community package installs route into the main/worker PVC when its mountPath already includes /home/node/.n8n/nodes, eliminating unnecessary separate volumes.

* **Fixed**: Addressed the creation of the worker PVC not occurring when worker.count > 1 with ReadWriteMany access mode.

* **Fixed**: Fixed the sharing of community packages across StatefulSet replicas using a ReadWriteOnce PVC when forceToUseStatefulset is true.

For a complete overview of all changes, check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.5) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.5 chart[​](#getting-started-with-n8n-1225-chart "Direct link to Getting Started with n8n 1.22.5 chart")

Are you ready to deploy n8n 1.22.5? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) walk you through the steps to get started, including:

* Quick installation using default configurations.
* Customizing settings tailored to your environment.
* Best practices for successful production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to make deploying n8n on Kubernetes both seamless and reliable. Here are some key benefits:

* **Ease of Use**: Streamlined installation and configuration process.
* **Community-Driven**: Continuous updates and improvements fueled by our contributors.
* **Flexibility**: Configurable options catering to a wide range of use cases.
* **Reliability**: Tested for consistent performance in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community involvement, and we’re eager for your contributions! Whether it’s fixing bugs, enhancing documentation, or proposing new features, here’s how you can jump in:

* **Explore the Chart**: Delve into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for detailed configuration insights.
* **Contribute**: We welcome your pull requests on our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you’ve encountered a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of n8n and GitHub Community Charts. Together, let's continue to simplify Kubernetes deployments!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-19-n8n-chart-version-1-22-5-released.md)


---

# n8n chart version 1.22.6 released

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the arrival of **n8n Helm chart version 1.22.6** on 2026-06-19, which includes the latest **app version 2.26.7**. This update features a variety of enhancements and community-driven improvements aimed at simplifying the deployment of n8n on Kubernetes.

## What's New in n8n 1.22.6 Chart[​](#whats-new-in-n8n-1226-chart "Direct link to What's New in n8n 1.22.6 Chart")

This release encompasses updates for both the Helm chart (version 1.22.6) and the underlying application (version 2.26.7). Here’s a glimpse into the changes made:

* **Changed**: Updated the n8nio/n8n image version to 2.26.7
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency postgresql from 18.7.5 to 18.7.6
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of the changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.6) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.6 Chart[​](#getting-started-with-n8n-1226-chart "Direct link to Getting Started with n8n 1.22.6 Chart")

Are you ready to deploy n8n 1.22.6? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide detailed, step-by-step instructions to help you get started, featuring:

* Quick installation with default configurations.
* Customization options tailored to fit your environment.
* Best practices for deploying in production.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available deployment options and get n8n up and running today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to ensure that deploying n8n on Kubernetes is not only easy but also reliable. Here are some of the key advantages:

* **Ease of Use**: Simplified installation and straightforward configuration.
* **Community-Driven**: Ongoing updates and enhancements driven by community contributors.
* **Flexibility**: Configurable options that adapt to diverse use cases.
* **Reliability**: Proven stability tested within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we warmly welcome your contributions! Whether you're interested in fixing bugs, improving documentation, or suggesting new features, here’s how you can participate:

* **Explore the Chart**: Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for comprehensive configuration details.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your suggestions through our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and the GitHub Community Charts. Together, let's continue making Kubernetes deployments simpler and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-19-n8n-chart-version-1-22-6-released.md)


---

# n8n chart version 1.22.7 released

June 19, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.22.7** as of June 19, 2026, which includes **app version 2.26.7**. This update introduces new features, enhancements, and valuable improvements driven by our community, making it even easier to deploy n8n on Kubernetes.

## What's New in n8n 1.22.7 chart[​](#whats-new-in-n8n-1227-chart "Direct link to What's New in n8n 1.22.7 chart")

This release features updates to the Helm chart (version 1.22.7) and the underlying application (version 2.26.7). Here’s a glimpse of the changes:

* **Fixed**: Enhanced community node detection to support scoped community nodes (e.g., @myorg/n8n-nodes-mynode)
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/241)

For a comprehensive list of changes, please view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.7) on GitHub.

<!-- -->

## Getting Started with n8n 1.22.7 chart[​](#getting-started-with-n8n-1227-chart "Direct link to Getting Started with n8n 1.22.7 chart")

Are you ready to deploy n8n 1.22.7? Our [installation guides](https://community-charts.github.io/docs/category/n8n) offer step-by-step instructions, including:

* Quick installation with default settings.
* Customizing configurations to fit your needs.
* Best practices for deploying in production.

Explore the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for all available options and kick-start your n8n deployment today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to simplify deploying n8n on Kubernetes. Here are some key benefits:

* **Ease of Use**: Streamlined installation and setup.
* **Community-Driven**: Regular updates and enhancements from dedicated contributors.
* **Flexibility**: Configurable options to accommodate various use cases.
* **Reliability**: Tested rigorously for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community collaboration, and we would love for you to join us! Whether you're fixing bugs, enhancing documentation, or proposing new features, here’s how you can contribute:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration insights.
* **Contribute**: Share your improvements by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you've spotted a bug, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: We welcome your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Together, we can make Kubernetes deployments simpler and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-19-n8n-chart-version-1-22-7-released.md)


---

# n8n chart version 1.23.0 released

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **n8n Helm chart version 1.23.0** as of June 19, 2026, showcasing **app version 2.26.7**. This update includes a host of new features, enhancements, and community-driven improvements designed to streamline your experience deploying n8n on Kubernetes.

## What's New in the n8n 1.23.0 Chart[​](#whats-new-in-the-n8n-1230-chart "Direct link to What's New in the n8n 1.23.0 Chart")

This release not only updates the Helm chart (version 1.23.0) but also enhances the underlying application (version 2.26.7). Here’s a quick look at what’s new:

* **Added**: Introduced the extraEnv field in main, worker, webhook, and webhook.mcp blocks for environment variables that support valueFrom (e.g., secretKeyRef, configMapKeyRef, fieldRef).

For a more detailed list of changes, be sure to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.23.0) on GitHub.

<!-- -->

## Getting Started with the n8n 1.23.0 Chart[​](#getting-started-with-the-n8n-1230-chart "Direct link to Getting Started with the n8n 1.23.0 Chart")

Are you ready to deploy n8n version 1.23.0? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/n8n) provide all the information you need to get up and running, including:

* Quick installation with default configurations.
* Customization options to fit your environment.
* Best practices for seamless production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and start deploying n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, brought to you by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to make your experience deploying n8n on Kubernetes both simple and efficient. Here are some key benefits:

* **Ease of Use**: Enjoy a streamlined installation and configuration process.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our vibrant community.
* **Flexibility**: Take advantage of customizable options to address your unique use cases.
* **Reliability**: Count on stability and performance, tested in various Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community contributions, and we encourage you to get involved! Whether you’re interested in fixing bugs, enhancing documentation, or proposing new features, here’s how you can contribute:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Share your expertise by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you've encountered a bug, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Have a suggestion? Share your ideas via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of n8n and GitHub Community Charts. Together, we can make Kubernetes deployments even easier!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-19-n8n-chart-version-1-23-0-released.md)


---

# n8n chart version 1.23.1 released

June 19, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.23.1** on June 19, 2026, featuring **app version 2.26.8**. This update introduces new features, enhancements, and valuable community-driven improvements to streamline the deployment of n8n on Kubernetes.

## What's New in the n8n 1.23.1 chart[​](#whats-new-in-the-n8n-1231-chart "Direct link to What's New in the n8n 1.23.1 chart")

The latest release includes updates to both the Helm chart (version 1.23.1) and the underlying application (version 2.26.8). Here’s a summary of what’s new:

* **Changed**: Updated the n8nio/n8n image version to 2.26.8
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Fixed**: Resolved broken screenshot URL(s) in the n8n chart

For a comprehensive list of changes, please view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.23.1) on GitHub.

<!-- -->

## Getting Started with the n8n 1.23.1 chart[​](#getting-started-with-the-n8n-1231-chart "Direct link to Getting Started with the n8n 1.23.1 chart")

Eager to deploy n8n 1.23.1? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide step-by-step instructions to help you get started. You'll find:

* Quick installation with default configurations.
* Customizing settings to suit your specific environment.
* Best practices for production deployments.

Be sure to visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), aims to facilitate a straightforward and reliable deployment of n8n on Kubernetes. Here are some key advantages:

* **Ease of Use**: Simplified installation and configuration process.
* **Community-Driven**: Regular updates and enhancements from our contributors.
* **Flexibility**: A range of configurable options to fit diverse use cases.
* **Reliability**: Thoroughly tested for stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community contributions, and we warmly welcome your involvement! Whether you’re fixing bugs, enhancing documentation, or suggesting new features, here are ways you can get started:

* **Explore the Chart**: Dive into the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Feel free to submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter any bugs, [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Together, let's continue to make Kubernetes deployments easier and more efficient!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-19-n8n-chart-version-1-23-1-released.md)


---

# n8n chart version 1.8.6 released

June 22, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **n8n Helm chart version 1.8.6** on 2025-06-22, featuring **app version 1.98.2**. This update brings new features, enhancements, and community-driven improvements to simplify deploying n8n on Kubernetes.

## What's New in n8n 1.8.6 chart[​](#whats-new-in-n8n-186-chart "Direct link to What's New in n8n 1.8.6 chart")

This release includes updates to the Helm chart (version 1.8.6) and the underlying application (version 1.98.2). Below is the detailed changelog:

* **Fixed**: Fix npm registry secret volume mount when only npmRegistry.enabled is true
  <!-- -->
  * [Github PR](https://github.com/community-charts/helm-charts/pull/135)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.8.6) on GitHub.

<!-- -->

## Getting Started with n8n 1.8.6 chart[​](#getting-started-with-n8n-186-chart "Direct link to Getting Started with n8n 1.8.6 chart")

Ready to deploy n8n 1.8.6? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide step-by-step instructions to get you started, including:

* Quick installation with default configurations.
* Customizing settings to suit your environment.
* Best practices for production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying n8n on Kubernetes straightforward and reliable. Key benefits include:

* **Ease of Use**: Simplified installation and configuration.
* **Community-Driven**: Regular updates and improvements from contributors.
* **Flexibility**: Configurable options to meet diverse use cases.
* **Reliability**: Tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a community-driven project, and we welcome your contributions! Whether you're fixing bugs, improving documentation, or suggesting new features, here's how you can get started:

* **Explore the Chart**: Check out the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Let's continue making Kubernetes deployments easier, together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-22-n8n-chart-version-1-8-6-released.md)


---

# n8n chart version 1.8.7 released

June 23, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **n8n Helm chart version 1.8.7** on 2025-06-23, featuring **app version 1.99.1**. This update brings new features, enhancements, and community-driven improvements to simplify deploying n8n on Kubernetes.

## What's New in n8n 1.8.7 chart[​](#whats-new-in-n8n-187-chart "Direct link to What's New in n8n 1.8.7 chart")

This release includes updates to the Helm chart (version 1.8.7) and the underlying application (version 1.99.1). Below is the detailed changelog:

* **Changed**: Update n8nio/n8n image version to 1.99.1
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.8.7) on GitHub.

<!-- -->

## Getting Started with n8n 1.8.7 chart[​](#getting-started-with-n8n-187-chart "Direct link to Getting Started with n8n 1.8.7 chart")

Ready to deploy n8n 1.8.7? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide step-by-step instructions to get you started, including:

* Quick installation with default configurations.
* Customizing settings to suit your environment.
* Best practices for production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying n8n on Kubernetes straightforward and reliable. Key benefits include:

* **Ease of Use**: Simplified installation and configuration.
* **Community-Driven**: Regular updates and improvements from contributors.
* **Flexibility**: Configurable options to meet diverse use cases.
* **Reliability**: Tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a community-driven project, and we welcome your contributions! Whether you're fixing bugs, improving documentation, or suggesting new features, here's how you can get started:

* **Explore the Chart**: Check out the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Let's continue making Kubernetes deployments easier, together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-23-n8n-chart-version-1-8-7-released.md)


---

# n8n chart version 1.9.0 released

June 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **n8n Helm chart version 1.9.0** on 2025-06-24, featuring **app version 1.99.1**. This update brings new features, enhancements, and community-driven improvements to simplify deploying n8n on Kubernetes.

## What's New in n8n 1.9.0 chart[​](#whats-new-in-n8n-190-chart "Direct link to What's New in n8n 1.9.0 chart")

This release includes updates to the Helm chart (version 1.9.0) and the underlying application (version 1.99.1). Below is the detailed changelog:

* **Added**: Add ingress path for rest/oauth2-credential/callback
  <!-- -->
  * [GitHub Issue](https://github.com/community-charts/helm-charts/issues/141)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.9.0) on GitHub.

<!-- -->

## Getting Started with n8n 1.9.0 chart[​](#getting-started-with-n8n-190-chart "Direct link to Getting Started with n8n 1.9.0 chart")

Ready to deploy n8n 1.9.0? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide step-by-step instructions to get you started, including:

* Quick installation with default configurations.
* Customizing settings to suit your environment.
* Best practices for production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying n8n on Kubernetes straightforward and reliable. Key benefits include:

* **Ease of Use**: Simplified installation and configuration.
* **Community-Driven**: Regular updates and improvements from contributors.
* **Flexibility**: Configurable options to meet diverse use cases.
* **Reliability**: Tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a community-driven project, and we welcome your contributions! Whether you're fixing bugs, improving documentation, or suggesting new features, here's how you can get started:

* **Explore the Chart**: Check out the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Let's continue making Kubernetes deployments easier, together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-24-n8n-chart-version-1-9-0-released.md)


---

# n8n chart version 1.9.1 released

June 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **n8n Helm chart version 1.9.1** on 2025-06-24, featuring **app version 1.99.1**. This update brings new features, enhancements, and community-driven improvements to simplify deploying n8n on Kubernetes.

## What's New in n8n 1.9.1 chart[​](#whats-new-in-n8n-191-chart "Direct link to What's New in n8n 1.9.1 chart")

This release includes updates to the Helm chart (version 1.9.1) and the underlying application (version 1.99.1). Below is the detailed changelog:

* **Added**: Add ingress path for static files
  <!-- -->
  * [GitHub PR](https://github.com/community-charts/helm-charts/pull/143)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.9.1) on GitHub.

<!-- -->

## Getting Started with n8n 1.9.1 chart[​](#getting-started-with-n8n-191-chart "Direct link to Getting Started with n8n 1.9.1 chart")

Ready to deploy n8n 1.9.1? Our [installation guides](https://community-charts.github.io/docs/category/n8n) provide step-by-step instructions to get you started, including:

* Quick installation with default configurations.
* Customizing settings to suit your environment.
* Best practices for production deployments.

Visit the [n8n documentation](https://community-charts.github.io/docs/category/n8n) to explore all available options and deploy n8n today.

## Why Choose the n8n Helm Chart?[​](#why-choose-the-n8n-helm-chart "Direct link to Why Choose the n8n Helm Chart?")

The n8n helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is designed to make deploying n8n on Kubernetes straightforward and reliable. Key benefits include:

* **Ease of Use**: Simplified installation and configuration.
* **Community-Driven**: Regular updates and improvements from contributors.
* **Flexibility**: Configurable options to meet diverse use cases.
* **Reliability**: Tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a community-driven project, and we welcome your contributions! Whether you're fixing bugs, improving documentation, or suggesting new features, here's how you can get started:

* **Explore the Chart**: Check out the [n8n documentation](https://community-charts.github.io/docs/category/n8n) for configuration details.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Suggest improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting n8n and GitHub Community Charts. Let's continue making Kubernetes deployments easier, together!

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-24-n8n-chart-version-1-9-1-released.md)


---

# Outline chart 0.4.0 brings powerful enhancements

July 3, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.4.0**, now available as of July 3, 2025. This release includes major improvements and expanded functionality that make deploying Outline on Kubernetes even more seamless and secure.

<!-- -->

## What’s New in Outline 0.4.0[​](#whats-new-in-outline-040 "Direct link to What’s New in Outline 0.4.0")

Chart version 0.4.0 introduces a range of new features and fixes that reflect active community contributions and ongoing enhancements in the open-source ecosystem:

* ✅ **External Secrets Support Extended**: Securely connect to external services like Redis, PostgreSQL, S3, SMTP, Slack, Dropbox, Google, Azure, OIDC, GitHub, Discord, Gitea, GitLab, Auth0, Keycloak, SAML, Iframely, and OpenAI.
  <!-- -->
  * 📌 [GitHub Issue #156](https://github.com/community-charts/helm-charts/issues/156)
* 🔧 **Bug Fix**: Resolved an issue with the missing Dropbox app key secret.
* 🌐 **DNS and Host Configuration**: Add support for dnsPolicy, dnsConfig, and hostAliases for advanced networking needs.
  <!-- -->
  * 📌 [GitHub Issue #157](https://github.com/community-charts/helm-charts/issues/157)
* ⚙️ **Service Toggle**: Introduced an enabled flag for service control.
* 🔌 **New Integrations**: Added official support for Linear and Notion integrations.
  <!-- -->
  * 📌 [GitHub Issue #161](https://github.com/community-charts/helm-charts/issues/161)

You can review the full release details in the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.4.0).

## Get Started with Outline 0.4.0[​](#get-started-with-outline-040 "Direct link to Get Started with Outline 0.4.0")

Looking to set up Outline on your Kubernetes cluster? Start here:

🛠️ Visit our [Outline documentation](https://community-charts.github.io/docs/category/outline) to find:

* Quick-start installation steps
* Configuration customization tips
* Best practices for production environments

Whether you're running on a local cluster or in a cloud environment (AWS, Azure, etc.), we've got guides to help you succeed.

## Why Use the Outline Helm Chart?[​](#why-use-the-outline-helm-chart "Direct link to Why Use the Outline Helm Chart?")

Managed by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the Outline Helm chart ensures fast, reliable, and easy deployments on Kubernetes.

✨ **Key advantages**:

* Simple and intuitive configuration
* Backed by a growing open-source community
* Flexible, production-ready setups
* Trusted and tested within real-world environments

## Join the Open Source Community[​](#join-the-open-source-community "Direct link to Join the Open Source Community")

Our project thrives on community support! Whether you’re a developer, DevOps engineer, or documentation enthusiast, here’s how you can contribute:

🔍 Learn: Browse the [Outline Helm chart documentation](https://community-charts.github.io/docs/category/outline)<br /><!-- -->👩‍💻 Contribute: Open a pull request on our [GitHub repository](https://github.com/community-charts/helm-charts)<br /><!-- -->🐞 Report: Spot a bug? [Log it here](https://github.com/community-charts/helm-charts/issues)<br /><!-- -->💡 Request: Submit your feature ideas via the [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thank you for being part of the journey to make Kubernetes deployments more accessible. Let’s innovate and grow together—powered by open source!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-03-outline-chart-version-0-4-0-released.md)


---

# outline chart version 0.4.1 released

July 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm Chart version 0.4.1**, available as of July 4, 2025. This update delivers important improvements and refreshed dependencies to make deploying Outline on your Kubernetes clusters smoother and more efficient.

<!-- -->

## What’s New in 0.4.1[​](#whats-new-in-041 "Direct link to What’s New in 0.4.1")

Release 0.4.1 includes updates to both the Helm chart and application stack, continuing our effort to provide a seamless and up-to-date deployment experience. Here’s what’s been updated:

* ✅ **Updated Image**: Bumped to `outlinewiki/outline:0.85.0`<br /><!-- -->→ [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)

* 🔄 **Redis Upgrade**: Now uses Redis chart `21.2.6` (previously `21.0.2`)<br /><!-- -->→ [Available on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 📦 **PostgreSQL Upgrade**: Upgraded PostgreSQL chart to `16.7.15` (from `16.7.2`)<br /><!-- -->→ [Available on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

📝 For the full list of enhancements and changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.4.1).

## Getting Started with Outline 0.4.1[​](#getting-started-with-outline-041 "Direct link to Getting Started with Outline 0.4.1")

Want to get up and running quickly? We’ve made it easy to deploy Outline in your Kubernetes environment with our comprehensive [installation guides](https://community-charts.github.io/docs/category/outline):

* 🚀 Straightforward setup using default values
* ⚙️ Custom configurations tailored to your workload
* 🛡️ Best practices for production-ready deployments

Visit the full [Outline documentation](https://community-charts.github.io/docs/category/outline) to start deploying today.

## Why Use the Outline Helm Chart?[​](#why-use-the-outline-helm-chart "Direct link to Why Use the Outline Helm Chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the Outline Helm chart makes your deployments more efficient, reliable, and customizable. Here’s what makes it stand out:

* 👏 **User-Friendly**: Easy setup and configuration with minimal effort
* 🌍 **Community-Powered**: Regular updates and feedback from real users
* 🔧 **Flexible**: Supports a broad range of Kubernetes environments
* ✅ **Stable**: Robust and tested across CI/CD workflows

Whether you're a developer, platform engineer, or part of a devops team, this chart provides the tools you need to scale knowledge sharing with Outline.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’re building this chart together—and your contributions matter! Jump in and help improve the Outline chart:

* 📖 Learn how to configure via the [Outline docs](https://community-charts.github.io/docs/category/outline)
* 🔧 Submit PRs on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or suggest features via the [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you for supporting Outline and open-source Kubernetes tooling. Together, we’re making deployment easier—one chart at a time!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-04-outline-chart-version-0-4-1-released.md)


---

# Outline chart version 0.4.2 now available

July 15, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the official Helm chart for Outline—**version 0.4.2**, now available as of July 15, 2025. This release includes **app version 0.85.1** and delivers important updates that build on our commitment to reliable, scalable, and easy-to-deploy Kubernetes solutions.

## What's new in Helm chart 0.4.2[​](#whats-new-in-helm-chart-042 "Direct link to What's new in Helm chart 0.4.2")

This version of the Outline Helm chart is packed with notable updates and small but impactful improvements that simplify your deployment experience.

* 🚀 **Upgraded Outline image to v0.85.1**<br /><!-- -->Get the latest features and fixes directly from the upstream project.<br /><!-- -->→ [Upstream Docker image](https://hub.docker.com/r/outlinewiki/outline)

* 🛠️ **Updated Redis dependency**<br /><!-- -->Bumped Redis chart from version 21.2.6 to 21.2.11 for better performance and compatibility.<br /><!-- -->→ [Redis on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* 🗃️ **Updated PostgreSQL dependency**<br /><!-- -->PostgreSQL chart updated from 16.7.15 to 16.7.19 for enhanced security and stability.<br /><!-- -->→ [PostgreSQL on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For full details, please refer to the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.4.2).

<!-- -->

## Getting started with Outline 0.4.2[​](#getting-started-with-outline-042 "Direct link to Getting started with Outline 0.4.2")

Ready to try out the new release? Our updated [installation guides](https://community-charts.github.io/docs/category/outline) walk you through every step:

* Seamlessly install using default values.
* Customize your Helm values to match your environment.
* Follow production-ready best practices for real-world deployments.

👉 Check out the [Outline documentation](https://community-charts.github.io/docs/category/outline) to get started today.

## Why use the Outline Helm chart?[​](#why-use-the-outline-helm-chart "Direct link to Why use the Outline Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, this chart offers a balanced combination of simplicity and power, giving you everything you need to run Outline smoothly on Kubernetes.

✨ Highlighted benefits:

* 🔧 **User-Friendly**: Easily customizable and straightforward to install.
* 🌍 **Open Source & Community-Driven**: Built and improved collaboratively.
* ⚙️ **Production-Ready**: Designed with stability, reliability, and upgradability in mind.
* ☁️ **Cloud-Native**: Built for modern Kubernetes environments.

## Join the community[​](#join-the-community "Direct link to Join the community")

We’re always looking for contributors and collaborators! Whether you’re new to Kubernetes or an experienced DevOps pro, here’s how you can get involved:

* 🧭 Learn more in the [Outline chart docs](https://community-charts.github.io/docs/category/outline).
* 🛠️ Submit improvements or fixes on [GitHub](https://github.com/community-charts/helm-charts).
* 🐞 Report issues using our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Request new features you'd like to see.

Thank you for supporting the Outline Helm chart. Together with our vibrant open-source community, we’re working to make Kubernetes deployments more accessible for everyone.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-15-outline-chart-version-0-4-2-released.md)


---

# Outline chart 0.4.3 released with app version 0.85.1

July 23, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the Outline Helm chart—**version 0.4.3**, paired with **application version 0.85.1**—shipped on July 23, 2025. This update brings key improvements and important fixes, making it even easier to deploy and manage Outline on Kubernetes.

## Highlights in Helm chart v0.4.3[​](#highlights-in-helm-chart-v043 "Direct link to Highlights in Helm chart v0.4.3")

Here’s what’s new in this release of the chart and application:

* 🛠️ **Fixed**: Support for non-default PostgreSQL ports when connecting to external databases.
  <!-- -->
  * Source: [Outline Docker Image](https://hub.docker.com/r/outlinewiki/outline)
* 📚 **Improved**: Documentation now correctly references `fileStorage.s3.bucketUrl` instead of the outdated `fileStorage.s3.baseUrl`.

These changes were driven by feedback and contributions from the open-source community. Explore the full changelog on our [GitHub release page](https://github.com/community-charts/helm-charts/releases/tag/outline-0.4.3).

<!-- -->

## How to get started with Outline 0.4.3[​](#how-to-get-started-with-outline-043 "Direct link to How to get started with Outline 0.4.3")

Getting up and running is easy. Whether you're just testing or going into production, our [installation documentation](https://community-charts.github.io/docs/category/outline) covers everything:

* 🔧 Quickstart guides for fast setups.
* ⚙️ Advanced configuration options.
* 🛡️ Best practices for secure and reliable production deployments.

Visit the [Outline Helm chart docs](https://community-charts.github.io/docs/category/outline) to explore all deployment options.

## Why choose Outline on Kubernetes via Helm?[​](#why-choose-outline-on-kubernetes-via-helm "Direct link to Why choose Outline on Kubernetes via Helm?")

The Outline chart, maintained by the [GitHub Community Charts project](https://github.com/community-charts/helm-charts), is purpose-built to help teams deploy Outline easily and securely in Kubernetes environments:

* 🚀 **Easy Installation**: Helm simplifies the deployment process.
* 🤝 **Community-Powered**: Benefit from regular updates and support.
* 🔄 **Flexible Configuration**: Tailor deployments to your needs.
* ✅ **Reliable Operations**: Built and tested for Kubernetes environments.

## Join the community[​](#join-the-community "Direct link to Join the community")

The GitHub Community Charts project thrives on open-source collaboration. Want to get involved and make contributions?

* 📘 Dive into the [Outline docs](https://community-charts.github.io/docs/category/outline) for config options and examples.
* 🛠 Submit pull requests to improve the [Helm repo on GitHub](https://github.com/community-charts/helm-charts).
* 🐛 Found a bug? [Report issues](https://github.com/community-charts/helm-charts/issues) to help us investigate.
* 💡 Have a feature idea? [Request enhancements](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being part of the journey. Together, we’re making open-source Kubernetes deployments better, faster, and easier!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-23-outline-chart-version-0-4-3-released.md)


---

# Outline chart version 0.5.0 now available

July 25, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **outline Helm chart version 0.5.0**, officially launched on **July 25, 2025**. This update includes **app version 0.85.1** and delivers new capabilities, refinements, and helpful improvements powered by valuable community contributions. As always, our goal is to make deploying Outline on Kubernetes as easy and efficient as possible.

## What’s new in version 0.5.0[​](#whats-new-in-version-050 "Direct link to What’s new in version 0.5.0")

This release enhances both the Helm chart (v0.5.0) and the Outline application (v0.85.1). Here's a quick overview of what’s included:

* 🧹 **Removed**: S3 region pattern removed from the chart for improved compatibility<br /><!-- -->↳ [View GitHub Issue](https://github.com/community-charts/helm-charts/issues/179)

* 🔐 **Added**: Support added for Secret Key and Utils Secret using External Secrets<br /><!-- -->↳ [View GitHub Issue](https://github.com/community-charts/helm-charts/issues/177)

For the full list of changes and technical details, check out the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.5.0).

<!-- -->

## Getting started with Outline 0.5.0[​](#getting-started-with-outline-050 "Direct link to Getting started with Outline 0.5.0")

Ready to deploy Outline using Helm? Head over to our comprehensive [installation guides](https://community-charts.github.io/docs/category/outline) to find everything you need:

* Quick setup using default values
* Advanced configuration for custom environments
* Best practices for production use

Explore the full [Outline chart documentation](https://community-charts.github.io/docs/category/outline) and start building a powerful, knowledge-sharing platform backed by Kubernetes.

## Why choose the Outline Helm chart?[​](#why-choose-the-outline-helm-chart "Direct link to Why choose the Outline Helm chart?")

Maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the Outline Helm chart is a reliable and flexible solution for Kubernetes users. Here’s what makes it stand out:

* 🚀 **Quick to Deploy**: Easily get Outline running in minutes
* 👥 **Driven by the Community**: Built and improved by open-source contributors like you
* ⚙️ **Flexible Configuration**: Fine-tune settings for your specific needs
* 🛡️ **Production-Ready**: Actively maintained and tested for real-world use

## Join the community[​](#join-the-community "Direct link to Join the community")

We’d love for you to be part of the GitHub Community Charts initiative! Whether you want to help improve the chart, report issues, or share feature ideas, your input is always welcome:

* 🔎 Explore the [Outline documentation](https://community-charts.github.io/docs/category/outline)
* 📦 Contribute code with a pull request via our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐛 Report issues directly in our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Request new features that benefit everyone

Your support is what keeps this open-source project thriving. Thanks for helping us make Kubernetes deployments easier and more accessible for everyone!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-25-outline-chart-version-0-5-0-released.md)


---

# outline chart version 0.5.1 released

July 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the latest release of the **outline Helm chart version 0.5.1** is now available as of **July 25, 2025**, including support for **application version 0.85.1**. This update brings valuable enhancements and fixes driven by community feedback, making it even easier to run Outline on Kubernetes.

## What’s New in outline chart 0.5.1[​](#whats-new-in-outline-chart-051 "Direct link to What’s New in outline chart 0.5.1")

This version introduces key improvements across the Helm chart (v0.5.1) and the Outline application (v0.85.1). Here’s what’s included:

* ✅ **Authentication Fixes**: Corrected environment variable handling for client secrets, ensuring seamless integration with existing configurations for Gitea, GitLab, Auth0, and Keycloak.

You can view the full list of updates in our [GitHub release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.5.1).

<!-- -->

## Get Started with outline 0.5.1[​](#get-started-with-outline-051 "Direct link to Get Started with outline 0.5.1")

Ready to deploy Outline on Kubernetes? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/outline) make it simple:

* Deploy with default settings in just a few steps.
* Customize configurations for your specific needs.
* Follow best practices for production-grade setups.

Visit the [official documentation](https://community-charts.github.io/docs/category/outline) to begin your journey with Outline today.

## Why Choose the outline Helm Chart?[​](#why-choose-the-outline-helm-chart "Direct link to Why Choose the outline Helm Chart?")

Maintained by the dedicated [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the outline Helm chart offers a reliable and streamlined experience for Kubernetes users:

* 🚀 **User-Friendly**: Easy setup and configuration out of the box.
* 🤝 **Community-Backed**: Actively maintained by an engaged open-source community.
* 🔧 **Highly Configurable**: Flexible settings to support various deployment scenarios.
* 🛠️ **Production-Ready**: Continuously tested for Kubernetes stability and performance.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The GitHub Community Charts project thrives on collaboration. Whether you're fixing bugs, updating documentation, or suggesting features, your contribution matters. Here’s how you can get involved:

* 🛠️ Explore the [outline documentation](https://community-charts.github.io/docs/category/outline).
* 🔄 Submit code improvements via [pull requests](https://github.com/community-charts/helm-charts).
* 🐞 Found an issue? [Report it here](https://github.com/community-charts/helm-charts/issues).
* 💡 Have an idea? Use our [issue tracker](https://github.com/community-charts/helm-charts/issues/new) to suggest new features.

Thanks for being part of the Outline and Kubernetes community. Together, we’re building better open-source tools for everyone!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-25-outline-chart-version-0-5-1-released.md)


---

# Outline chart version 0.6.0 released

July 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart v0.6.0**, now available as of **July 25, 2025**, featuring **application version 0.85.1**. This version brings valuable improvements and fixes inspired by community feedback, making it even easier to run Outline on Kubernetes.

<!-- -->

## What’s new in chart version 0.6.0?[​](#whats-new-in-chart-version-060 "Direct link to What’s new in chart version 0.6.0?")

Here’s a look at what’s been updated in the Outline Helm chart (v0.6.0) alongside the application upgrade to version 0.85.1:

* ✅ **Resolved PostgreSQL secret key issue**: We've fixed a bug affecting the handling of existing secret keys for external PostgreSQL configurations. This ensures smoother setup and better reliability for users leveraging external databases.

For full technical details, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.0).

## Get started with Outline v0.6.0[​](#get-started-with-outline-v060 "Direct link to Get started with Outline v0.6.0")

Deploying Outline on Kubernetes has never been easier. Follow our comprehensive [installation guides](https://community-charts.github.io/docs/category/outline) to get up and running quickly:

* One-step installation using default configurations
* Custom setup options to match your unique environment
* Recommendations for production-grade deployments

Explore all configuration options in the [official Outline Helm Chart documentation](https://community-charts.github.io/docs/category/outline).

## Why use the Outline Helm chart?[​](#why-use-the-outline-helm-chart "Direct link to Why use the Outline Helm chart?")

The Outline Helm chart is maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts). Here’s why it’s trusted by developers and DevOps teams:

* ⚙️ **Streamlined setup** for Kubernetes environments
* 💡 **Community-driven development** with regular updates
* 🛠 **Flexible customization** to suit different workloads
* 🔒 **Reliable deployments** tested by a growing user base

## Join the community[​](#join-the-community "Direct link to Join the community")

We welcome contributors from all backgrounds! Whether you’re fixing issues, improving docs, or proposing new features, here’s how to get involved:

* 🔍 Browse the [Outline chart documentation](https://community-charts.github.io/docs/category/outline)
* 💻 Open pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or suggest enhancements via the [issue tracker](https://github.com/community-charts/helm-charts/issues)

Thanks for being part of the GitHub Community Charts family! Let’s keep improving Kubernetes deployments—together.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-07-25-outline-chart-version-0-6-0-released.md)


---

# Outline chart version 0.6.1 released

August 6, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest update to the Outline Helm chart — version **0.6.1**, available as of 2025-08-06. This release packages **Outline app version 0.86.0**, delivering new features, performance enhancements, and valuable fixes driven by community feedback.

## What's New in Outline 0.6.1 Chart[​](#whats-new-in-outline-061-chart "Direct link to What's New in Outline 0.6.1 Chart")

This version brings several meaningful updates to the Helm chart and its dependencies:

* ✅ Updated: Upgraded the main Docker image to `outlinewiki/outline:0.86.0`
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Updated: Bumped Redis Helm chart from version 21.2.11 to 21.2.14
  <br />
  <!-- -->
  → [See on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Updated: Upgraded PostgreSQL Helm chart from version 16.7.19 to 16.7.21
  <br />
  <!-- -->
  → [See on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a complete breakdown of changes and improvements, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.1).

<!-- -->

## Get Started with Outline 0.6.1[​](#get-started-with-outline-061 "Direct link to Get Started with Outline 0.6.1")

Looking to deploy Outline on Kubernetes? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/outline) walk you through everything from initial setup to production best practices:

* Install quickly using default configurations.
* Fine-tune for your environment with flexible options.
* Follow deployment guidance tailored for stability and scalability.

Explore the full [Outline documentation](https://community-charts.github.io/docs/category/outline) and get up and running today.

## Why Use the Outline Helm Chart?[​](#why-use-the-outline-helm-chart "Direct link to Why Use the Outline Helm Chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, the Outline Helm chart offers:

* 🚀 Fast & Easy Deployments: Minimal setup to get started on Kubernetes.
* 🛠 Customization: Adapts to a wide range of needs and infrastructure setups.
* 🌱 Community Support: Continuously maintained with improvements from contributors.
* 📦 Reliable by Design: Built for production-ready use cases.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We’d love for you to be part of shaping the future of this chart. Whether it’s code, feedback, or feature ideas — your input helps make the project better for everyone:

* 🔍 Learn more in the [official Outline chart docs](https://community-charts.github.io/docs/category/outline)
* 🔧 Contribute via pull requests on our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐛 Found an issue? [Report it here](https://github.com/community-charts/helm-charts/issues)
* 💡 Have a suggestion? [Request a feature](https://github.com/community-charts/helm-charts/issues/new)

Thank you for supporting Outline and the open-source community. Together, we’re making Kubernetes-first deployments more accessible and powerful for everyone.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-06-outline-chart-version-0-6-1-released.md)


---

# Outline chart update 0.6.2 brings app version 0.86.1

August 10, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the updated **Outline Helm chart version 0.6.2**, officially available as of August 10, 2025. This version ships with **app version 0.86.1** and introduces valuable upgrades and optimizations to make deploying Outline on Kubernetes even more efficient.

## What’s New in Version 0.6.2[​](#whats-new-in-version-062 "Direct link to What’s New in Version 0.6.2")

Packed with improvements and fresh updates, this release enhances both the Helm chart and the underlying Outline application. Here’s a quick look at what’s changed:

* ✅ **Application Update**: Bumped container image to outlinewiki/outline:0.86.1
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🔁 **Redis Upgrade**: Updated Redis dependency from 21.2.14 to 22.0.1
  <br />
  <!-- -->
  → [See Redis chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🛠️ **PostgreSQL Upgrade**: Updated PostgreSQL chart from 16.7.21 to 16.7.24
  <br />
  <!-- -->
  → [See PostgreSQL chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

To dive into the complete list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.2).

<!-- -->

## Getting Started[​](#getting-started "Direct link to Getting Started")

Ready to deploy Outline with the latest Helm chart? Our [comprehensive documentation](https://community-charts.github.io/docs/category/outline) makes it simple:

* 🔧 Follow quick-start installation steps with default values.
* 🎛️ Customize configuration for your team or production setup.
* 📦 Learn best practices for operating Outline in Kubernetes environments.

Explore deployment options and tailor your setup today by visiting the [Outline chart docs](https://community-charts.github.io/docs/category/outline).

## Why Use the Outline Helm Chart?[​](#why-use-the-outline-helm-chart "Direct link to Why Use the Outline Helm Chart?")

The Outline Helm chart, maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) team, is designed for stability, ease of use, and flexibility. Here's why it's a great choice:

* 🚀 **Quick Setup**: Get Outline up and running in no time.
* 🌱 **Open Source & Community-Powered**: Improved continuously by contributors.
* 🧩 **Highly Configurable**: Fit to your specific Kubernetes environment.
* ✅ **Trusted & Well-Maintained**: Tested for compatibility and durability.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

The GitHub Community Charts project thrives on community involvement. We’d love to have you onboard! Here’s how you can contribute:

* 📘 Learn more in the [Outline Helm chart documentation](https://community-charts.github.io/docs/category/outline)
* 🤝 Contribute via pull requests on our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Report issues or bugs through our [issue tracker](https://github.com/community-charts/helm-charts/issues)
* 💡 Share ideas or request features you’d like to see next

Thank you for being a part of the Outline and Kubernetes community. Let’s continue simplifying open-source deployments—together!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-10-outline-chart-version-0-6-2-released.md)


---

# Outline Helm Chart 0.6.3 Released with App Version 0.87.1

September 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the Outline Helm chart—version 0.6.3—available as of 2025-09-01. This release includes app version 0.87.1 and brings enhancements, updated dependencies, and valuable contributions from the open-source community.

## What’s New in 0.6.3[​](#whats-new-in-063 "Direct link to What’s New in 0.6.3")

This update refreshes both the Outline application and its supporting Helm chart, helping you streamline deployments on Kubernetes.

Here’s what’s included in this version:

* 🔄 Updated to use the latest Outline Docker image (v0.87.1)
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🧠 Redis dependency upgraded from 22.0.1 to 22.0.7
  <br />
  <!-- -->
  → [View Redis Helm Chart](https://artifacthub.io/packages/helm/bitnami/redis)
* 🐘 PostgreSQL dependency updated from 16.7.24 to 16.7.27
  <br />
  <!-- -->
  → [View PostgreSQL Helm Chart](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.3).

<!-- -->

## Get Started with Outline 0.6.3[​](#get-started-with-outline-063 "Direct link to Get Started with Outline 0.6.3")

Deploying Outline on Kubernetes has never been easier. Our step-by-step [installation guides](https://community-charts.github.io/docs/category/outline) walk you through everything you need to launch with confidence:

* Perform a quick start with default settings.
* Customize deployments to suit your environment.
* Follow production best practices.

Visit the official [Outline documentation](https://community-charts.github.io/docs/category/outline) to get started today.

## Why Use the Outline Helm Chart?[​](#why-use-the-outline-helm-chart "Direct link to Why Use the Outline Helm Chart?")

Built and maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), the Outline Helm chart offers a reliable and flexible way to run Outline on Kubernetes. Here's why users love it:

* ⚡ Easy setup with Helm and Kubernetes
* 🌱 Backed by a vibrant open-source community
* 🔧 Highly configurable for different workloads
* ✅ Production-tested reliability

## Join the Community[​](#join-the-community "Direct link to Join the Community")

We believe in open-source collaboration, and there are many ways to get involved:

* Browse the [Outline Helm chart documentation](https://community-charts.github.io/docs/category/outline).
* Contribute improvements or fixes via [GitHub pull requests](https://github.com/community-charts/helm-charts).
* Report issues and help shape future releases in our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* Suggest new features and contribute ideas—we’re all ears!

Thank you for being a part of the growing Outline and Kubernetes community. Let’s keep building great things, together!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-01-outline-chart-version-0-6-3-released.md)


---

# Outline chart update 0.6.4 now available

September 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.6.4** as of September 2, 2025, featuring the latest **application version 0.87.3**. This release brings key improvements, enhanced stability, and contributions from our vibrant community—making it even easier to deploy Outline in your Kubernetes environment.

## What’s new in version 0.6.4[​](#whats-new-in-version-064 "Direct link to What’s new in version 0.6.4")

This release includes updates to both the Helm chart (v0.6.4) and the Outline application (v0.87.3). Here’s a quick look at what’s changed:

* ✅ Updated: Switched to outlinewiki/outline Docker image version 0.87.3
  <br />
  <!-- -->
  👉 [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)

Check out the full list of changes in the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.4).

<!-- -->

## Quick start with the Outline 0.6.4 chart[​](#quick-start-with-the-outline-064-chart "Direct link to Quick start with the Outline 0.6.4 chart")

Looking to upgrade or start fresh? Our [installation guide](https://community-charts.github.io/docs/category/outline) offers clear and detailed steps to help you deploy Outline smoothly:

* Install quickly with default settings
* Customize your chart values for your team’s needs
* Follow production-ready best practices

Everything you need to get started is available in the [Outline documentation](https://community-charts.github.io/docs/category/outline).

## Why deploy Outline using Helm?[​](#why-deploy-outline-using-helm "Direct link to Why deploy Outline using Helm?")

The Outline Helm chart, maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts), is the easiest way to get Outline running on Kubernetes. Here’s why:

* 🚀 Easy to install and upgrade
* 👥 Backed by a growing community of contributors
* ⚙️ Flexible options to match your environment
* ✅ Stable and thoroughly tested for Kubernetes clusters

## Join the community[​](#join-the-community "Direct link to Join the community")

We’re building this project together—and we’d love for you to get involved. Here are a few ways to contribute:

* 🔍 Explore the [Outline documentation](https://community-charts.github.io/docs/category/outline) for configuration tips
* 🔧 Submit pull requests or issues via our [GitHub repository](https://github.com/community-charts/helm-charts)
* 🐞 Found something odd? [Report a bug](https://github.com/community-charts/helm-charts/issues)
* 💡 Have an idea? [Request a new feature](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the community and supporting open-source projects like Outline and GitHub Community Charts. Let’s keep making Kubernetes easier—together.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-02-outline-chart-version-0-6-4-released.md)


---

# Outline chart version 0.6.5 released

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the Outline Helm chart, **v0.6.5**, is now available, featuring **app version 0.87.4**! This release brings important updates and improvements focused on delivering a smoother and more flexible deployment experience on Kubernetes.

## What’s new in Chart v0.6.5[​](#whats-new-in-chart-v065 "Direct link to What’s new in Chart v0.6.5")

With this release, you’ll benefit from updated components that enhance reliability and simplify deployment:

* 🔄 **Updated**: `outlinewiki/outline` image bumped to version 0.87.4
  <br />
  <!-- -->
  → Check it out on [Docker Hub](https://hub.docker.com/r/outlinewiki/outline)

For the full list of changes, view the official [v0.6.5 release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.5) on GitHub.

<!-- -->

## Get started with Outline 0.6.5[​](#get-started-with-outline-065 "Direct link to Get started with Outline 0.6.5")

Looking to deploy Outline with Helm? Our updated [installation guide](https://community-charts.github.io/docs/category/outline) walks you through everything you need:

* Install with default settings in a few steps
* Customize configurations for your environment
* Follow best practices for production-ready setups

Check out the documentation to begin your deployment journey today.

## Why use the Outline Helm chart?[​](#why-use-the-outline-helm-chart "Direct link to Why use the Outline Helm chart?")

Maintained by the open-source community through the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, this Helm chart aims to make Kubernetes deployments easier and more accessible:

* ⚙️ **User-Friendly**: Quick installation and minimal setup
* 🌍 **Community-Driven**: Regular contributions and active support
* 🛠 **Highly Configurable**: Adaptable for various workloads
* ✅ **Kubernetes-Ready**: Built and tested for stability

## Contribute to the project[​](#contribute-to-the-project "Direct link to Contribute to the project")

The power of open-source lies in its community, and we’d love for you to be part of it! Here’s how you can get involved:

* 🔍 Learn more: Explore the [Outline Helm documentation](https://community-charts.github.io/docs/category/outline)
* 🛠 Contribute: Submit a pull request on our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐛 Found an issue? [Report it here](https://github.com/community-charts/helm-charts/issues)
* 💡 Share ideas: Request features using our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the Outline and Community Charts ecosystem. Let’s keep improving the Kubernetes experience—together!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-18-outline-chart-version-0-6-5-released.md)


---

# Outline chart 0.7.0 released with app version 0.87.4

September 20, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the new version of the Outline Helm chart—**v0.7.0**—is now available! This release includes **application version 0.87.4** and delivers meaningful improvements that enhance reliability and simplify Kubernetes deployments.

## What’s new in v0.7.0[​](#whats-new-in-v070 "Direct link to What’s new in v0.7.0")

Version 0.7.0 of the Outline Helm chart introduces key enhancements that focus on stability and lifecycle automation. Here’s what’s changed:

* ✅ **Improved deployment automation**: Added automatic rolling restarts for deployments when ConfigMaps or Secrets change, using checksum annotations in deployment templates.
  <br />
  <!-- -->
  → See the community discussion: [GitHub Issue #238](https://github.com/community-charts/helm-charts/issues/238)

For the full release details, check out the complete [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.0).

<!-- -->

## Get started with Outline 0.7.0[​](#get-started-with-outline-070 "Direct link to Get started with Outline 0.7.0")

Ready to deploy Outline with Helm? Our detailed [installation guides](https://community-charts.github.io/docs/category/outline) cover everything you need to start:

* Step-by-step installation using default settings.
* Custom configuration options for your environment.
* Deployment tips for production-ready setups.

Explore the updated [Outline documentation](https://community-charts.github.io/docs/category/outline) and launch your instance today.

## Why use the Outline Helm chart?[​](#why-use-the-outline-helm-chart "Direct link to Why use the Outline Helm chart?")

Maintained by the open-source community at [GitHub Community Charts](https://github.com/community-charts/helm-charts), the Outline Helm chart makes deploying Outline to Kubernetes straightforward and reliable.

Benefits include:

* 🔧 **Easy setup** with smart defaults.
* 🌱 **Community-powered development** and regular updates.
* 🛠️ **Flexible configurations** for all use cases.
* ✅ **Production-ready** design tested in real-world environments.

## Join the community[​](#join-the-community "Direct link to Join the community")

The GitHub Community Charts project is open-source and community-driven. Your feedback and contributions help us grow and improve continuously:

* 📘 Browse the [Outline chart documentation](https://community-charts.github.io/docs/category/outline).
* 🧪 Submit pull requests or enhancements on [GitHub](https://github.com/community-charts/helm-charts).
* 🐞 Report bugs or ask questions in the [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Have an idea? [Request features](https://github.com/community-charts/helm-charts/issues/new) directly.

Thank you for being part of the Outline and Kubernetes Helm ecosystem. We're building better deployment tools—together!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-09-20-outline-chart-version-0-7-0-released.md)


---

# Outline chart update 0.7.1 with app version 1.0.0

October 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.7.1**, officially available as of October 27, 2025. This latest version includes **app version 1.0.0**, delivering key updates, improved stability, and valuable contributions from our open-source community.

Whether you're running Outline in production or exploring it for the first time, this release brings smoother deployment and better integration with your Kubernetes environment.

## What’s new in version 0.7.1[​](#whats-new-in-version-071 "Direct link to What’s new in version 0.7.1")

This update improves both the Helm chart and important dependencies, aligning with the latest enhancements from upstream projects:

* ✅ Upgraded Outline Docker image to **v1.0.0**
  <br />
  <!-- -->
  ↳ [View upstream image](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Updated Redis dependency from 22.0.7 to **23.2.1**
  <br />
  <!-- -->
  ↳ [Redis Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Updated PostgreSQL dependency from 16.7.27 to **18.1.1**
  <br />
  <!-- -->
  ↳ [PostgreSQL Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

See the full changelog in the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.1).

<!-- -->

## Getting started with Outline 0.7.1[​](#getting-started-with-outline-071 "Direct link to Getting started with Outline 0.7.1")

Ready to deploy? Our comprehensive [documentation](https://community-charts.github.io/docs/category/outline) makes getting started easy:

* Install with default settings using a single Helm command
* Customize configurations to suit your environment
* Follow tips and best practices for production-ready deployments

Visit the [Outline installation guides](https://community-charts.github.io/docs/category/outline) to begin.

## Why use the Outline Helm chart?[​](#why-use-the-outline-helm-chart "Direct link to Why use the Outline Helm chart?")

Maintained by the GitHub Community Charts team, the Outline Helm chart offers everything you need for a reliable Kubernetes deployment:

* 🔧 Simple and fast installation process
* 🧩 Highly configurable for different environments
* 📦 Regular updates powered by community contributions
* ✅ Tested compatibility with current Kubernetes best practices

Whether you're running a small team wiki or a large knowledge base, this chart scales with your needs.

## Join our growing community[​](#join-our-growing-community "Direct link to Join our growing community")

The GitHub Community Charts project values your support and contributions. Here’s how you can get involved:

* 📚 Explore the [Outline chart documentation](https://community-charts.github.io/docs/category/outline)
* 💡 Send pull requests to our [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs or issues via the [issue tracker](https://github.com/community-charts/helm-charts/issues)
* ✨ Suggest feature ideas and let us know what you’d love to see next

Thanks for being a part of the open-source community making Outline even better on Kubernetes. Let’s keep building together!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-27-outline-chart-version-0-7-1-released.md)


---

# Outline chart 0.7.2 includes app version 1.0.1 with Redis and Postgres updates

October 30, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to introduce the release of the **Outline Helm chart version 0.7.2**, published on October 30, 2025. This release includes support for **Outline application version 1.0.1** and brings important updates to chart dependencies—making it easier than ever to run and scale Outline on Kubernetes.

<!-- -->

## What's new in Outline 0.7.2[​](#whats-new-in-outline-072 "Direct link to What's new in Outline 0.7.2")

This version provides a series of enhancements and community-led improvements that update the chart for performance, reliability, and compatibility:

* 🔄 **Application update**: Upgrades the container image to `outlinewiki/outline:1.0.1`<br />[View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)

* 🛠 **Redis update**: Bumps Helm chart dependency from version 23.2.1 to 23.2.2<br />[View Redis Chart](https://artifacthub.io/packages/helm/bitnami/redis)

* 🗄 **PostgreSQL update**: Upgrades postgresql chart from version 18.1.1 to 18.1.3<br />[View PostgreSQL Chart](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of changes, check out the official [GitHub release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.2).

## How to install Outline 0.7.2[​](#how-to-install-outline-072 "Direct link to How to install Outline 0.7.2")

Getting started with the latest Outline chart is simple. Head over to our [installation documentation](https://community-charts.github.io/docs/category/outline) for setup instructions and configuration examples tailored to your needs:

* Quick install steps using default values
* Advanced customization for production use
* Deployment best practices for Kubernetes environments

Everything you need to get running is in our [Outline Helm docs](https://community-charts.github.io/docs/category/outline).

## Why deploy Outline using the Helm chart?[​](#why-deploy-outline-using-the-helm-chart "Direct link to Why deploy Outline using the Helm chart?")

The Outline Helm chart, maintained by the [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, is a reliable and flexible way to manage your installation in Kubernetes. Here’s why the community loves it:

* ✅ **Easy to deploy**: Minimize manual setup with templated configurations
* 🔁 **Community-supported**: Active development with feedback from real users
* 🧩 **Highly configurable**: Designed for use cases both simple and complex
* 🔐 **Built for Kubernetes**: Optimized for scalable, cloud-native environments

## Join the community[​](#join-the-community "Direct link to Join the community")

We believe in open-source and welcome your involvement! Whether you're here to deploy Outline, improve the chart, or join in discussions, there are plenty of ways to get started:

* Read the [Outline Helm chart docs](https://community-charts.github.io/docs/category/outline)
* Contribute via pull requests on [GitHub](https://github.com/community-charts/helm-charts)
* Report bugs or share ideas through the [GitHub issue tracker](https://github.com/community-charts/helm-charts/issues)

Thank you for being part of the Outline and Helm chart community. Together, we’re building a better Kubernetes experience—one release at a time.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [Redis](/blog/tags/redis.md "Configure your applications with Redis for caching, queueing, and real-time data, including managed Redis on major cloud providers.")
* [Postgres](/blog/tags/postgres.md "Learn how to configure applications with PostgreSQL for reliable data storage, including guides for managed PostgreSQL on AWS, Google Cloud, and Azure.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-10-30-outline-chart-version-0-7-2-released.md)


---

# Outline chart version 0.7.3 released

November 17, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest update to the Outline Helm chart — version 0.7.3 — available as of November 17, 2025. This release brings support for Outline application version 1.1.0 and includes several improvements aimed at streamlining your Kubernetes deployment experience.

## What’s New in Chart Version 0.7.3[​](#whats-new-in-chart-version-073 "Direct link to What’s New in Chart Version 0.7.3")

This release introduces meaningful enhancements both to the Helm chart and to the application itself. Here’s what’s been updated:

* 🛠️ Updated the container image to outlinewiki/outline app version 1.1.0
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Refreshed Redis dependency from version 23.2.2 to 23.2.12
  <br />
  <!-- -->
  → [See on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Upgraded PostgreSQL dependency from version 18.1.3 to 18.1.9
  <br />
  <!-- -->
  → [See on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full breakdown of changes, head over to the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.3) on GitHub.

<!-- -->

## Getting Started with Outline 0.7.3[​](#getting-started-with-outline-073 "Direct link to Getting Started with Outline 0.7.3")

Ready to deploy Outline on Kubernetes? The new chart version makes it easier than ever. Our comprehensive [installation guides](https://community-charts.github.io/docs/category/outline) can help you:

* Perform a quick deployment using default settings.
* Customize your Outline installation for your specific environment.
* Follow best practices for staging and production-level deployments.

Take the first step by visiting the [Outline Helm chart documentation](https://community-charts.github.io/docs/category/outline).

## Why Use the Outline Helm Chart?[​](#why-use-the-outline-helm-chart "Direct link to Why Use the Outline Helm Chart?")

The Outline Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), offers a dependable and flexible way to manage your Outline deployments on Kubernetes. Key advantages include:

* ✅ Easy to install and configure.
* 🌍 Built and improved by a vibrant open-source community.
* ⚙️ Customizable to meet various deployment scenarios.
* 🧪 Stability tested for real-world use in Kubernetes environments.

## Join the Community[​](#join-the-community "Direct link to Join the Community")

Your voice and contributions matter! The GitHub Community Charts project thrives on collaboration. Here’s how you can get involved:

* 🧭 Explore configuration options in the [Outline chart docs](https://community-charts.github.io/docs/category/outline).
* 🛠️ Submit pull requests to the [Helm charts repo](https://github.com/community-charts/helm-charts).
* 🐛 Report bugs or issues directly on our [issue tracker](https://github.com/community-charts/helm-charts/issues).
* 💡 Share new ideas and feature requests via GitHub.

Thank you for being part of this growing open-source effort. Let’s continue building and improving Outline deployments—together!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-11-17-outline-chart-version-0-7-3-released.md)


---

# Outline Chart Version 0.7.4 Released

May 29, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **Outline Helm chart version 0.7.4** on May 29, 2026, featuring **app version 1.7.1**. This latest update introduces an array of new features, enhancements, and community-driven improvements designed to make deploying Outline on Kubernetes even easier.

## What's New in Outline Chart 0.7.4[​](#whats-new-in-outline-chart-074 "Direct link to What's New in Outline Chart 0.7.4")

This release showcases updates to the Helm chart (version 0.7.4) alongside the underlying application (version 1.7.1). Here’s a quick look at the key changes:

* **Changed**: Updated the outlinewiki/outline image version to 1.7.1
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/outlinewiki/outline)
* **Fixed**: Resolved entrypoint script issues, now utilizing node instead of yarn (a requirement since v1.2.0)
  <!-- -->
  * [Upstream Release Notes](https://github.com/outline/outline/releases/tag/v1.2.0)
* **Changed**: Updated the Redis dependency from 23.2.12 to 25.5.3
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* **Changed**: Updated the PostgreSQL dependency from 18.1.9 to 18.6.8
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of changes, you can refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.4) on GitHub.

<!-- -->

## Getting Started with Outline Chart 0.7.4[​](#getting-started-with-outline-chart-074 "Direct link to Getting Started with Outline Chart 0.7.4")

Are you ready to deploy Outline 0.7.4? Our [installation guides](https://community-charts.github.io/docs/category/outline) provide easy-to-follow instructions for getting started, including:

* Quick installation using default configurations.
* Customization options to fit your specific environment.
* Best practices for seamless production deployments.

Explore the [Outline documentation](https://community-charts.github.io/docs/category/outline) to discover all your deployment options and bring Outline to life today!

## Why Choose the Outline Helm Chart?[​](#why-choose-the-outline-helm-chart "Direct link to Why Choose the Outline Helm Chart?")

The Outline Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is meticulously designed to facilitate straightforward and reliable deployments of Outline on Kubernetes. Here are just a few reasons to choose it:

* **Ease of Use**: Enjoy simplified installation and configuration.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by our passionate community.
* **Flexibility**: Access a range of configurable options tailored to diverse use cases.
* **Reliability**: Count on stability tested in various Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on contributions from enthusiastic individuals like you! Whether you want to fix bugs, enhance documentation, or propose exciting new features, we invite you to get involved:

* **Explore the Chart**: Visit the [Outline documentation](https://community-charts.github.io/docs/category/outline) for detailed configuration information.
* **Contribute**: Submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, don’t hesitate to [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: We encourage suggestions for improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being a part of the Outline and GitHub Community Charts journey. Together, we can make Kubernetes deployments a breeze!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-05-29-outline-chart-version-0-7-4-released.md)


---

# Outline Chart Version 0.7.5 Released

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **Outline Helm chart version 0.7.5** on June 2, 2026, now featuring **app version 1.8.0**. This release brings a host of new features, enhancements, and improvements driven by our vibrant community, all designed to make deploying Outline on Kubernetes easier than ever.

## What's New in Outline 0.7.5 Chart[​](#whats-new-in-outline-075-chart "Direct link to What's New in Outline 0.7.5 Chart")

In this update, you’ll find significant improvements to both the Helm chart (version 0.7.5) and the underlying application (version 1.8.0). Here’s a quick overview of the changes:

* **Changed**: Updated the Outline image version to 1.8.0
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/outlinewiki/outline)
* **Changed**: Updated the PostgreSQL dependency from 18.6.8 to 18.7.0
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a detailed look at all changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.5) on GitHub.

<!-- -->

## Getting Started with Outline 0.7.5 Chart[​](#getting-started-with-outline-075-chart "Direct link to Getting Started with Outline 0.7.5 Chart")

Ready to deploy Outline 0.7.5? Our [installation guides](https://community-charts.github.io/docs/category/outline) offer comprehensive, step-by-step instructions to help you get started, including:

* Quick installation with default settings.
* Customization options tailored to your environment.
* Best practices for successful production deployments.

Visit the [Outline documentation](https://community-charts.github.io/docs/category/outline) to learn about all available features and start your deployment today.

## Why Choose the Outline Helm Chart?[​](#why-choose-the-outline-helm-chart "Direct link to Why Choose the Outline Helm Chart?")

The Outline Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), simplifies deploying Outline on Kubernetes while ensuring reliability. Here are some key benefits:

* **Ease of Use**: Streamlined installation and configuration process.
* **Community-Driven**: Regular updates and enhancements provided by our contributors.
* **Flexibility**: Configurable options for various use cases.
* **Reliability**: Thoroughly tested to ensure stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on community contributions, and we would love your involvement! Whether you're fixing bugs, enhancing documentation, or proposing new features, here’s how you can join us:

* **Explore the Chart**: Dive into the [Outline documentation](https://community-charts.github.io/docs/category/outline) for detailed configuration options.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you encounter a bug, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for your support of Outline and GitHub Community Charts! Together, we can make Kubernetes deployments even easier.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-02-outline-chart-version-0-7-5-released.md)


---

# Outline Chart Version 0.8.0 Released

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **Outline Helm Chart Version 0.8.0** on June 2, 2026, featuring **App Version 1.8.0**. This latest update introduces new functionalities, improvements, and valuable enhancements driven by our community, making it even easier to deploy Outline on Kubernetes.

## What's New in the Outline 0.8.0 Chart[​](#whats-new-in-the-outline-080-chart "Direct link to What's New in the Outline 0.8.0 Chart")

The release includes important updates to both the Helm Chart (version 0.8.0) and the underlying application (version 1.8.0). Here’s a brief overview of the changes:

* **Added**: Support for setting custom labels on the local persistence PVC.

For a comprehensive list of updates, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.8.0) on GitHub.

<!-- -->

## Getting Started with Outline 0.8.0 Chart[​](#getting-started-with-outline-080-chart "Direct link to Getting Started with Outline 0.8.0 Chart")

Are you ready to deploy Outline 0.8.0? Our [installation guides](https://community-charts.github.io/docs/category/outline) provide detailed, step-by-step instructions to get you up and running, including:

* Quick installation using default configurations.
* Customizing settings to align with your specific environment.
* Best practices for successful production deployments.

Explore the full range of deployment options by visiting the [Outline documentation](https://community-charts.github.io/docs/category/outline) today!

## Why Choose the Outline Helm Chart?[​](#why-choose-the-outline-helm-chart "Direct link to Why Choose the Outline Helm Chart?")

The Outline Helm Chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to streamline the deployment process on Kubernetes. Here are just a few reasons to choose it:

* **Ease of Use**: Enjoy simplified installation and configuration processes.
* **Community-Driven**: Benefit from regular updates and enhancements contributed by the community.
* **Flexibility**: Utilize configurable options tailored to various use cases.
* **Reliability**: Count on tested stability within Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

At GitHub Community Charts, we value your participation! We encourage you to join our community by contributing in various ways. Whether you're fixing bugs, improving documentation, or suggesting new features, here's how to get started:

* **Explore the Chart**: Dive into the [Outline documentation](https://community-charts.github.io/docs/category/outline) for configuration insights.
* **Contribute**: Share your expertise by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Encountered a bug? [Let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your ideas for improvements via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting Outline and the GitHub Community Charts. Together, we can continue to simplify Kubernetes deployments!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-02-outline-chart-version-0-8-0-released.md)


---

# Outline Chart Version 0.8.1 Released

June 7, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **Outline Helm Chart Version 0.8.1** on June 7, 2026, which comes with the latest **App Version 1.8.1**. This update introduces an array of new features, enhancements, and community-inspired improvements that make deploying Outline on Kubernetes easier than ever.

## What's New in Outline 0.8.1 Chart[​](#whats-new-in-outline-081-chart "Direct link to What's New in Outline 0.8.1 Chart")

This release includes significant updates to both the Helm chart (Version 0.8.1) and the associated application (Version 1.8.1). Here’s a detailed look at the changes:

* **Updated**: The Outline image version has been upgraded to 1.8.1
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/outlinewiki/outline)
* **Updated**: Redis dependency has been refreshed from 25.5.3 to 27.0.4
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* **Updated**: PostgreSQL dependency has been updated from 18.7.0 to 18.7.2
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a complete overview of the updates, check out the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.8.1) on GitHub.

<!-- -->

## Getting Started with Outline 0.8.1 Chart[​](#getting-started-with-outline-081-chart "Direct link to Getting Started with Outline 0.8.1 Chart")

Are you ready to deploy Outline 0.8.1? Our comprehensive [installation guides](https://community-charts.github.io/docs/category/outline) provide step-by-step instructions to ensure your setup is seamless, including:

* Quick installation with default configurations.
* Customizing settings to fit your unique environment.
* Best practices for production-grade deployments.

Don’t forget to visit the [Outline documentation](https://community-charts.github.io/docs/category/outline) to discover all available options and get started today!

## Why Choose the Outline Helm Chart?[​](#why-choose-the-outline-helm-chart "Direct link to Why Choose the Outline Helm Chart?")

The Outline Helm Chart, expertly maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to simplify and enhance your deployment experience on Kubernetes. Here are some key benefits:

* **User-Friendly**: Streamlined installation and configuration processes.
* **Community-Driven**: Regular updates and enhancements from dedicated contributors.
* **Flexible**: Customizable options to accommodate various use cases.
* **Reliable**: Thoroughly tested for stability in diverse Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts thrives on collaboration, and we invite you to be a part of it! Whether you're interested in fixing bugs, enhancing documentation, or suggesting new features, here's how you can contribute:

* **Explore the Chart**: Dive into the [Outline documentation](https://community-charts.github.io/docs/category/outline) for detailed configuration information.
* **Contribute**: Share your expertise by submitting pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: Found a bug? We’d love to hear about it—[let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Have an idea for an improvement? Share your suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for being part of the Outline and GitHub Community Charts journey. Together, let's make Kubernetes deployments even more accessible and efficient!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-07-outline-chart-version-0-8-1-released.md)


---

# outline chart version 0.9.0 released

June 20, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **outline Helm chart version 0.9.0** on June 20, 2026, featuring **app version 1.8.1**. This latest update introduces a host of new features, enhancements, and community-driven improvements, all aimed at making your deployment of outline on Kubernetes more seamless.

## What's New in outline 0.9.0 chart[​](#whats-new-in-outline-090-chart "Direct link to What's New in outline 0.9.0 chart")

This version includes important updates to both the Helm chart (version 0.9.0) and the underlying application (version 1.8.1). Check out the detailed changelog below:

* **Added**: Optional image digest support for immutable image pulls.

* **Fixed**: Enabled readOnlyRootFilesystem and added a built-in tmp emptyDir volume.

* **Changed**: Updated outlinewiki/outline image version to 1.8.1

  * [Upstream Project](https://hub.docker.com/r/outlinewiki/outline)

* **Changed**: Upgraded dependency redis from version 25.5.3 to 27.0.4

  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* **Changed**: Updated dependency postgresql from version 18.7.0 to 18.7.2

  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a complete list of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.9.0) on GitHub.

<!-- -->

## Getting Started with outline 0.9.0 chart[​](#getting-started-with-outline-090-chart "Direct link to Getting Started with outline 0.9.0 chart")

Are you ready to deploy outline 0.9.0? Our [installation guides](https://community-charts.github.io/docs/category/outline) provide you with step-by-step instructions to get started, including:

* Quick installation using default configurations.
* Customizing settings to fit your specific environment.
* Best practices for successful production deployments.

Visit the [outline documentation](https://community-charts.github.io/docs/category/outline) to discover all available options and deploy outline today.

## Why Choose the outline Helm Chart?[​](#why-choose-the-outline-helm-chart "Direct link to Why Choose the outline Helm Chart?")

The outline Helm chart, maintained by [GitHub Community Charts](https://github.com/community-charts/helm-charts), is crafted to make it easy and reliable to deploy outline on Kubernetes. Key benefits include:

* **Ease of Use**: Simplified installation and configuration process.
* **Community-Driven**: Regular updates and enhancements from a dedicated group of contributors.
* **Flexibility**: Configurable options to cater to various use cases.
* **Reliability**: Thoroughly tested for stability in Kubernetes environments.

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is a collaborative project, and we invite you to contribute! Whether you want to fix bugs, enhance documentation, or propose new features, here’s how you can get started:

* **Explore the Chart**: Dive into the [outline documentation](https://community-charts.github.io/docs/category/outline) for detailed configuration information.
* **Contribute**: Submit your pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
* **Report Issues**: If you discover a bug, please [let us know](https://github.com/community-charts/helm-charts/issues).
* **Request Features**: Share your improvement suggestions via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new).

Thank you for supporting outline and the GitHub Community Charts. Together, let's make Kubernetes deployments easier and more effective!

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2026-06-20-outline-chart-version-0-9-0-released.md)


---

## [cloudflared chart version 2.1.3 released](/blog/cloudflared-chart-version-2.1.3-released.md)

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest cloudflared Helm chart—version 2.1.3—officially available as of September 18, 2025. This update includes app version 2025.9.0 and brings helpful enhancements designed to simplify your Kubernetes deployments.

## What’s new in cloudflared 2.1.3[​](#whats-new-in-cloudflared-213 "Direct link to What’s new in cloudflared 2.1.3")

Version 2.1.3 focuses on staying up to date with upstream developments and ensuring a smoother deployment experience. Key changes include:

* ✅ Updated container image to cloudflare/cloudflared version 2025.9.0
  <!-- -->
  * [Check the image on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

Review the full changelog in the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.3) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.1.3-released.md)


---

## [Outline Helm Chart 0.6.3 Released with App Version 0.87.1](/blog/outline-chart-version-0.6.3-released.md)

September 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the Outline Helm chart—version 0.6.3—available as of 2025-09-01. This release includes app version 0.87.1 and brings enhancements, updated dependencies, and valuable contributions from the open-source community.

## What’s New in 0.6.3[​](#whats-new-in-063 "Direct link to What’s New in 0.6.3")

This update refreshes both the Outline application and its supporting Helm chart, helping you streamline deployments on Kubernetes.

Here’s what’s included in this version:

* 🔄 Updated to use the latest Outline Docker image (v0.87.1)
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🧠 Redis dependency upgraded from 22.0.1 to 22.0.7
  <br />
  <!-- -->
  → [View Redis Helm Chart](https://artifacthub.io/packages/helm/bitnami/redis)
* 🐘 PostgreSQL dependency updated from 16.7.24 to 16.7.27
  <br />
  <!-- -->
  → [View PostgreSQL Helm Chart](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.3).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.6.3-released.md)


---

## [pypiserver chart version 0.1.8 released](/blog/pypiserver-chart-version-0.1.8-released.md)

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of our Helm chart for pypiserver — version 0.1.8 — now available as of August 19, 2025. This release delivers support for app version **v2.4.0**, bringing new features and meaningful improvements to make your Helm-based deployments even more seamless.

**Tags:**

* [PyPI Server](/blog/tags/pypiserver.md "Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/pypiserver-chart-version-0.1.8-released.md)


---

## [n8n chart version 1.13.8 released](/blog/n8n-chart-version-1.13.8-released.md)

August 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest stable version of the **n8n Helm chart — version 1.13.8**, published on August 4, 2025! This release includes **n8n app version 1.105.2**, with valuable upgrades and refinements to improve your workflow automation experience on Kubernetes.

## What’s new in Helm chart 1.13.8?[​](#whats-new-in-helm-chart-1138 "Direct link to What’s new in Helm chart 1.13.8?")

In this version, both the chart and its dependencies have been refreshed to deliver a more secure and reliable deployment experience.

* ✅ **Updated**: n8n image version is now 1.105.2
  <br />
  <!-- -->
  → Check out the upstream repo: [n8n GitHub](https://github.com/n8n-io/n8n)
* 🔁 **Updated**: Redis dependency upgrade from 21.2.13 to 21.2.14
  <br />
  <!-- -->
  → View it on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For a complete breakdown, see the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.13.8-released.md)


---

## [mlflow chart version 1.3.2 released](/blog/mlflow-chart-version-1.3.2-released.md)

July 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **mlflow Helm chart version 1.3.2** is now available as of **2025-07-24**, bringing you **mlflow app version 3.1.4**. This release delivers usability enhancements and community-driven improvements to make deploying mlflow on Kubernetes even smoother and more efficient.

## What’s New in Helm Chart 1.3.2[​](#whats-new-in-helm-chart-132 "Direct link to What’s New in Helm Chart 1.3.2")

With this release, both the Helm chart and the application itself have been upgraded to offer better functionality and integration:

* 🚀 **Updated**: Container image upgraded to `burakince/mlflow:3.1.4`
  <br />
  <!-- -->
  → View on [Docker Hub](https://hub.docker.com/r/burakince/mlflow)

To see all technical changes, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.2).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.3.2-released.md)


---

## [outline chart version 0.4.1 released](/blog/outline-chart-version-0.4.1-released.md)

July 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm Chart version 0.4.1**, available as of July 4, 2025. This update delivers important improvements and refreshed dependencies to make deploying Outline on your Kubernetes clusters smoother and more efficient.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.4.1-released.md)


---

## [n8n chart version 1.10.0 now available](/blog/n8n-chart-version-1.10.0-released.md)

June 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **n8n Helm chart version 1.10.0**, launched on 2025-06-27 and powered by **application version 1.99.1**. This update introduces new features, usability enhancements, and community-requested improvements that make deploying n8n on Kubernetes easier and more flexible than ever.

## What’s New in Version 1.10.0[​](#whats-new-in-version-1100 "Direct link to What’s New in Version 1.10.0")

This release includes updates to both the Helm chart and the underlying application. Highlights from the changelog include:

* ✅ **Form Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/147)
* ✅ **MCP Server Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/148)
* ✅ **New flag introduced to enable or disable service as needed**

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.10.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.10.0-released.md)


---

## [n8n chart version 1.22.6 released](/blog/n8n-chart-version-1.22.6-released.md)

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the arrival of **n8n Helm chart version 1.22.6** on 2026-06-19, which includes the latest **app version 2.26.7**. This update features a variety of enhancements and community-driven improvements aimed at simplifying the deployment of n8n on Kubernetes.

## What's New in n8n 1.22.6 Chart[​](#whats-new-in-n8n-1226-chart "Direct link to What's New in n8n 1.22.6 Chart")

This release encompasses updates for both the Helm chart (version 1.22.6) and the underlying application (version 2.26.7). Here’s a glimpse into the changes made:

* **Changed**: Updated the n8nio/n8n image version to 2.26.7
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency postgresql from 18.7.5 to 18.7.6
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of the changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.6) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.22.6-released.md)


---

## [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md)

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce that **n8n Helm chart version 1.21.0** has been released as of 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and community-driven improvements designed to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.21.0 chart[​](#whats-new-in-n8n-1210-chart "Direct link to What's New in n8n 1.21.0 chart")

This release brings important updates to both the Helm chart (version 1.21.0) and the underlying application (version 2.23.4). Here are some highlights from the changelog:

* **Added**: Support for extra manifests through `extraManifests` and `extraTemplateManifests` values.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.21.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.21.0-released.md)


---

## [MLflow Chart Version 1.8.5 Released](/blog/mlflow-chart-version-1.8.5-released.md)

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **MLflow Helm chart version 1.8.5** on June 2, 2026, featuring **app version 3.13.0**. This update brings a wealth of new features, enhancements, and community-driven improvements designed to streamline your MLflow deployment on Kubernetes.

## What's New in MLflow 1.8.5 Chart[​](#whats-new-in-mlflow-185-chart "Direct link to What's New in MLflow 1.8.5 Chart")

This release includes updates to both the Helm chart (version 1.8.5) and the underlying application (version 3.13.0). Here are some of the key changes:

* **Fixed**: Resolved broken screenshot URL(s) in the MLflow chart.

For a comprehensive list of changes, you can view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.5) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.5-released.md)


---

## [Cloudflared Chart Version 2.2.8 Released](/blog/cloudflared-chart-version-2.2.8-released.md)

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **cloudflared Helm chart version 2.2.8** on May 29, 2026, featuring **app version 2026.5.2**. This update introduces new features and community-driven enhancements to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.8 Chart[​](#whats-new-in-cloudflared-228-chart "Direct link to What's New in Cloudflared 2.2.8 Chart")

This release not only updates the Helm chart (version 2.2.8) but also the underlying application (version 2026.5.2). Here are the key changes:

* **Changed**: Updated cloudflare/cloudflared image version to 2026.5.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete breakdown of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.8) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.2.8-released.md)


---

## [n8n chart version 1.16.8 released](/blog/n8n-chart-version-1.16.8-released.md)

December 5, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.16.8**, is now available as of December 5, 2025. This release packages **app version 1.122.5** and includes key updates to streamline your workflow automation deployments on Kubernetes.

## What’s New in Version 1.16.8[​](#whats-new-in-version-1168 "Direct link to What’s New in Version 1.16.8")

This update brings improvements to the Helm chart along with the bump to the latest n8n app release. Here's what’s changed:

* 🛠️ **Updated**: n8nio/n8n Docker image upgraded to version 1.122.5
  <br />
  <!-- -->
  → [Upstream Repository](https://github.com/n8n-io/n8n)

Check out the full changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.16.8-released.md)


---

## [mlflow chart version 1.8.0 released](/blog/mlflow-chart-version-1.8.0-released.md)

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.8.0**, available as of 2025-11-08. This release includes the latest **app version 3.6.0** and brings valuable improvements focused on performance, customization, and Kubernetes-native deployments.

## What’s New in mlflow Helm chart 1.8.0[​](#whats-new-in-mlflow-helm-chart-180 "Direct link to What’s New in mlflow Helm chart 1.8.0")

This version of the chart includes important updates designed to offer greater flexibility when running mlflow on Kubernetes. Highlights include:

* ✅ **Resource Configuration for Init Containers**: You can now define compute resources for the `dbchecker` and `ini-file-initializer` init containers.
  <br />
  <!-- -->
  See the discussion on [GitHub Issue #265](https://github.com/community-charts/helm-charts/issues/265)

These changes allow for more efficient use of resources and better alignment with production-grade deployments.

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.0).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.0-released.md)


---

## [Outline chart update 0.7.1 with app version 1.0.0](/blog/outline-chart-version-0.7.1-released.md)

October 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.7.1**, officially available as of October 27, 2025. This latest version includes **app version 1.0.0**, delivering key updates, improved stability, and valuable contributions from our open-source community.

Whether you're running Outline in production or exploring it for the first time, this release brings smoother deployment and better integration with your Kubernetes environment.

## What’s new in version 0.7.1[​](#whats-new-in-version-071 "Direct link to What’s new in version 0.7.1")

This update improves both the Helm chart and important dependencies, aligning with the latest enhancements from upstream projects:

* ✅ Upgraded Outline Docker image to **v1.0.0**
  <br />
  <!-- -->
  ↳ [View upstream image](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Updated Redis dependency from 22.0.7 to **23.2.1**
  <br />
  <!-- -->
  ↳ [Redis Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Updated PostgreSQL dependency from 16.7.27 to **18.1.1**
  <br />
  <!-- -->
  ↳ [PostgreSQL Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

See the full changelog in the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.1).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.7.1-released.md)


---

## [actualbudget chart version 1.8.3 released](/blog/actualbudget-chart-version-1.8.3-released.md)

October 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the 🧾 **actualbudget Helm chart (v1.8.3)** is now available, featuring the newly updated **app version 25.10.0**, as of 2025-10-03. This version continues our focus on improving the experience of deploying actualbudget on Kubernetes with enhanced support, better performance, and key community contributions.

## What’s New in actualbudget 1.8.3[​](#whats-new-in-actualbudget-183 "Direct link to What’s New in actualbudget 1.8.3")

This release includes both chart and application updates to keep your deployments modern and efficient:

* ✅ **Updated:** actualbudget/actual-server image upgraded to version 25.10.0
  <br />
  <!-- -->
  ↳ View the [Docker image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For a full list of changes and enhancements, check out the official [v1.8.3 release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.3) on GitHub.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/actualbudget-chart-version-1.8.3-released.md)


---

# pypiserver chart version 0.1.8 released

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of our Helm chart for pypiserver — version 0.1.8 — now available as of August 19, 2025. This release delivers support for app version **v2.4.0**, bringing new features and meaningful improvements to make your Helm-based deployments even more seamless.

<!-- -->

## What’s New in Chart Version 0.1.8[​](#whats-new-in-chart-version-018 "Direct link to What’s New in Chart Version 0.1.8")

The 0.1.8 release updates both the Helm chart and the underlying pypiserver image. Here’s what’s included:

* ✅ Updated underlying image to **pypiserver/pypiserver<!-- -->:v2<!-- -->.4.0**
  * View on [Docker Hub](https://hub.docker.com/r/pypiserver/pypiserver)

Check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/pypiserver-0.1.8) for complete details.

## Getting Started with pypiserver 0.1.8[​](#getting-started-with-pypiserver-018 "Direct link to Getting Started with pypiserver 0.1.8")

Want to try it out? Our detailed [installation guide](https://community-charts.github.io/docs/category/pypiserver) walks you through everything you need:

* Quick-start installation using default values
* How to fine-tune chart values to suit your environment
* Best practices for production deployments

Whether you're running on a local cluster or cloud provider like AWS or Azure, our documentation helps you get started quickly and reliably.

## Why Use the pypiserver Helm Chart?[​](#why-use-the-pypiserver-helm-chart "Direct link to Why Use the pypiserver Helm Chart?")

Maintained by the open-source [GitHub Community Charts](https://github.com/community-charts/helm-charts) project, the pypiserver Helm chart is built to simplify Kubernetes application packaging. Here’s what makes it stand out:

* ⚙️ Easy to install and customize
* 🌍 Backed by a passionate open-source community
* 🔧 Flexible configurations for various use cases
* 🛠️ Tested and stable for Kubernetes environments

With solid community support and active maintenance, this chart delivers a reliable way to manage private Python package repositories on Kubernetes.

## How You Can Contribute[​](#how-you-can-contribute "Direct link to How You Can Contribute")

We’d love to have you join our growing community of contributors! There are many ways to support the project:

* 🔍 Read the [docs](https://community-charts.github.io/docs/category/pypiserver) for usage and configuration tips
* 🧩 Contribute code or improvements to the [GitHub repo](https://github.com/community-charts/helm-charts)
* 🐞 Report bugs and issues [here](https://github.com/community-charts/helm-charts/issues)
* 💡 Submit ideas or request new features via our [issue tracker](https://github.com/community-charts/helm-charts/issues/new)

Thanks for being part of the community — together, we’re building better tools for managing open-source workloads in cloud-native environments.

**Tags:**

* [PyPI Server](/blog/tags/pypiserver.md "Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-08-19-pypiserver-chart-version-0-1-8-released.md)


---

## A[​](#A "Direct link to A")

* [Actual Budget12](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")

***


---

## [actualbudget chart version 1.9.0 released](/blog/actualbudget-chart-version-1.9.0-released.md)

June 20, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **actualbudget Helm chart version 1.9.0** on June 20, 2026, featuring **app version 26.6.0**. This latest update introduces enhanced functionalities and community-driven improvements, making it easier than ever to deploy actualbudget on Kubernetes.

## What's New in actualbudget 1.9.0 chart[​](#whats-new-in-actualbudget-190-chart "Direct link to What's New in actualbudget 1.9.0 chart")

This release includes significant updates to the Helm chart (version 1.9.0) alongside the underlying application (version 26.6.0). Here’s a sneak peek at the changes:

* **Added**: Optional image digest support for immutable image pulls
* **Fixed**: Corrected secret namespace to use the release namespace rather than an undefined value
* **Fixed**: Aligned schema default values with the actual values.yaml defaults
* **Fixed**: Corrected a typo in the supplementalGroups schema title
* **Fixed**: Adjusted the notContains test assertion on scalar fields to use isNull
* **Fixed**: Updated NOTES.txt to reflect configurable service port in port-forward instructions
* **Fixed**: Implemented @deprecated marker convention for the discoverUrl field
* **Fixed**: Enabled readOnlyRootFilesystem and added a built-in tmp emptyDir volume

For a comprehensive list of changes, please take a look at the [release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.9.0) on GitHub.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/actualbudget-chart-version-1.9.0-released.md)


---

## [actualbudget chart version 1.7.1 update now available](/blog/actualbudget-chart-version-1.7.1-released.md)

July 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the **actualbudget Helm chart (v1.7.1)** is now available as of July 2, 2025. This release also includes the updated **application version 25.7.0**, bringing helpful improvements and refinements based on community feedback to enhance your Kubernetes deployment experience.

## What’s New in actualbudget 1.7.1[​](#whats-new-in-actualbudget-171 "Direct link to What’s New in actualbudget 1.7.1")

This release updates both the Helm chart (v1.7.1) and the actualbudget application (v25.7.0). Here’s a summary of the latest changes:

* ✅ **Updated**: Upgraded the container image to actualbudget/actual-server version 25.7.0
  <!-- -->
  * View on [Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For full details, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.7.1).

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/actualbudget-chart-version-1.7.1-released.md)


---

## [mlflow chart version 1.6.1 released](/blog/mlflow-chart-version-1.6.1-released.md)

August 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.6.1**, published on 2025-08-25 and powered by **mlflow app version 3.3.1**. This update introduces several enhancements, improved dependency versions, and continued support from the open-source community to make deploying MLflow on Kubernetes even easier.

## What’s new in version 1.6.1[​](#whats-new-in-version-161 "Direct link to What’s new in version 1.6.1")

This release includes updates to both the Helm chart and its dependencies, ensuring greater reliability and smoother integration for Kubernetes users:

* 🔄 **Image Update**: Upgraded Docker image to `burakince/mlflow:3.3.1`<br /><!-- -->➤ [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)

* ⬆️ **PostgreSQL Dependency**: Upgraded Bitnami PostgreSQL chart from `16.7.21` to `16.7.26`<br /><!-- -->➤ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

* ⬆️ **MySQL Dependency**: Upgraded Bitnami MySQL chart from `14.0.0` to `14.0.3`<br /><!-- -->➤ [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/mysql)

🔗 For the complete list of changes, review the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.6.1).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")
* [CI/CD](/blog/tags/ci-cd.md "Discover expert CI/CD strategies, automation workflows, and top tools for continuous integration and continuous deployment to accelerate your software delivery pipeline.")

[**Read more**](/blog/mlflow-chart-version-1.6.1-released.md)


---

## [mlflow chart version 1.3.1 released](/blog/mlflow-chart-version-1.3.1-released.md)

July 23, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.3.1**, officially available as of **July 23, 2025**. This update includes **mlflow app version 3.1.3**, featuring enhancements, updated dependencies, and meaningful contributions from our open-source community.

## What’s New in mlflow 1.3.1[​](#whats-new-in-mlflow-131 "Direct link to What’s New in mlflow 1.3.1")

Helm chart version 1.3.1 introduces several key improvements and version bumps to support a smoother and more secure deployment experience on Kubernetes:

* 🔄 **App Update**: Upgraded `burakince/mlflow` image to version `3.1.3`
  * [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)
* 📦 **PostgreSQL Update**: Bumped the Bitnami `postgresql` dependency from `16.7.13` to `16.7.21`
  * [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)
* 📦 **MySQL Update**: Upgraded Bitnami `mysql` dependency from `13.0.2` to `14.0.0`
  * [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/mysql)

For a complete breakdown of changes, see the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.1).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")
* [Cloud Databases](/blog/tags/cloud-databases.md "Expert guides and best practices for connecting to managed cloud databases and caches on AWS, Azure, GCP, and other leading cloud providers.")

[**Read more**](/blog/mlflow-chart-version-1.3.1-released.md)


---

## [Cloudflared Chart Version 2.2.10 Released](/blog/cloudflared-chart-version-2.2.10-released.md)

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce the launch of the **cloudflared Helm chart version 2.2.10**, released on 2026-06-19, featuring **app version 2026.6.1**. This update introduces a host of new features, enhancements, and community-driven improvements designed to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.10 Chart[​](#whats-new-in-cloudflared-2210-chart "Direct link to What's New in Cloudflared 2.2.10 Chart")

In this release, we've made updates to both the Helm chart (version 2.2.10) and the underlying application (version 2026.6.1). Here’s a brief overview of the notable changes:

* **Changed**: Updated the cloudflare/cloudflared image version to 2026.6.1.
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a detailed list of all changes, please check the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.10) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.2.10-released.md)


---

## [cloudflared chart version 2.1.1 released](/blog/cloudflared-chart-version-2.1.1-released.md)

August 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the official release of the **cloudflared Helm chart version 2.1.1**, published on **August 8, 2025**, and featuring the latest **application version 2025.8.0**. This update introduces a refreshed container image and builds on community contributions to improve deployment in Kubernetes environments.

## What’s New in cloudflared 2.1.1[​](#whats-new-in-cloudflared-211 "Direct link to What’s New in cloudflared 2.1.1")

Chart version 2.1.1 includes important enhancements to streamline your cloudflared setup. Here’s what’s changed:

* ✅ **Updated Image**: Upgraded to `cloudflare/cloudflared:2025.8.0`
  <br />
  <!-- -->
  🔗 [View on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete list of updates and technical details, check out the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.1) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.1.1-released.md)


---

## [Welcome to Helm Charts - Kubernetes with Community Power](/blog/welcome-to-community-charts.md)

June 15, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're thrilled to announce the launch of the **GitHub Community Charts** website, your go-to resource for community-maintained Helm charts designed to simplify deploying open-source projects on Kubernetes. Our mission is to bridge the gap for projects that lack official or actively maintained Helm charts, ensuring you can easily integrate tools like [MLflow](https://mlflow.org), [n8n](https://n8n.io), and [Actual Budget](https://actualbudget.org) into your Kubernetes clusters.

## Why GitHub Community Charts?[​](#why-github-community-charts "Direct link to Why GitHub Community Charts?")

Many open-source projects lose official Helm chart support when companies shift priorities or discontinue contributions. That's where we step in. At GitHub Community Charts, we maintain and enhance Helm charts for essential tools, keeping them up-to-date, well-documented, and production-ready. Our community-driven approach ensures these charts remain relevant, reliable, and easy to use.

**Tags:**

* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [Community](/blog/tags/community.md "Join a vibrant community where ideas, projects, and support come together to help everyone grow and succeed.")

[**Read more**](/blog/welcome-to-community-charts.md)


---

## [n8n chart version 1.16.14 released](/blog/n8n-chart-version-1.16.14-released.md)

December 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **n8n Helm chart version 1.16.14**, published on December 24, 2025. This latest release includes **application version 2.1.4** and brings several enhancements and updates that improve deploying and managing n8n on Kubernetes.

## Highlights of the n8n 1.16.14 Release[​](#highlights-of-the-n8n-11614-release "Direct link to Highlights of the n8n 1.16.14 Release")

This version introduces key updates to both the Helm chart and the n8n application:

* 🔄 **Updated** n8nio/n8n Docker image to version `2.1.4`
  <br />
  <!-- -->
  → [View upstream repo](https://github.com/n8n-io/n8n)
* 🗃️ **Updated** PostgreSQL chart dependency from `18.1.15` to `18.2.0`
  <br />
  <!-- -->
  → [See ArtifactHub Listing](https://artifacthub.io/packages/helm/bitnami/postgresql)

These updates help ensure greater stability, improved performance, and compatibility with new features.

Check out the complete release changelog on our [GitHub release page](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.14).

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [DevOps](/blog/tags/devops.md "Best practices, strategies, and tips for building, deploying, and managing applications using DevOps tools, automation, and modern CI/CD techniques.")

[**Read more**](/blog/n8n-chart-version-1.16.14-released.md)


---

## [Exciting Release of Drone Chart Version 0.1.5](/blog/drone-chart-version-0.1.5-released.md)

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share that the **drone Helm chart version 0.1.5** is now live as of 2026-05-29, featuring **app version 2.28.2**. This update brings a host of new features, enhancements, and community-driven improvements that make deploying Drone on Kubernetes even more straightforward and efficient.

## What's New in Drone 0.1.5 Chart[​](#whats-new-in-drone-015-chart "Direct link to What's New in Drone 0.1.5 Chart")

This latest release includes updates to both the Helm chart (version 0.1.5) and the underlying application (version 2.28.2). Here’s a quick overview of what’s new:

* **Changed**: Updated to the drone/drone image version 2.28.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/drone/drone)

To see the full list of changes, feel free to check the [release notes](https://github.com/community-charts/helm-charts/releases/tag/drone-0.1.5) on GitHub.

**Tags:**

* [Drone](/blog/tags/drone.md "Build, test, and deploy your code confidently with Drone, a friendly and powerful CI/CD platform for developers.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/drone-chart-version-0.1.5-released.md)


---

## [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md)

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **mlflow Helm chart version 1.11.2** on June 21, 2026, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements to streamline the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.2 chart[​](#whats-new-in-mlflow-1112-chart "Direct link to What's New in mlflow 1.11.2 chart")

This latest version includes important updates to the Helm chart (version 1.11.2) alongside the underlying application (version 3.14.0). Here’s a brief overview of the enhancements:

* **Changed**: Updated dbchecker image version to 1.38.0
  <!-- -->
  * [dbchecker](https://hub.docker.com/r/library/busybox)
* **Changed**: Updated ini-file-initializer image version to 1.38.0
  <!-- -->
  * [ini-file-initializer](https://hub.docker.com/r/library/busybox)

For a comprehensive list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.2) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.11.2-released.md)


---

## [cloudflared chart version 2.1.3 released](/blog/cloudflared-chart-version-2.1.3-released.md)

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest cloudflared Helm chart—version 2.1.3—officially available as of September 18, 2025. This update includes app version 2025.9.0 and brings helpful enhancements designed to simplify your Kubernetes deployments.

## What’s new in cloudflared 2.1.3[​](#whats-new-in-cloudflared-213 "Direct link to What’s new in cloudflared 2.1.3")

Version 2.1.3 focuses on staying up to date with upstream developments and ensuring a smoother deployment experience. Key changes include:

* ✅ Updated container image to cloudflare/cloudflared version 2025.9.0
  <!-- -->
  * [Check the image on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

Review the full changelog in the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.3) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.1.3-released.md)


---

## [Outline Helm Chart 0.6.3 Released with App Version 0.87.1](/blog/outline-chart-version-0.6.3-released.md)

September 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the Outline Helm chart—version 0.6.3—available as of 2025-09-01. This release includes app version 0.87.1 and brings enhancements, updated dependencies, and valuable contributions from the open-source community.

## What’s New in 0.6.3[​](#whats-new-in-063 "Direct link to What’s New in 0.6.3")

This update refreshes both the Outline application and its supporting Helm chart, helping you streamline deployments on Kubernetes.

Here’s what’s included in this version:

* 🔄 Updated to use the latest Outline Docker image (v0.87.1)
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🧠 Redis dependency upgraded from 22.0.1 to 22.0.7
  <br />
  <!-- -->
  → [View Redis Helm Chart](https://artifacthub.io/packages/helm/bitnami/redis)
* 🐘 PostgreSQL dependency updated from 16.7.24 to 16.7.27
  <br />
  <!-- -->
  → [View PostgreSQL Helm Chart](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.3).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.6.3-released.md)


---

## [pypiserver chart version 0.1.8 released](/blog/pypiserver-chart-version-0.1.8-released.md)

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of our Helm chart for pypiserver — version 0.1.8 — now available as of August 19, 2025. This release delivers support for app version **v2.4.0**, bringing new features and meaningful improvements to make your Helm-based deployments even more seamless.

**Tags:**

* [PyPI Server](/blog/tags/pypiserver.md "Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/pypiserver-chart-version-0.1.8-released.md)


---

## [n8n chart version 1.13.8 released](/blog/n8n-chart-version-1.13.8-released.md)

August 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest stable version of the **n8n Helm chart — version 1.13.8**, published on August 4, 2025! This release includes **n8n app version 1.105.2**, with valuable upgrades and refinements to improve your workflow automation experience on Kubernetes.

## What’s new in Helm chart 1.13.8?[​](#whats-new-in-helm-chart-1138 "Direct link to What’s new in Helm chart 1.13.8?")

In this version, both the chart and its dependencies have been refreshed to deliver a more secure and reliable deployment experience.

* ✅ **Updated**: n8n image version is now 1.105.2
  <br />
  <!-- -->
  → Check out the upstream repo: [n8n GitHub](https://github.com/n8n-io/n8n)
* 🔁 **Updated**: Redis dependency upgrade from 21.2.13 to 21.2.14
  <br />
  <!-- -->
  → View it on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For a complete breakdown, see the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.13.8-released.md)


---

## [mlflow chart version 1.3.2 released](/blog/mlflow-chart-version-1.3.2-released.md)

July 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **mlflow Helm chart version 1.3.2** is now available as of **2025-07-24**, bringing you **mlflow app version 3.1.4**. This release delivers usability enhancements and community-driven improvements to make deploying mlflow on Kubernetes even smoother and more efficient.

## What’s New in Helm Chart 1.3.2[​](#whats-new-in-helm-chart-132 "Direct link to What’s New in Helm Chart 1.3.2")

With this release, both the Helm chart and the application itself have been upgraded to offer better functionality and integration:

* 🚀 **Updated**: Container image upgraded to `burakince/mlflow:3.1.4`
  <br />
  <!-- -->
  → View on [Docker Hub](https://hub.docker.com/r/burakince/mlflow)

To see all technical changes, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.2).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.3.2-released.md)


---

## [outline chart version 0.4.1 released](/blog/outline-chart-version-0.4.1-released.md)

July 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm Chart version 0.4.1**, available as of July 4, 2025. This update delivers important improvements and refreshed dependencies to make deploying Outline on your Kubernetes clusters smoother and more efficient.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.4.1-released.md)


---

## [n8n chart version 1.10.0 now available](/blog/n8n-chart-version-1.10.0-released.md)

June 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **n8n Helm chart version 1.10.0**, launched on 2025-06-27 and powered by **application version 1.99.1**. This update introduces new features, usability enhancements, and community-requested improvements that make deploying n8n on Kubernetes easier and more flexible than ever.

## What’s New in Version 1.10.0[​](#whats-new-in-version-1100 "Direct link to What’s New in Version 1.10.0")

This release includes updates to both the Helm chart and the underlying application. Highlights from the changelog include:

* ✅ **Form Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/147)
* ✅ **MCP Server Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/148)
* ✅ **New flag introduced to enable or disable service as needed**

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.10.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.10.0-released.md)


---

## [n8n chart version 1.22.6 released](/blog/n8n-chart-version-1.22.6-released.md)

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the arrival of **n8n Helm chart version 1.22.6** on 2026-06-19, which includes the latest **app version 2.26.7**. This update features a variety of enhancements and community-driven improvements aimed at simplifying the deployment of n8n on Kubernetes.

## What's New in n8n 1.22.6 Chart[​](#whats-new-in-n8n-1226-chart "Direct link to What's New in n8n 1.22.6 Chart")

This release encompasses updates for both the Helm chart (version 1.22.6) and the underlying application (version 2.26.7). Here’s a glimpse into the changes made:

* **Changed**: Updated the n8nio/n8n image version to 2.26.7
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency postgresql from 18.7.5 to 18.7.6
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of the changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.6) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.22.6-released.md)


---

## [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md)

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce that **n8n Helm chart version 1.21.0** has been released as of 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and community-driven improvements designed to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.21.0 chart[​](#whats-new-in-n8n-1210-chart "Direct link to What's New in n8n 1.21.0 chart")

This release brings important updates to both the Helm chart (version 1.21.0) and the underlying application (version 2.23.4). Here are some highlights from the changelog:

* **Added**: Support for extra manifests through `extraManifests` and `extraTemplateManifests` values.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.21.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.21.0-released.md)


---

## [MLflow Chart Version 1.8.5 Released](/blog/mlflow-chart-version-1.8.5-released.md)

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **MLflow Helm chart version 1.8.5** on June 2, 2026, featuring **app version 3.13.0**. This update brings a wealth of new features, enhancements, and community-driven improvements designed to streamline your MLflow deployment on Kubernetes.

## What's New in MLflow 1.8.5 Chart[​](#whats-new-in-mlflow-185-chart "Direct link to What's New in MLflow 1.8.5 Chart")

This release includes updates to both the Helm chart (version 1.8.5) and the underlying application (version 3.13.0). Here are some of the key changes:

* **Fixed**: Resolved broken screenshot URL(s) in the MLflow chart.

For a comprehensive list of changes, you can view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.5) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.5-released.md)


---

## [Cloudflared Chart Version 2.2.8 Released](/blog/cloudflared-chart-version-2.2.8-released.md)

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **cloudflared Helm chart version 2.2.8** on May 29, 2026, featuring **app version 2026.5.2**. This update introduces new features and community-driven enhancements to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.8 Chart[​](#whats-new-in-cloudflared-228-chart "Direct link to What's New in Cloudflared 2.2.8 Chart")

This release not only updates the Helm chart (version 2.2.8) but also the underlying application (version 2026.5.2). Here are the key changes:

* **Changed**: Updated cloudflare/cloudflared image version to 2026.5.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete breakdown of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.8) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.2.8-released.md)


---

## [n8n chart version 1.16.8 released](/blog/n8n-chart-version-1.16.8-released.md)

December 5, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.16.8**, is now available as of December 5, 2025. This release packages **app version 1.122.5** and includes key updates to streamline your workflow automation deployments on Kubernetes.

## What’s New in Version 1.16.8[​](#whats-new-in-version-1168 "Direct link to What’s New in Version 1.16.8")

This update brings improvements to the Helm chart along with the bump to the latest n8n app release. Here's what’s changed:

* 🛠️ **Updated**: n8nio/n8n Docker image upgraded to version 1.122.5
  <br />
  <!-- -->
  → [Upstream Repository](https://github.com/n8n-io/n8n)

Check out the full changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.16.8-released.md)


---

## [mlflow chart version 1.8.0 released](/blog/mlflow-chart-version-1.8.0-released.md)

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.8.0**, available as of 2025-11-08. This release includes the latest **app version 3.6.0** and brings valuable improvements focused on performance, customization, and Kubernetes-native deployments.

## What’s New in mlflow Helm chart 1.8.0[​](#whats-new-in-mlflow-helm-chart-180 "Direct link to What’s New in mlflow Helm chart 1.8.0")

This version of the chart includes important updates designed to offer greater flexibility when running mlflow on Kubernetes. Highlights include:

* ✅ **Resource Configuration for Init Containers**: You can now define compute resources for the `dbchecker` and `ini-file-initializer` init containers.
  <br />
  <!-- -->
  See the discussion on [GitHub Issue #265](https://github.com/community-charts/helm-charts/issues/265)

These changes allow for more efficient use of resources and better alignment with production-grade deployments.

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.0).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.0-released.md)


---

## [Outline chart update 0.7.1 with app version 1.0.0](/blog/outline-chart-version-0.7.1-released.md)

October 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.7.1**, officially available as of October 27, 2025. This latest version includes **app version 1.0.0**, delivering key updates, improved stability, and valuable contributions from our open-source community.

Whether you're running Outline in production or exploring it for the first time, this release brings smoother deployment and better integration with your Kubernetes environment.

## What’s new in version 0.7.1[​](#whats-new-in-version-071 "Direct link to What’s new in version 0.7.1")

This update improves both the Helm chart and important dependencies, aligning with the latest enhancements from upstream projects:

* ✅ Upgraded Outline Docker image to **v1.0.0**
  <br />
  <!-- -->
  ↳ [View upstream image](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Updated Redis dependency from 22.0.7 to **23.2.1**
  <br />
  <!-- -->
  ↳ [Redis Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Updated PostgreSQL dependency from 16.7.27 to **18.1.1**
  <br />
  <!-- -->
  ↳ [PostgreSQL Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

See the full changelog in the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.1).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.7.1-released.md)


---

## [actualbudget chart version 1.8.3 released](/blog/actualbudget-chart-version-1.8.3-released.md)

October 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the 🧾 **actualbudget Helm chart (v1.8.3)** is now available, featuring the newly updated **app version 25.10.0**, as of 2025-10-03. This version continues our focus on improving the experience of deploying actualbudget on Kubernetes with enhanced support, better performance, and key community contributions.

## What’s New in actualbudget 1.8.3[​](#whats-new-in-actualbudget-183 "Direct link to What’s New in actualbudget 1.8.3")

This release includes both chart and application updates to keep your deployments modern and efficient:

* ✅ **Updated:** actualbudget/actual-server image upgraded to version 25.10.0
  <br />
  <!-- -->
  ↳ View the [Docker image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For a full list of changes and enhancements, check out the official [v1.8.3 release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.3) on GitHub.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/actualbudget-chart-version-1.8.3-released.md)


---

## [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md)

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **mlflow Helm chart version 1.11.2** on June 21, 2026, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements to streamline the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.2 chart[​](#whats-new-in-mlflow-1112-chart "Direct link to What's New in mlflow 1.11.2 chart")

This latest version includes important updates to the Helm chart (version 1.11.2) alongside the underlying application (version 3.14.0). Here’s a brief overview of the enhancements:

* **Changed**: Updated dbchecker image version to 1.38.0
  <!-- -->
  * [dbchecker](https://hub.docker.com/r/library/busybox)
* **Changed**: Updated ini-file-initializer image version to 1.38.0
  <!-- -->
  * [ini-file-initializer](https://hub.docker.com/r/library/busybox)

For a comprehensive list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.2) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.11.2-released.md)


---

## [cloudflared chart version 2.1.3 released](/blog/cloudflared-chart-version-2.1.3-released.md)

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest cloudflared Helm chart—version 2.1.3—officially available as of September 18, 2025. This update includes app version 2025.9.0 and brings helpful enhancements designed to simplify your Kubernetes deployments.

## What’s new in cloudflared 2.1.3[​](#whats-new-in-cloudflared-213 "Direct link to What’s new in cloudflared 2.1.3")

Version 2.1.3 focuses on staying up to date with upstream developments and ensuring a smoother deployment experience. Key changes include:

* ✅ Updated container image to cloudflare/cloudflared version 2025.9.0
  <!-- -->
  * [Check the image on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

Review the full changelog in the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.3) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.1.3-released.md)


---

## [Outline Helm Chart 0.6.3 Released with App Version 0.87.1](/blog/outline-chart-version-0.6.3-released.md)

September 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the Outline Helm chart—version 0.6.3—available as of 2025-09-01. This release includes app version 0.87.1 and brings enhancements, updated dependencies, and valuable contributions from the open-source community.

## What’s New in 0.6.3[​](#whats-new-in-063 "Direct link to What’s New in 0.6.3")

This update refreshes both the Outline application and its supporting Helm chart, helping you streamline deployments on Kubernetes.

Here’s what’s included in this version:

* 🔄 Updated to use the latest Outline Docker image (v0.87.1)
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🧠 Redis dependency upgraded from 22.0.1 to 22.0.7
  <br />
  <!-- -->
  → [View Redis Helm Chart](https://artifacthub.io/packages/helm/bitnami/redis)
* 🐘 PostgreSQL dependency updated from 16.7.24 to 16.7.27
  <br />
  <!-- -->
  → [View PostgreSQL Helm Chart](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.3).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.6.3-released.md)


---

## [pypiserver chart version 0.1.8 released](/blog/pypiserver-chart-version-0.1.8-released.md)

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of our Helm chart for pypiserver — version 0.1.8 — now available as of August 19, 2025. This release delivers support for app version **v2.4.0**, bringing new features and meaningful improvements to make your Helm-based deployments even more seamless.

**Tags:**

* [PyPI Server](/blog/tags/pypiserver.md "Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/pypiserver-chart-version-0.1.8-released.md)


---

## [n8n chart version 1.13.8 released](/blog/n8n-chart-version-1.13.8-released.md)

August 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest stable version of the **n8n Helm chart — version 1.13.8**, published on August 4, 2025! This release includes **n8n app version 1.105.2**, with valuable upgrades and refinements to improve your workflow automation experience on Kubernetes.

## What’s new in Helm chart 1.13.8?[​](#whats-new-in-helm-chart-1138 "Direct link to What’s new in Helm chart 1.13.8?")

In this version, both the chart and its dependencies have been refreshed to deliver a more secure and reliable deployment experience.

* ✅ **Updated**: n8n image version is now 1.105.2
  <br />
  <!-- -->
  → Check out the upstream repo: [n8n GitHub](https://github.com/n8n-io/n8n)
* 🔁 **Updated**: Redis dependency upgrade from 21.2.13 to 21.2.14
  <br />
  <!-- -->
  → View it on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For a complete breakdown, see the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.13.8-released.md)


---

## [mlflow chart version 1.3.2 released](/blog/mlflow-chart-version-1.3.2-released.md)

July 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **mlflow Helm chart version 1.3.2** is now available as of **2025-07-24**, bringing you **mlflow app version 3.1.4**. This release delivers usability enhancements and community-driven improvements to make deploying mlflow on Kubernetes even smoother and more efficient.

## What’s New in Helm Chart 1.3.2[​](#whats-new-in-helm-chart-132 "Direct link to What’s New in Helm Chart 1.3.2")

With this release, both the Helm chart and the application itself have been upgraded to offer better functionality and integration:

* 🚀 **Updated**: Container image upgraded to `burakince/mlflow:3.1.4`
  <br />
  <!-- -->
  → View on [Docker Hub](https://hub.docker.com/r/burakince/mlflow)

To see all technical changes, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.2).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.3.2-released.md)


---

## [outline chart version 0.4.1 released](/blog/outline-chart-version-0.4.1-released.md)

July 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm Chart version 0.4.1**, available as of July 4, 2025. This update delivers important improvements and refreshed dependencies to make deploying Outline on your Kubernetes clusters smoother and more efficient.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.4.1-released.md)


---

## [n8n chart version 1.10.0 now available](/blog/n8n-chart-version-1.10.0-released.md)

June 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **n8n Helm chart version 1.10.0**, launched on 2025-06-27 and powered by **application version 1.99.1**. This update introduces new features, usability enhancements, and community-requested improvements that make deploying n8n on Kubernetes easier and more flexible than ever.

## What’s New in Version 1.10.0[​](#whats-new-in-version-1100 "Direct link to What’s New in Version 1.10.0")

This release includes updates to both the Helm chart and the underlying application. Highlights from the changelog include:

* ✅ **Form Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/147)
* ✅ **MCP Server Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/148)
* ✅ **New flag introduced to enable or disable service as needed**

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.10.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.10.0-released.md)


---

## [n8n chart version 1.22.6 released](/blog/n8n-chart-version-1.22.6-released.md)

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the arrival of **n8n Helm chart version 1.22.6** on 2026-06-19, which includes the latest **app version 2.26.7**. This update features a variety of enhancements and community-driven improvements aimed at simplifying the deployment of n8n on Kubernetes.

## What's New in n8n 1.22.6 Chart[​](#whats-new-in-n8n-1226-chart "Direct link to What's New in n8n 1.22.6 Chart")

This release encompasses updates for both the Helm chart (version 1.22.6) and the underlying application (version 2.26.7). Here’s a glimpse into the changes made:

* **Changed**: Updated the n8nio/n8n image version to 2.26.7
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency postgresql from 18.7.5 to 18.7.6
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of the changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.6) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.22.6-released.md)


---

## [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md)

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce that **n8n Helm chart version 1.21.0** has been released as of 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and community-driven improvements designed to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.21.0 chart[​](#whats-new-in-n8n-1210-chart "Direct link to What's New in n8n 1.21.0 chart")

This release brings important updates to both the Helm chart (version 1.21.0) and the underlying application (version 2.23.4). Here are some highlights from the changelog:

* **Added**: Support for extra manifests through `extraManifests` and `extraTemplateManifests` values.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.21.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.21.0-released.md)


---

## [MLflow Chart Version 1.8.5 Released](/blog/mlflow-chart-version-1.8.5-released.md)

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **MLflow Helm chart version 1.8.5** on June 2, 2026, featuring **app version 3.13.0**. This update brings a wealth of new features, enhancements, and community-driven improvements designed to streamline your MLflow deployment on Kubernetes.

## What's New in MLflow 1.8.5 Chart[​](#whats-new-in-mlflow-185-chart "Direct link to What's New in MLflow 1.8.5 Chart")

This release includes updates to both the Helm chart (version 1.8.5) and the underlying application (version 3.13.0). Here are some of the key changes:

* **Fixed**: Resolved broken screenshot URL(s) in the MLflow chart.

For a comprehensive list of changes, you can view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.5) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.5-released.md)


---

## [Cloudflared Chart Version 2.2.8 Released](/blog/cloudflared-chart-version-2.2.8-released.md)

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **cloudflared Helm chart version 2.2.8** on May 29, 2026, featuring **app version 2026.5.2**. This update introduces new features and community-driven enhancements to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.8 Chart[​](#whats-new-in-cloudflared-228-chart "Direct link to What's New in Cloudflared 2.2.8 Chart")

This release not only updates the Helm chart (version 2.2.8) but also the underlying application (version 2026.5.2). Here are the key changes:

* **Changed**: Updated cloudflare/cloudflared image version to 2026.5.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete breakdown of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.8) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.2.8-released.md)


---

## [n8n chart version 1.16.8 released](/blog/n8n-chart-version-1.16.8-released.md)

December 5, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.16.8**, is now available as of December 5, 2025. This release packages **app version 1.122.5** and includes key updates to streamline your workflow automation deployments on Kubernetes.

## What’s New in Version 1.16.8[​](#whats-new-in-version-1168 "Direct link to What’s New in Version 1.16.8")

This update brings improvements to the Helm chart along with the bump to the latest n8n app release. Here's what’s changed:

* 🛠️ **Updated**: n8nio/n8n Docker image upgraded to version 1.122.5
  <br />
  <!-- -->
  → [Upstream Repository](https://github.com/n8n-io/n8n)

Check out the full changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.16.8-released.md)


---

## [mlflow chart version 1.8.0 released](/blog/mlflow-chart-version-1.8.0-released.md)

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.8.0**, available as of 2025-11-08. This release includes the latest **app version 3.6.0** and brings valuable improvements focused on performance, customization, and Kubernetes-native deployments.

## What’s New in mlflow Helm chart 1.8.0[​](#whats-new-in-mlflow-helm-chart-180 "Direct link to What’s New in mlflow Helm chart 1.8.0")

This version of the chart includes important updates designed to offer greater flexibility when running mlflow on Kubernetes. Highlights include:

* ✅ **Resource Configuration for Init Containers**: You can now define compute resources for the `dbchecker` and `ini-file-initializer` init containers.
  <br />
  <!-- -->
  See the discussion on [GitHub Issue #265](https://github.com/community-charts/helm-charts/issues/265)

These changes allow for more efficient use of resources and better alignment with production-grade deployments.

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.0).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.0-released.md)


---

## [Outline chart update 0.7.1 with app version 1.0.0](/blog/outline-chart-version-0.7.1-released.md)

October 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.7.1**, officially available as of October 27, 2025. This latest version includes **app version 1.0.0**, delivering key updates, improved stability, and valuable contributions from our open-source community.

Whether you're running Outline in production or exploring it for the first time, this release brings smoother deployment and better integration with your Kubernetes environment.

## What’s new in version 0.7.1[​](#whats-new-in-version-071 "Direct link to What’s new in version 0.7.1")

This update improves both the Helm chart and important dependencies, aligning with the latest enhancements from upstream projects:

* ✅ Upgraded Outline Docker image to **v1.0.0**
  <br />
  <!-- -->
  ↳ [View upstream image](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Updated Redis dependency from 22.0.7 to **23.2.1**
  <br />
  <!-- -->
  ↳ [Redis Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Updated PostgreSQL dependency from 16.7.27 to **18.1.1**
  <br />
  <!-- -->
  ↳ [PostgreSQL Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

See the full changelog in the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.1).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.7.1-released.md)


---

## [actualbudget chart version 1.8.3 released](/blog/actualbudget-chart-version-1.8.3-released.md)

October 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the 🧾 **actualbudget Helm chart (v1.8.3)** is now available, featuring the newly updated **app version 25.10.0**, as of 2025-10-03. This version continues our focus on improving the experience of deploying actualbudget on Kubernetes with enhanced support, better performance, and key community contributions.

## What’s New in actualbudget 1.8.3[​](#whats-new-in-actualbudget-183 "Direct link to What’s New in actualbudget 1.8.3")

This release includes both chart and application updates to keep your deployments modern and efficient:

* ✅ **Updated:** actualbudget/actual-server image upgraded to version 25.10.0
  <br />
  <!-- -->
  ↳ View the [Docker image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For a full list of changes and enhancements, check out the official [v1.8.3 release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.3) on GitHub.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/actualbudget-chart-version-1.8.3-released.md)


---

## [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md)

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **mlflow Helm chart version 1.11.2** on June 21, 2026, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements to streamline the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.2 chart[​](#whats-new-in-mlflow-1112-chart "Direct link to What's New in mlflow 1.11.2 chart")

This latest version includes important updates to the Helm chart (version 1.11.2) alongside the underlying application (version 3.14.0). Here’s a brief overview of the enhancements:

* **Changed**: Updated dbchecker image version to 1.38.0
  <!-- -->
  * [dbchecker](https://hub.docker.com/r/library/busybox)
* **Changed**: Updated ini-file-initializer image version to 1.38.0
  <!-- -->
  * [ini-file-initializer](https://hub.docker.com/r/library/busybox)

For a comprehensive list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.2) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.11.2-released.md)


---

## [mlflow chart version 1.8.1 released](/blog/mlflow-chart-version-1.8.1-released.md)

December 7, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **mlflow Helm chart version 1.8.1**, now available as of 2025-12-07. This version includes support for **mlflow application version 3.7.0** and brings helpful improvements and upgrades to the chart—making your deployments on Kubernetes even smoother.

## What’s New in mlflow 1.8.1[​](#whats-new-in-mlflow-181 "Direct link to What’s New in mlflow 1.8.1")

The 1.8.1 update includes key changes to both the Helm chart and its dependencies:

* 🛠️ **Updated**: Upgraded Docker image to `burakince/mlflow:3.7.0`
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/burakince/mlflow)
* 🏗️ **Updated**: Bumped PostgreSQL chart dependency from `18.1.7` to `18.1.13`
  <br />
  <!-- -->
  → [View on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of updates and enhancements, check out the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.1) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.1-released.md)


---

## [mlflow chart version 1.6.0 released](/blog/mlflow-chart-version-1.6.0-released.md)

August 25, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the mlflow Helm chart — version 1.6.0 — available as of August 25, 2025. This release includes the updated mlflow application version 3.2.0 and brings a variety of improvements designed to make your Kubernetes deployments more seamless and secure.

## What’s new in mlflow chart 1.6.0[​](#whats-new-in-mlflow-chart-160 "Direct link to What’s new in mlflow chart 1.6.0")

Version 1.6.0 introduces several key changes and fixes thanks to contributions from our vibrant open-source community. Highlights include:

* 🔁 Auth and LDAP Auth external secret loading now handled via init containers

  * Addresses: [Issue #200](https://github.com/community-charts/helm-charts/issues/200), [Issue #217](https://github.com/community-charts/helm-charts/issues/217)

* 🔒 Improved security handling by removing empty security context definitions

  * Fixes: [Issue #219](https://github.com/community-charts/helm-charts/issues/219)

For the full list of updates and technical details, check out the official [mlflow 1.6.0 release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.6.0) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.6.0-released.md)


---

## [n8n chart version 1.23.1 released](/blog/n8n-chart-version-1.23.1-released.md)

June 19, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **n8n Helm chart version 1.23.1** on June 19, 2026, featuring **app version 2.26.8**. This update introduces new features, enhancements, and valuable community-driven improvements to streamline the deployment of n8n on Kubernetes.

## What's New in the n8n 1.23.1 chart[​](#whats-new-in-the-n8n-1231-chart "Direct link to What's New in the n8n 1.23.1 chart")

The latest release includes updates to both the Helm chart (version 1.23.1) and the underlying application (version 2.26.8). Here’s a summary of what’s new:

* **Changed**: Updated the n8nio/n8n image version to 2.26.8
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Fixed**: Resolved broken screenshot URL(s) in the n8n chart

For a comprehensive list of changes, please view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.23.1) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.23.1-released.md)


---

## [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md)

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce that **n8n Helm chart version 1.21.0** has been released as of 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and community-driven improvements designed to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.21.0 chart[​](#whats-new-in-n8n-1210-chart "Direct link to What's New in n8n 1.21.0 chart")

This release brings important updates to both the Helm chart (version 1.21.0) and the underlying application (version 2.23.4). Here are some highlights from the changelog:

* **Added**: Support for extra manifests through `extraManifests` and `extraTemplateManifests` values.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.21.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.21.0-released.md)


---

## [n8n chart version 1.16.45 released](/blog/n8n-chart-version-1.16.45-released.md)

June 2, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share that the **n8n Helm chart version 1.16.45** has been officially released as of June 2, 2026, featuring **app version 2.22.6**. This latest update introduces a host of new features, enhancements, and community-driven improvements designed to streamline the deployment of n8n on Kubernetes.

## What's New in n8n 1.16.45 chart[​](#whats-new-in-n8n-11645-chart "Direct link to What's New in n8n 1.16.45 chart")

The release of the n8n chart version 1.16.45 includes notable updates to the Helm chart alongside the underlying application version 2.22.6. Here’s a brief overview of the key changes:

* **Changed**: Updated the n8nio/n8n image version to 2.22.6
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Upgraded the PostgreSQL dependency from version 18.6.8 to 18.7.0
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For more detailed information, please check out the complete [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.45) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.16.45-released.md)


---

## [n8n chart version 1.16.5 released](/blog/n8n-chart-version-1.16.5-released.md)

November 26, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the **n8n Helm chart (v1.16.5)** is now available as of 2025-11-26. This release includes **n8n application version 1.121.2**, bringing valuable updates, dependency upgrades, and community-backed enhancements to improve your deployment experience on Kubernetes.

## What’s New in n8n Chart v1.16.5[​](#whats-new-in-n8n-chart-v1165 "Direct link to What’s New in n8n Chart v1.16.5")

Here’s a quick look at what’s included in this release:

* 📦 **App Update**: Upgraded to n8n version 1.121.2
  <br />
  <!-- -->
  ➤ [View the upstream project](https://github.com/n8n-io/n8n)
* 🔧 **Redis Helm Chart Updated**: From version 23.2.12 to 24.0.0
  <br />
  <!-- -->
  ➤ [Bitnami Redis on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🗃️ **PostgreSQL Helm Chart Updated**: From version 18.1.10 to 18.1.13
  <br />
  <!-- -->
  ➤ [Bitnami PostgreSQL on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For the full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.5).

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.16.5-released.md)


---

## [n8n chart version 1.15.16 released](/blog/n8n-chart-version-1.15.16-released.md)

October 15, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the **n8n Helm chart version 1.15.16** is now available, featuring **application version 1.115.3**. This release comes with meaningful improvements and important updates to make deploying n8n on Kubernetes even more seamless and scalable.

## What’s new in n8n chart 1.15.16[​](#whats-new-in-n8n-chart-11516 "Direct link to What’s new in n8n chart 1.15.16")

This release includes updates to both the Helm chart (v1.15.16) and the n8n application (v1.115.3). Here’s what’s changed:

* 🔄 **Application Version Upgrade**: Updated to n8nio/n8n image version 1.115.3
  <br />
  <!-- -->
  → [View on GitHub](https://github.com/n8n-io/n8n)
* 🔧 **Dependency Update**: Upgraded PostgreSQL from version 18.0.14 to 18.0.15
  <br />
  <!-- -->
  → [View on Artifact Hub](https://artifacthub.io/packages/helm/bitnami/postgresql)

Check out the full details in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.16) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.15.16-released.md)


---

## [n8n chart version 1.15.6 released](/blog/n8n-chart-version-1.15.6-released.md)

September 16, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **n8n Helm chart version 1.15.6** is now available as of 2025-09-16, featuring **app version 1.111.0**. This release includes fresh updates and enhancements that streamline your automation workflows on Kubernetes.

## What’s New in 1.15.6[​](#whats-new-in-1156 "Direct link to What’s New in 1.15.6")

This chart update brings you the latest improvements from the n8n community and upstream maintainers:

* ⬆️ **Upgraded**: n8nio/n8n Docker image to version 1.111.0
  <br />
  <!-- -->
  ↳ See the [n8n upstream project](https://github.com/n8n-io/n8n)

For the complete changelog, view the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.15.6) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.15.6-released.md)


---

## [n8n chart version 1.14.0 released](/blog/n8n-chart-version-1.14.0-released.md)

August 11, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart—**v1.14.0**—is now available as of 2025-08-11, featuring **app version 1.105.4**. This release delivers valuable enhancements and community-driven fixes to streamline your n8n deployments on Kubernetes.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.14.0-released.md)


---

## [n8n chart 1.13.0 update is here](/blog/n8n-chart-version-1.13.0-released.md)

July 6, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the n8n Helm chart — **version 1.13.0**, published on July 6, 2025! While the app version is currently undefined, this update introduces several valuable improvements that enhance the experience of deploying n8n on Kubernetes.

## What’s new in version 1.13.0[​](#whats-new-in-version-1130 "Direct link to What’s new in version 1.13.0")

The Helm chart (v1.13.0) includes multiple additions, fixes, and enhancements based on community feedback. Here's a quick overview of the highlights:

* ✅ **Fixed:** Resolved an issue with MCP connections handling multiple webhooks<br /><!-- -->→ [View GitHub Issue](https://github.com/community-charts/helm-charts/issues/165)

* 🆕 **Added:** New field for defining service labels

* 🆕 **Added:** Option to enable or disable MCP Webhooks

* 🔁 **Changed:** Main pod labels now use main.name and main.fullname for better consistency

* 🆕 **Added:** Configurable runtimeClassName for main, worker, and webhook pods

Find the complete list and technical details in our official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.0).

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.13.0-released.md)


---

## [n8n chart version 1.8.6 released](/blog/n8n-chart-version-1.8.6-released.md)

June 22, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are thrilled to announce the release of the **n8n Helm chart version 1.8.6** on 2025-06-22, featuring **app version 1.98.2**. This update brings new features, enhancements, and community-driven improvements to simplify deploying n8n on Kubernetes.

## What's New in n8n 1.8.6 chart[​](#whats-new-in-n8n-186-chart "Direct link to What's New in n8n 1.8.6 chart")

This release includes updates to the Helm chart (version 1.8.6) and the underlying application (version 1.98.2). Below is the detailed changelog:

* **Fixed**: Fix npm registry secret volume mount when only npmRegistry.enabled is true
  <!-- -->
  * [Github PR](https://github.com/community-charts/helm-charts/pull/135)

For a complete list of changes, view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.8.6) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.8.6-released.md)


---

## [mlflow chart version 1.11.2 released](/blog/mlflow-chart-version-1.11.2-released.md)

June 21, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the **mlflow Helm chart version 1.11.2** on June 21, 2026, featuring **app version 3.14.0**. This update introduces new features, enhancements, and community-driven improvements to streamline the deployment of mlflow on Kubernetes.

## What's New in mlflow 1.11.2 chart[​](#whats-new-in-mlflow-1112-chart "Direct link to What's New in mlflow 1.11.2 chart")

This latest version includes important updates to the Helm chart (version 1.11.2) alongside the underlying application (version 3.14.0). Here’s a brief overview of the enhancements:

* **Changed**: Updated dbchecker image version to 1.38.0
  <!-- -->
  * [dbchecker](https://hub.docker.com/r/library/busybox)
* **Changed**: Updated ini-file-initializer image version to 1.38.0
  <!-- -->
  * [ini-file-initializer](https://hub.docker.com/r/library/busybox)

For a comprehensive list of changes, feel free to check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.11.2) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.11.2-released.md)


---

## [cloudflared chart version 2.1.3 released](/blog/cloudflared-chart-version-2.1.3-released.md)

September 18, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share the release of the latest cloudflared Helm chart—version 2.1.3—officially available as of September 18, 2025. This update includes app version 2025.9.0 and brings helpful enhancements designed to simplify your Kubernetes deployments.

## What’s new in cloudflared 2.1.3[​](#whats-new-in-cloudflared-213 "Direct link to What’s new in cloudflared 2.1.3")

Version 2.1.3 focuses on staying up to date with upstream developments and ensuring a smoother deployment experience. Key changes include:

* ✅ Updated container image to cloudflare/cloudflared version 2025.9.0
  <!-- -->
  * [Check the image on Docker Hub](https://hub.docker.com/r/cloudflare/cloudflared)

Review the full changelog in the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.1.3) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.1.3-released.md)


---

## [Outline Helm Chart 0.6.3 Released with App Version 0.87.1](/blog/outline-chart-version-0.6.3-released.md)

September 1, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of the Outline Helm chart—version 0.6.3—available as of 2025-09-01. This release includes app version 0.87.1 and brings enhancements, updated dependencies, and valuable contributions from the open-source community.

## What’s New in 0.6.3[​](#whats-new-in-063 "Direct link to What’s New in 0.6.3")

This update refreshes both the Outline application and its supporting Helm chart, helping you streamline deployments on Kubernetes.

Here’s what’s included in this version:

* 🔄 Updated to use the latest Outline Docker image (v0.87.1)
  <br />
  <!-- -->
  → [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)
* 🧠 Redis dependency upgraded from 22.0.1 to 22.0.7
  <br />
  <!-- -->
  → [View Redis Helm Chart](https://artifacthub.io/packages/helm/bitnami/redis)
* 🐘 PostgreSQL dependency updated from 16.7.24 to 16.7.27
  <br />
  <!-- -->
  → [View PostgreSQL Helm Chart](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a full list of changes, check out the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.3).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.6.3-released.md)


---

## [pypiserver chart version 0.1.8 released](/blog/pypiserver-chart-version-0.1.8-released.md)

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of our Helm chart for pypiserver — version 0.1.8 — now available as of August 19, 2025. This release delivers support for app version **v2.4.0**, bringing new features and meaningful improvements to make your Helm-based deployments even more seamless.

**Tags:**

* [PyPI Server](/blog/tags/pypiserver.md "Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/pypiserver-chart-version-0.1.8-released.md)


---

## [n8n chart version 1.13.8 released](/blog/n8n-chart-version-1.13.8-released.md)

August 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest stable version of the **n8n Helm chart — version 1.13.8**, published on August 4, 2025! This release includes **n8n app version 1.105.2**, with valuable upgrades and refinements to improve your workflow automation experience on Kubernetes.

## What’s new in Helm chart 1.13.8?[​](#whats-new-in-helm-chart-1138 "Direct link to What’s new in Helm chart 1.13.8?")

In this version, both the chart and its dependencies have been refreshed to deliver a more secure and reliable deployment experience.

* ✅ **Updated**: n8n image version is now 1.105.2
  <br />
  <!-- -->
  → Check out the upstream repo: [n8n GitHub](https://github.com/n8n-io/n8n)
* 🔁 **Updated**: Redis dependency upgrade from 21.2.13 to 21.2.14
  <br />
  <!-- -->
  → View it on [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

For a complete breakdown, see the full [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.13.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.13.8-released.md)


---

## [mlflow chart version 1.3.2 released](/blog/mlflow-chart-version-1.3.2-released.md)

July 24, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're excited to share that the **mlflow Helm chart version 1.3.2** is now available as of **2025-07-24**, bringing you **mlflow app version 3.1.4**. This release delivers usability enhancements and community-driven improvements to make deploying mlflow on Kubernetes even smoother and more efficient.

## What’s New in Helm Chart 1.3.2[​](#whats-new-in-helm-chart-132 "Direct link to What’s New in Helm Chart 1.3.2")

With this release, both the Helm chart and the application itself have been upgraded to offer better functionality and integration:

* 🚀 **Updated**: Container image upgraded to `burakince/mlflow:3.1.4`
  <br />
  <!-- -->
  → View on [Docker Hub](https://hub.docker.com/r/burakince/mlflow)

To see all technical changes, check out the full [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.3.2).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.3.2-released.md)


---

## [outline chart version 0.4.1 released](/blog/outline-chart-version-0.4.1-released.md)

July 4, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm Chart version 0.4.1**, available as of July 4, 2025. This update delivers important improvements and refreshed dependencies to make deploying Outline on your Kubernetes clusters smoother and more efficient.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.4.1-released.md)


---

## [n8n chart version 1.10.0 now available](/blog/n8n-chart-version-1.10.0-released.md)

June 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest **n8n Helm chart version 1.10.0**, launched on 2025-06-27 and powered by **application version 1.99.1**. This update introduces new features, usability enhancements, and community-requested improvements that make deploying n8n on Kubernetes easier and more flexible than ever.

## What’s New in Version 1.10.0[​](#whats-new-in-version-1100 "Direct link to What’s New in Version 1.10.0")

This release includes updates to both the Helm chart and the underlying application. Highlights from the changelog include:

* ✅ **Form Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/147)
* ✅ **MCP Server Trigger paths added to ingress configuration**
  <br />
  [View Pull Request](https://github.com/community-charts/helm-charts/pull/148)
* ✅ **New flag introduced to enable or disable service as needed**

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.10.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.10.0-released.md)


---

## [n8n chart version 1.22.6 released](/blog/n8n-chart-version-1.22.6-released.md)

June 19, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the arrival of **n8n Helm chart version 1.22.6** on 2026-06-19, which includes the latest **app version 2.26.7**. This update features a variety of enhancements and community-driven improvements aimed at simplifying the deployment of n8n on Kubernetes.

## What's New in n8n 1.22.6 Chart[​](#whats-new-in-n8n-1226-chart "Direct link to What's New in n8n 1.22.6 Chart")

This release encompasses updates for both the Helm chart (version 1.22.6) and the underlying application (version 2.26.7). Here’s a glimpse into the changes made:

* **Changed**: Updated the n8nio/n8n image version to 2.26.7
  <!-- -->
  * [Upstream Project](https://github.com/n8n-io/n8n)
* **Changed**: Updated dependency postgresql from 18.7.5 to 18.7.6
  <!-- -->
  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a comprehensive list of the changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.22.6) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.22.6-released.md)


---

## [n8n chart version 1.21.0 released](/blog/n8n-chart-version-1.21.0-released.md)

June 7, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to announce that **n8n Helm chart version 1.21.0** has been released as of 2026-06-07, featuring **app version 2.23.4**. This update introduces new features, enhancements, and community-driven improvements designed to streamline your deployment of n8n on Kubernetes.

## What's New in n8n 1.21.0 chart[​](#whats-new-in-n8n-1210-chart "Direct link to What's New in n8n 1.21.0 chart")

This release brings important updates to both the Helm chart (version 1.21.0) and the underlying application (version 2.23.4). Here are some highlights from the changelog:

* **Added**: Support for extra manifests through `extraManifests` and `extraTemplateManifests` values.

For a comprehensive list of changes, please check out the [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.21.0) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.21.0-released.md)


---

## [MLflow Chart Version 1.8.5 Released](/blog/mlflow-chart-version-1.8.5-released.md)

June 2, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the launch of the **MLflow Helm chart version 1.8.5** on June 2, 2026, featuring **app version 3.13.0**. This update brings a wealth of new features, enhancements, and community-driven improvements designed to streamline your MLflow deployment on Kubernetes.

## What's New in MLflow 1.8.5 Chart[​](#whats-new-in-mlflow-185-chart "Direct link to What's New in MLflow 1.8.5 Chart")

This release includes updates to both the Helm chart (version 1.8.5) and the underlying application (version 3.13.0). Here are some of the key changes:

* **Fixed**: Resolved broken screenshot URL(s) in the MLflow chart.

For a comprehensive list of changes, you can view the [release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.5) on GitHub.

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.5-released.md)


---

## [Cloudflared Chart Version 2.2.8 Released](/blog/cloudflared-chart-version-2.2.8-released.md)

May 29, 2026 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **cloudflared Helm chart version 2.2.8** on May 29, 2026, featuring **app version 2026.5.2**. This update introduces new features and community-driven enhancements to streamline the deployment of cloudflared on Kubernetes.

## What's New in Cloudflared 2.2.8 Chart[​](#whats-new-in-cloudflared-228-chart "Direct link to What's New in Cloudflared 2.2.8 Chart")

This release not only updates the Helm chart (version 2.2.8) but also the underlying application (version 2026.5.2). Here are the key changes:

* **Changed**: Updated cloudflare/cloudflared image version to 2026.5.2
  <!-- -->
  * [Upstream Project](https://hub.docker.com/r/cloudflare/cloudflared)

For a complete breakdown of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/cloudflared-2.2.8) on GitHub.

**Tags:**

* [Cloudflared](/blog/tags/cloudflared.md "Securely connect your infrastructure to Cloudflare with Cloudflared, making tunnels and integrations a breeze.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/cloudflared-chart-version-2.2.8-released.md)


---

## [n8n chart version 1.16.8 released](/blog/n8n-chart-version-1.16.8-released.md)

December 5, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest version of the n8n Helm chart, **v1.16.8**, is now available as of December 5, 2025. This release packages **app version 1.122.5** and includes key updates to streamline your workflow automation deployments on Kubernetes.

## What’s New in Version 1.16.8[​](#whats-new-in-version-1168 "Direct link to What’s New in Version 1.16.8")

This update brings improvements to the Helm chart along with the bump to the latest n8n app release. Here's what’s changed:

* 🛠️ **Updated**: n8nio/n8n Docker image upgraded to version 1.122.5
  <br />
  <!-- -->
  → [Upstream Repository](https://github.com/n8n-io/n8n)

Check out the full changelog in the official [release notes](https://github.com/community-charts/helm-charts/releases/tag/n8n-1.16.8) on GitHub.

**Tags:**

* [n8n](/blog/tags/n8n.md "Automate your workflows with n8n, the flexible tool that connects your favorite apps and services with ease.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/n8n-chart-version-1.16.8-released.md)


---

## [mlflow chart version 1.8.0 released](/blog/mlflow-chart-version-1.8.0-released.md)

November 8, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **mlflow Helm chart version 1.8.0**, available as of 2025-11-08. This release includes the latest **app version 3.6.0** and brings valuable improvements focused on performance, customization, and Kubernetes-native deployments.

## What’s New in mlflow Helm chart 1.8.0[​](#whats-new-in-mlflow-helm-chart-180 "Direct link to What’s New in mlflow Helm chart 1.8.0")

This version of the chart includes important updates designed to offer greater flexibility when running mlflow on Kubernetes. Highlights include:

* ✅ **Resource Configuration for Init Containers**: You can now define compute resources for the `dbchecker` and `ini-file-initializer` init containers.
  <br />
  <!-- -->
  See the discussion on [GitHub Issue #265](https://github.com/community-charts/helm-charts/issues/265)

These changes allow for more efficient use of resources and better alignment with production-grade deployments.

Explore the full changelog in the [official release notes](https://github.com/community-charts/helm-charts/releases/tag/mlflow-1.8.0).

**Tags:**

* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/mlflow-chart-version-1.8.0-released.md)


---

## [Outline chart update 0.7.1 with app version 1.0.0](/blog/outline-chart-version-0.7.1-released.md)

October 27, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.7.1**, officially available as of October 27, 2025. This latest version includes **app version 1.0.0**, delivering key updates, improved stability, and valuable contributions from our open-source community.

Whether you're running Outline in production or exploring it for the first time, this release brings smoother deployment and better integration with your Kubernetes environment.

## What’s new in version 0.7.1[​](#whats-new-in-version-071 "Direct link to What’s new in version 0.7.1")

This update improves both the Helm chart and important dependencies, aligning with the latest enhancements from upstream projects:

* ✅ Upgraded Outline Docker image to **v1.0.0**
  <br />
  <!-- -->
  ↳ [View upstream image](https://hub.docker.com/r/outlinewiki/outline)
* 🔄 Updated Redis dependency from 22.0.7 to **23.2.1**
  <br />
  <!-- -->
  ↳ [Redis Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)
* 🔄 Updated PostgreSQL dependency from 16.7.27 to **18.1.1**
  <br />
  <!-- -->
  ↳ [PostgreSQL Helm chart on ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

See the full changelog in the [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.7.1).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.7.1-released.md)


---

## [actualbudget chart version 1.8.3 released](/blog/actualbudget-chart-version-1.8.3-released.md)

October 3, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to share that the latest release of the 🧾 **actualbudget Helm chart (v1.8.3)** is now available, featuring the newly updated **app version 25.10.0**, as of 2025-10-03. This version continues our focus on improving the experience of deploying actualbudget on Kubernetes with enhanced support, better performance, and key community contributions.

## What’s New in actualbudget 1.8.3[​](#whats-new-in-actualbudget-183 "Direct link to What’s New in actualbudget 1.8.3")

This release includes both chart and application updates to keep your deployments modern and efficient:

* ✅ **Updated:** actualbudget/actual-server image upgraded to version 25.10.0
  <br />
  <!-- -->
  ↳ View the [Docker image on Docker Hub](https://hub.docker.com/r/actualbudget/actual-server)

For a full list of changes and enhancements, check out the official [v1.8.3 release notes](https://github.com/community-charts/helm-charts/releases/tag/actualbudget-1.8.3) on GitHub.

**Tags:**

* [Actual Budget](/blog/tags/actual-budget.md "Take control of your finances with Actual Budget, an open-source app designed for privacy and simple, effective budgeting.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/actualbudget-chart-version-1.8.3-released.md)


---

## [outline chart version 0.9.0 released](/blog/outline-chart-version-0.9.0-released.md)

June 20, 2026 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We are excited to share the release of the **outline Helm chart version 0.9.0** on June 20, 2026, featuring **app version 1.8.1**. This latest update introduces a host of new features, enhancements, and community-driven improvements, all aimed at making your deployment of outline on Kubernetes more seamless.

## What's New in outline 0.9.0 chart[​](#whats-new-in-outline-090-chart "Direct link to What's New in outline 0.9.0 chart")

This version includes important updates to both the Helm chart (version 0.9.0) and the underlying application (version 1.8.1). Check out the detailed changelog below:

* **Added**: Optional image digest support for immutable image pulls.

* **Fixed**: Enabled readOnlyRootFilesystem and added a built-in tmp emptyDir volume.

* **Changed**: Updated outlinewiki/outline image version to 1.8.1

  * [Upstream Project](https://hub.docker.com/r/outlinewiki/outline)

* **Changed**: Upgraded dependency redis from version 25.5.3 to 27.0.4

  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/redis)

* **Changed**: Updated dependency postgresql from version 18.7.0 to 18.7.2

  * [ArtifactHub](https://artifacthub.io/packages/helm/bitnami/postgresql)

For a complete list of changes, please refer to the [release notes](https://github.com/community-charts/helm-charts/releases/tag/outline-0.9.0) on GitHub.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.9.0-released.md)


---

## [Outline chart update 0.6.4 now available](/blog/outline-chart-version-0.6.4-released.md)

September 2, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.6.4** as of September 2, 2025, featuring the latest **application version 0.87.3**. This release brings key improvements, enhanced stability, and contributions from our vibrant community—making it even easier to deploy Outline in your Kubernetes environment.

## What’s new in version 0.6.4[​](#whats-new-in-version-064 "Direct link to What’s new in version 0.6.4")

This release includes updates to both the Helm chart (v0.6.4) and the Outline application (v0.87.3). Here’s a quick look at what’s changed:

* ✅ Updated: Switched to outlinewiki/outline Docker image version 0.87.3
  <br />
  <!-- -->
  👉 [View on Docker Hub](https://hub.docker.com/r/outlinewiki/outline)

Check out the full list of changes in the official [release notes on GitHub](https://github.com/community-charts/helm-charts/releases/tag/outline-0.6.4).

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.6.4-released.md)


---

## [Outline chart 0.4.0 brings powerful enhancements](/blog/outline-chart-version-0.4.0-released.md)

July 3, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the **Outline Helm chart version 0.4.0**, now available as of July 3, 2025. This release includes major improvements and expanded functionality that make deploying Outline on Kubernetes even more seamless and secure.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/outline-chart-version-0.4.0-released.md)


---

## [Outline chart 0.7.2 includes app version 1.0.1 with Redis and Postgres updates](/blog/outline-chart-version-0.7.2-released.md)

October 30, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to introduce the release of the **Outline Helm chart version 0.7.2**, published on October 30, 2025. This release includes support for **Outline application version 1.0.1** and brings important updates to chart dependencies—making it easier than ever to run and scale Outline on Kubernetes.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [Redis](/blog/tags/redis.md "Configure your applications with Redis for caching, queueing, and real-time data, including managed Redis on major cloud providers.")
* [Postgres](/blog/tags/postgres.md "Learn how to configure applications with PostgreSQL for reliable data storage, including guides for managed PostgreSQL on AWS, Google Cloud, and Azure.")

[**Read more**](/blog/outline-chart-version-0.7.2-released.md)


---

## [pypiserver chart version 0.1.8 released](/blog/pypiserver-chart-version-0.1.8-released.md)

August 19, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to announce the release of the latest version of our Helm chart for pypiserver — version 0.1.8 — now available as of August 19, 2025. This release delivers support for app version **v2.4.0**, bringing new features and meaningful improvements to make your Helm-based deployments even more seamless.

**Tags:**

* [PyPI Server](/blog/tags/pypiserver.md "Host and share your Python packages privately and simply with PyPI Server, your lightweight package index solution.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")

[**Read more**](/blog/pypiserver-chart-version-0.1.8-released.md)


---

## [Outline chart 0.7.2 includes app version 1.0.1 with Redis and Postgres updates](/blog/outline-chart-version-0.7.2-released.md)

October 30, 2025 ·

<!-- -->

2 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We’re excited to introduce the release of the **Outline Helm chart version 0.7.2**, published on October 30, 2025. This release includes support for **Outline application version 1.0.1** and brings important updates to chart dependencies—making it easier than ever to run and scale Outline on Kubernetes.

**Tags:**

* [Outline](/blog/tags/outline.md "Collaborate and organize your team's knowledge with Outline, a modern and intuitive wiki for everyone.")
* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [Redis](/blog/tags/redis.md "Configure your applications with Redis for caching, queueing, and real-time data, including managed Redis on major cloud providers.")
* [Postgres](/blog/tags/postgres.md "Learn how to configure applications with PostgreSQL for reliable data storage, including guides for managed PostgreSQL on AWS, Google Cloud, and Azure.")

[**Read more**](/blog/outline-chart-version-0.7.2-released.md)


---

# Welcome to Helm Charts - Kubernetes with Community Power

June 15, 2025 ·

<!-- -->

3 min read

[![Burak Ince](https://github.com/burakince.png)](/blog/authors/burakince.md)

[Burak Ince](/blog/authors/burakince.md)

Software Developer

[](https://x.com/burakinc "X")[](https://twitter.com/burakinc "Twitter")[](https://bsky.app/profile/burakince.bsky.social "Bluesky")[](https://www.linkedin.com/in/inceburak/ "LinkedIn")[](https://github.com/burakince "GitHub")[](https://www.burakince.com "newsletter")[](https://keybase.io/burakince "keybase")[](https://huggingface.co/burakince "huggingface")

We're thrilled to announce the launch of the **GitHub Community Charts** website, your go-to resource for community-maintained Helm charts designed to simplify deploying open-source projects on Kubernetes. Our mission is to bridge the gap for projects that lack official or actively maintained Helm charts, ensuring you can easily integrate tools like [MLflow](https://mlflow.org), [n8n](https://n8n.io), and [Actual Budget](https://actualbudget.org) into your Kubernetes clusters.

## Why GitHub Community Charts?[​](#why-github-community-charts "Direct link to Why GitHub Community Charts?")

Many open-source projects lose official Helm chart support when companies shift priorities or discontinue contributions. That's where we step in. At GitHub Community Charts, we maintain and enhance Helm charts for essential tools, keeping them up-to-date, well-documented, and production-ready. Our community-driven approach ensures these charts remain relevant, reliable, and easy to use.

<!-- -->

### Featured Chart: MLflow[​](#featured-chart-mlflow "Direct link to Featured Chart: MLflow")

One of our flagship offerings is the [MLflow Helm chart](/docs/category/mlflow.md), which enables seamless deployment of [MLflow](https://mlflow.org), an open-source platform for managing the machine learning lifecycle. Whether you're tracking experiments, managing models, or deploying ML pipelines, our chart supports:

* **Multiple Backends**: PostgreSQL, MySQL, or SQLite for flexible storage.
* **Cloud Integration**: AWS S3, Azure Blob Storage, and Google Cloud Storage for artifacts.
* **Authentication**: Basic auth, LDAP, or centralized PostgreSQL for secure access.
* **Autoscaling**: Horizontal Pod Autoscaling (HPA) for production workloads.

Check out our [MLflow documentation](/docs/category/mlflow.md) for step-by-step guides on [basic installation](/docs/charts/mlflow/basic-installation.md), [PostgreSQL setup](/docs/charts/mlflow/postgresql-backend-installation.md), [AWS S3 integration](/docs/charts/mlflow/aws-s3-integration.md), and more.

## Our Current Chart Lineup[​](#our-current-chart-lineup "Direct link to Our Current Chart Lineup")

We currently support the following Helm charts, each crafted to meet the needs of diverse use cases:

* **MLflow**: Manage your machine learning workflows with ease.
* **n8n**: Automate tasks and integrate apps with a no-code/low-code platform.
* **Actual Budget**: Track personal finances securely in a self-hosted environment.
* **Cloudflared**: Securely connect to your Kubernetes services with Cloudflare tunnels.
* **Drone**: Set up continuous integration and deployment pipelines.
* **Outline**: Collaborate on knowledge bases with a modern wiki solution.
* **Pypiserver**: Host your own Python package repository.

Explore all our charts in the [Charts section](/docs/category/charts.md) and let us know which projects you'd like us to support next!

## Get Involved[​](#get-involved "Direct link to Get Involved")

GitHub Community Charts is built by the community, for the community. We welcome contributions, whether you're fixing bugs, improving documentation, or proposing new charts. Here's how you can get started:

1. **Browse Our Charts**: Visit our [documentation](/docs/category/charts.md) to explore installation guides and configuration options.
2. **Contribute**: Check out our [contribution guide](https://github.com/community-charts/helm-charts/blob/main/CONTRIBUTING.md) and submit pull requests to our [GitHub repository](https://github.com/community-charts/helm-charts).
3. **Suggest a Chart**: Have an open-source project in mind? [Submit a chart request](https://github.com/community-charts/helm-charts/issues/new?template=chart_request.yml).
4. **Report Issues**: Found a bug? [Let us know](https://github.com/community-charts/helm-charts/issues) so we can improve.

## What's Next?[​](#whats-next "Direct link to What's Next?")

This is just the beginning. We're actively working on enhancing our documentation, adding new charts, and integrating community feedback. Stay tuned for updates on new features, chart releases, and tutorials. Follow our [GitHub repository](https://github.com/community-charts/helm-charts) for the latest news, and join our community (coming soon!) to connect with other Kubernetes enthusiasts.

Thank you for supporting GitHub Community Charts. Let's make deploying open-source tools on Kubernetes easier, together!

**Tags:**

* [Helm](/blog/tags/helm.md "Easily manage and deploy your Kubernetes applications with Helm, the friendly package manager for cloud-native environments.")
* [Kubernetes](/blog/tags/kubernetes.md "Orchestrate, scale, and manage your containerized applications with Kubernetes, the leading open-source platform for modern infrastructure.")
* [Mlflow](/blog/tags/mlflow.md "Streamline your machine learning projects with MLflow, your companion for tracking, packaging, and deploying models effortlessly.")
* [Open Source](/blog/tags/open-source.md "Discover the power of open-source software—collaborative, transparent, and built by the community for everyone.")
* [Community](/blog/tags/community.md "Join a vibrant community where ideas, projects, and support come together to help everyone grow and succeed.")

[Edit this page](https://github.com/community-charts/community-charts.github.io/tree/main/blog/2025-06-15-welcome-to-community-charts.md)


---

[Skip to main content](#__docusaurus_skipToContent_fallback)

[![Community Charts Logo](/img/logo.png)![Community Charts Logo](/img/logo.png)](/index.md)

[**Community Charts**](/index.md)[Guide](/docs/getting-started.md)[Blog](/blog.md)

[GitHub](https://github.com/community-charts/community-charts.github.io)

Search

# Search the documentation

Type your search here

Powered by[](https://www.algolia.com/)

Docs

* [Getting Started](/docs/getting-started.md)

Community

* [Stack Overflow](https://stackoverflow.com/questions/tagged/community-charts)
* [X (Twitter)](https://x.com/ChartsCommunity)
* [BlueSky](https://bsky.app/profile/community-charts.bsky.social)
* [Keybase](https://keybase.io/communitycharts)

More

* [Blog](/blog.md)
* [GitHub](https://github.com/community-charts/helm-charts)

Copyright © 2026 Community Charts


---

## [📄️Usage](/docs/charts/actualbudget/usage.md)

[Get started with Actual Budget Helm chart deployment and basic usage](/docs/charts/actualbudget/usage.md)


---

## [🗃mlflow](/docs/category/mlflow.md)

[10 items](/docs/category/mlflow.md)


---

## [📄️Usage](/docs/charts/cloudflared/usage.md)

[Learn how to deploy and use Cloudflared Tunnel with the community-maintained Helm chart](/docs/charts/cloudflared/usage.md)


---

## [📄️Usage](/docs/charts/drone/usage.md)

[How to install, upgrade, and use the Drone Helm chart for CI/CD on Kubernetes.](/docs/charts/drone/usage.md)


---

## [📄️Usage Guide](/docs/charts/mlflow/usage.md)

[Complete guide to deploying and configuring MLflow on Kubernetes using the community-maintained Helm chart. Learn about databases, cloud storage, authentication, autoscaling, and monitoring.](/docs/charts/mlflow/usage.md)


---

## [📄️Usage Guide](/docs/charts/n8n/usage.md)

[Deploy and configure n8n on Kubernetes with enterprise-grade features using our community-maintained Helm chart](/docs/charts/n8n/usage.md)


---

## [📄️Usage](/docs/charts/outline/usage.md)

[Get started with Outline Helm chart deployment and basic usage](/docs/charts/outline/usage.md)


---

## [📄️Usage](/docs/charts/pypiserver/usage.md)

[Learn how to deploy and use PyPI Server on Kubernetes with the community-maintained Helm chart](/docs/charts/pypiserver/usage.md)


---

# Advanced Configuration

This guide covers advanced configuration options for production deployments and specialized use cases.

## Security Configuration[​](#security-configuration "Direct link to Security Configuration")

### Pod Security Context[​](#pod-security-context "Direct link to Pod Security Context")

We use the following security context for enhanced security. User ID 1001 and Group ID 1001 actual user and actual group IDs respectively. Pleae find more information from [here](https://github.com/actualbudget/actual/blob/e3aa63d1fa252ebc3f99061a95ebe9ad0454c400/packages/sync-server/docker/ubuntu.Dockerfile#L46).

```
podSecurityContext:

  fsGroup: 1001

  fsGroupChangePolicy: "OnRootMismatch"



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

  readOnlyRootFilesystem: false

  runAsNonRoot: true

  privileged: false

  runAsUser: 1001

  runAsGroup: 1001
```

### Service Account Configuration[​](#service-account-configuration "Direct link to Service Account Configuration")

Customize service account settings:

```
serviceAccount:

  create: true

  automount: true

  name: ""

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/actualbudget-role"
```

## Networking Configuration[​](#networking-configuration "Direct link to Networking Configuration")

### Service Configuration[​](#service-configuration "Direct link to Service Configuration")

Advanced service configuration:

```
service:

  type: ClusterIP

  port: 5006

  name: http

  annotations:

    service.beta.kubernetes.io/aws-load-balancer-type: "nlb"

    service.beta.kubernetes.io/aws-load-balancer-internal: "true"
```

### Ingress Advanced Configuration[​](#ingress-advanced-configuration "Direct link to Ingress Advanced Configuration")

Complex ingress setup with multiple hosts and TLS:

```
ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

    cert-manager.io/cluster-issuer: letsencrypt-prod

    nginx.ingress.kubernetes.io/ssl-redirect: "true"

    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"

    nginx.ingress.kubernetes.io/proxy-body-size: "50m"

  hosts:

    - host: actualbudget.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

    - host: budget.internal.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: actualbudget-tls

      hosts:

        - actualbudget.yourdomain.com

        - budget.internal.yourdomain.com
```

### Load Balancer Configuration[​](#load-balancer-configuration "Direct link to Load Balancer Configuration")

For cloud providers with load balancers:

```
service:

  type: LoadBalancer

  port: 5006

  annotations:

    service.beta.kubernetes.io/aws-load-balancer-type: "nlb"

    service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing"

    service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip"
```

## Resource Management[​](#resource-management "Direct link to Resource Management")

### Advanced Resource Configuration[​](#advanced-resource-configuration "Direct link to Advanced Resource Configuration")

Fine-tune resource allocation:

```
resources:

  limits:

    cpu: "1"

    memory: "2Gi"

    ephemeral-storage: "1Gi"

  requests:

    cpu: "500m"

    memory: "1Gi"

    ephemeral-storage: "512Mi"
```

### Horizontal Pod Autoscaling[​](#horizontal-pod-autoscaling "Direct link to Horizontal Pod Autoscaling")

Configure HPA for high availability:

```
# values.yaml

replicaCount: 1



# Create HPA separately

apiVersion: autoscaling/v2

kind: HorizontalPodAutoscaler

metadata:

  name: actualbudget-hpa

spec:

  scaleTargetRef:

    apiVersion: apps/v1

    kind: Deployment

    name: actualbudget

  minReplicas: 1

  maxReplicas: 3

  metrics:

    - type: Resource

      resource:

        name: memory

        target:

          type: Utilization

          averageUtilization: 80

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70
```

## Node Selection and Affinity[​](#node-selection-and-affinity "Direct link to Node Selection and Affinity")

### Node Selector[​](#node-selector "Direct link to Node Selector")

Deploy to specific nodes:

```
nodeSelector:

  node-type: application

  storage: ssd
```

### Affinity and Anti-Affinity[​](#affinity-and-anti-affinity "Direct link to Affinity and Anti-Affinity")

Configure pod placement rules:

```
affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - actualbudget

        topologyKey: kubernetes.io/hostname

  nodeAffinity:

    requiredDuringSchedulingIgnoredDuringExecution:

      nodeSelectorTerms:

      - matchExpressions:

        - key: node-type

          operator: In

          values:

          - application
```

### Tolerations[​](#tolerations "Direct link to Tolerations")

Deploy to tainted nodes:

```
tolerations:

- key: "dedicated"

  operator: "Equal"

  value: "actualbudget"

  effect: "NoSchedule"
```

## Volume and Volume Mounts[​](#volume-and-volume-mounts "Direct link to Volume and Volume Mounts")

### Additional Volumes[​](#additional-volumes "Direct link to Additional Volumes")

Mount additional volumes for configuration or data:

```
volumes:

  - name: config-volume

    configMap:

      name: actualbudget-config

  - name: certs-volume

    secret:

      secretName: actualbudget-certs

  - name: logs-volume

    persistentVolumeClaim:

      claimName: actualbudget-logs



volumeMounts:

  - name: config-volume

    mountPath: /app/config

    readOnly: true

  - name: certs-volume

    mountPath: /app/certs

    readOnly: true

  - name: logs-volume

    mountPath: /app/logs
```

## Init Containers[​](#init-containers "Direct link to Init Containers")

Configure init containers for setup tasks:

```
initContainers:

  - name: init-db

    image: busybox

    command:

      - /bin/sh

      - -c

      - |

        echo "Initializing database..."

        mkdir -p /data/server-files /data/user-files

        chown -R 1000:3000 /data

    volumeMounts:

      - name: data

        mountPath: /data
```

## Sidecar Containers[​](#sidecar-containers "Direct link to Sidecar Containers")

Add sidecar containers for monitoring or logging:

```
extraContainers:

  - name: nginx-sidecar

    image: nginx:alpine

    ports:

      - name: nginx

        containerPort: 80

    volumeMounts:

      - name: nginx-config

        mountPath: /etc/nginx/conf.d

    resources:

      limits:

        cpu: 100m

        memory: 128Mi

      requests:

        cpu: 50m

        memory: 64Mi



volumes:

  - name: nginx-config

    configMap:

      name: nginx-config
```

## Image Pull Secrets[​](#image-pull-secrets "Direct link to Image Pull Secrets")

Configure private registry access:

```
imagePullSecrets:

  - name: registry-secret
```

## Pod Annotations and Labels[​](#pod-annotations-and-labels "Direct link to Pod Annotations and Labels")

Add custom metadata:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "5006"

  prometheus.io/path: "/metrics"

  backup.kubernetes.io/enabled: "true"

  backup.kubernetes.io/schedule: "daily"



podLabels:

  app.kubernetes.io/component: "application"

  app.kubernetes.io/part-of: "finance"

  environment: "production"
```

## Deployment Strategy[​](#deployment-strategy "Direct link to Deployment Strategy")

Advanced deployment strategies:

```
strategy:

  type: RollingUpdate

  rollingUpdate:

    maxSurge: "25%"

    maxUnavailable: "25%"
```

For zero-downtime deployments with multiple replicas:

```
replicaCount: 2

strategy:

  type: RollingUpdate

  rollingUpdate:

    maxSurge: "50%"

    maxUnavailable: "0"
```

## Health Check Configuration[​](#health-check-configuration "Direct link to Health Check Configuration")

Customize health checks:

```
livenessProbe:

  httpGet:

    path: /

    port: http

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 3



readinessProbe:

  httpGet:

    path: /

    port: http

  initialDelaySeconds: 5

  periodSeconds: 5

  timeoutSeconds: 3

  failureThreshold: 3
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [troubleshooting common issues](/docs/charts/actualbudget/troubleshooting.md)
* Configure [authentication methods](/docs/charts/actualbudget/authentication.md)
* Set up [storage and persistence](/docs/charts/actualbudget/storage.md)


---

# Authentication Setup

Actual Budget supports multiple authentication methods. This guide covers all available authentication options and their configuration.

## Authentication Methods[​](#authentication-methods "Direct link to Authentication Methods")

The chart supports three authentication methods:

* **Password**: Traditional username/password authentication
* **Header**: Header-based authentication for reverse proxy setups
* **OpenID Connect**: OAuth2/OpenID Connect for enterprise SSO

## Basic Authentication Configuration[​](#basic-authentication-configuration "Direct link to Basic Authentication Configuration")

```
login:

  method: password

  allowedLoginMethods:

    - password

    - header

    - openid

  skipSSLVerification: false
```

## Password Authentication[​](#password-authentication "Direct link to Password Authentication")

The default authentication method using username and password:

```
login:

  method: password

  allowedLoginMethods:

    - password
```

info

When using password authentication, you'll create your account on first login through the web interface.

## Header-Based Authentication[​](#header-based-authentication "Direct link to Header-Based Authentication")

Use header-based authentication when running behind a reverse proxy that handles authentication:

```
login:

  method: header

  allowedLoginMethods:

    - header
```

tip

Header authentication is useful when you have an existing authentication system (like LDAP, OAuth proxy, etc.) that sets user headers.

## OpenID Connect Authentication[​](#openid-connect-authentication "Direct link to OpenID Connect Authentication")

Configure OpenID Connect for enterprise SSO integration. Actual Budget supports both discovery-based and manual endpoint configuration.

### Discovery-Based Configuration[​](#discovery-based-configuration "Direct link to Discovery-Based Configuration")

```
login:

  method: openid

  allowedLoginMethods:

    - openid

  openid:

    enforce: true

    providerName: "Your SSO Provider"

    discoveryUrl: "https://your-provider.com/.well-known/openid_configuration"

    clientId: "your-client-id"

    clientSecret: "your-client-secret"
```

### Manual Endpoint Configuration[​](#manual-endpoint-configuration "Direct link to Manual Endpoint Configuration")

```
login:

  method: openid

  allowedLoginMethods:

    - openid

  openid:

    enforce: true

    providerName: "Custom OIDC Provider"

    authorizationEndpoint: "https://your-provider.com/oauth/authorize"

    tokenEndpoint: "https://your-provider.com/oauth/token"

    userInfoEndpoint: "https://your-provider.com/oauth/userinfo"

    clientId: "your-client-id"

    clientSecret: "your-client-secret"
```

### OpenID Connect with Ingress[​](#openid-connect-with-ingress "Direct link to OpenID Connect with Ingress")

When using OpenID Connect with ingress, the chart automatically configures the server hostname:

```
ingress:

  enabled: true

  hosts:

    - host: actualbudget.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: actualbudget-tls

      hosts:

        - actualbudget.yourdomain.com



login:

  method: openid

  allowedLoginMethods:

    - openid

  openid:

    enforce: true

    providerName: "Your SSO Provider"

    discoveryUrl: "https://your-provider.com/.well-known/openid_configuration"

    clientId: "your-client-id"

    clientSecret: "your-client-secret"
```

warning

The `clientSecret` will be stored in a Kubernetes Secret. Ensure your cluster has proper RBAC and encryption at rest configured.

### Existing Secret for OpenID Client Secret[​](#existing-secret-for-openid-client-secret "Direct link to Existing Secret for OpenID Client Secret")

To use OpenID with a Kubernetes Secret for sensitive data:

1. **Create a Secret**:

```
kubectl create secret generic actualbudget-openid-secret \

  --from-literal=clientId=actualbudget-client \

  --from-literal=clientSecret=your-client-secret
```

2. **Update `values.yaml`**:

```
login:

  method: "openid"

  openid:

    enforce: true

    providerName: "Keycloak"

    discoveryUrl: "https://keycloak.example.com/auth/realms/my-realm/.well-known/openid-configuration"

    tokenExpiration: 3600

    existingSecret:

      name: "actualbudget-openid-secret"

      clientIdKey: "clientId"

      clientSecretKey: "clientSecret"
```

## Multiple Authentication Methods[​](#multiple-authentication-methods "Direct link to Multiple Authentication Methods")

You can enable multiple authentication methods simultaneously:

```
login:

  method: password  # Default method

  allowedLoginMethods:

    - password

    - openid

  openid:

    enforce: false  # Don't enforce OIDC, allow fallback to password

    providerName: "Optional SSO"

    discoveryUrl: "https://your-provider.com/.well-known/openid_configuration"

    clientId: "your-client-id"

    clientSecret: "your-client-secret"
```

## SSL Verification[​](#ssl-verification "Direct link to SSL Verification")

For development or self-signed certificates, you can disable SSL verification:

```
login:

  method: openid

  skipSSLVerification: true

  openid:

    # ... OIDC configuration
```

danger

Only disable SSL verification in development environments. Production deployments should use proper SSL certificates.

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically sets the following environment variables based on your configuration:

| Variable                       | Description                             | Source                      |
| ------------------------------ | --------------------------------------- | --------------------------- |
| `ACTUAL_LOGIN_METHOD`          | Primary authentication method           | `login.method`              |
| `ACTUAL_ALLOWED_LOGIN_METHODS` | Comma-separated list of allowed methods | `login.allowedLoginMethods` |
| `NODE_TLS_REJECT_UNAUTHORIZED` | SSL verification setting                | `login.skipSSLVerification` |
| `ACTUAL_MULTIUSER`             | Multi-user mode flag                    | Auto-set for OIDC           |
| `ACTUAL_OPENID_*`              | OpenID Connect configuration            | `login.openid.*`            |

## Common OpenID Connect Providers[​](#common-openid-connect-providers "Direct link to Common OpenID Connect Providers")

### Google Workspace[​](#google-workspace "Direct link to Google Workspace")

```
login:

  method: openid

  allowedLoginMethods:

    - openid

  openid:

    enforce: true

    providerName: "Google Workspace"

    discoveryUrl: "https://accounts.google.com/.well-known/openid_configuration"

    clientId: "your-google-client-id"

    clientSecret: "your-google-client-secret"

    authMethod: "openid"

    tokenExpiration: 3600
```

### Azure AD[​](#azure-ad "Direct link to Azure AD")

```
login:

  method: openid

  allowedLoginMethods:

    - openid

  openid:

    enforce: true

    providerName: "Azure AD"

    discoveryUrl: "https://login.microsoftonline.com/your-tenant-id/v2.0/.well-known/openid_configuration"

    clientId: "your-azure-client-id"

    clientSecret: "your-azure-client-secret"

    authMethod: "openid"

    tokenExpiration: 3600
```

### Okta[​](#okta "Direct link to Okta")

```
login:

  method: openid

  allowedLoginMethods:

    - openid

  openid:

    enforce: true

    providerName: "Okta"

    discoveryUrl: "https://your-domain.okta.com/.well-known/openid_configuration"

    clientId: "your-okta-client-id"

    clientSecret: "your-okta-client-secret"

    authMethod: "openid"

    tokenExpiration: 3600
```

## Troubleshooting Authentication[​](#troubleshooting-authentication "Direct link to Troubleshooting Authentication")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **OIDC Discovery Fails**: Verify the discovery URL is accessible and returns valid JSON
2. **Client ID/Secret Errors**: Ensure credentials are correct and the application is properly configured
3. **Redirect URI Issues**: Configure the correct redirect URI in your OIDC provider (usually `https://your-domain.com/oauth/callback`)
4. **SSL Certificate Issues**: Use `skipSSLVerification: true` for development, proper certificates for production

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Configure [storage and persistence](/docs/charts/actualbudget/storage.md)
* Set up [advanced configuration options](/docs/charts/actualbudget/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/actualbudget/troubleshooting.md)


---

# Configuration Guide

This guide covers the essential configuration options for deploying Actual Budget using the Helm chart.

## Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

### Image Configuration[​](#image-configuration "Direct link to Image Configuration")

```
image:

  repository: actualbudget/actual-server

  tag: ""  # Uses chart appVersion by default

  pullPolicy: IfNotPresent
```

### Service Configuration[​](#service-configuration "Direct link to Service Configuration")

```
service:

  type: ClusterIP

  port: 5006

  name: http

  annotations: {}
```

## File Storage Configuration[​](#file-storage-configuration "Direct link to File Storage Configuration")

Actual Budget requires specific directory structure for data storage:

```
files:

  dataDirectory: /data

  server: /data/server-files

  user: /data/user-files
```

info

* **`dataDirectory`**: Base directory where all data is stored
* **`server`**: Contains account.sqlite with user accounts and session tokens
* **`user`**: Stores budget files as binary blobs

## Persistence Configuration[​](#persistence-configuration "Direct link to Persistence Configuration")

Enable persistent storage to retain data across pod restarts:

```
persistence:

  enabled: true

  size: 10Gi

  accessModes:

    - ReadWriteOnce

  storageClass: ""

  existingClaim: ""
```

tip

For production deployments, always enable persistence to prevent data loss during pod restarts or updates.

## Upload Limits[​](#upload-limits "Direct link to Upload Limits")

Configure file upload size limits:

```
upload:

  fileSizeLimitMB: 20

  fileSizeSyncLimitMB: 20

  syncEncryptedFileSizeLimitMB: 50
```

## Deployment Strategy[​](#deployment-strategy "Direct link to Deployment Strategy")

Choose between RollingUpdate and Recreate strategies:

```
strategy:

  type: Recreate  # Recommended for single-instance deployments

  rollingUpdate:

    maxSurge: "100%"

    maxUnavailable: 0
```

warning

Use `Recreate` strategy for single-instance deployments to avoid data corruption issues during updates.

## Resource Management[​](#resource-management "Direct link to Resource Management")

Set resource requests and limits:

```
resources:

  limits:

    cpu: 200m

    memory: 256Mi

  requests:

    cpu: 100m

    memory: 128Mi
```

## Health Checks[​](#health-checks "Direct link to Health Checks")

Configure liveness and readiness probes:

```
livenessProbe:

  httpGet:

    path: /

    port: http



readinessProbe:

  httpGet:

    path: /

    port: http
```

## Ingress Configuration[​](#ingress-configuration "Direct link to Ingress Configuration")

Enable ingress for external access:

```
ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

    kubernetes.io/tls-acme: "true"

  hosts:

    - host: actualbudget.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: actualbudget-tls

      hosts:

        - actualbudget.yourdomain.com
```

## Complete Example[​](#complete-example "Direct link to Complete Example")

Here's a complete configuration example for a production deployment:

```
# Basic deployment

replicaCount: 1

strategy:

  type: Recreate



# Image configuration

image:

  repository: actualbudget/actual-server

  pullPolicy: IfNotPresent



# File storage

files:

  dataDirectory: /data

  server: /data/server-files

  user: /data/user-files



# Persistence

persistence:

  enabled: true

  size: 20Gi

  accessModes:

    - ReadWriteOnce

  storageClass: ""



# Upload limits

upload:

  fileSizeLimitMB: 20

  fileSizeSyncLimitMB: 20

  syncEncryptedFileSizeLimitMB: 50



# Authentication

login:

  method: password

  allowedLoginMethods:

    - password

    - header

    - openid



# Ingress

ingress:

  enabled: true

  className: nginx

  hosts:

    - host: actualbudget.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific



# Resources

resources:

  limits:

    cpu: 500m

    memory: 512Mi

  requests:

    cpu: 200m

    memory: 256Mi
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [authentication setup](/docs/charts/actualbudget/authentication.md)
* Configure [storage and persistence](/docs/charts/actualbudget/storage.md)
* Explore [advanced configuration options](/docs/charts/actualbudget/advanced-configuration.md)


---

# Storage and Persistence

Proper storage configuration is crucial for Actual Budget deployments to ensure data persistence across pod restarts and updates.

## Storage Architecture[​](#storage-architecture "Direct link to Storage Architecture")

Actual Budget uses a specific directory structure for data storage:

```
/data/

├── server-files/     # Server configuration and user accounts

│   └── account.sqlite

└── user-files/       # Budget files and user data

    └── *.blob
```

## Basic Persistence Configuration[​](#basic-persistence-configuration "Direct link to Basic Persistence Configuration")

Enable persistent storage with default settings:

```
persistence:

  enabled: true

  size: 10Gi

  accessModes:

    - ReadWriteOnce

  storageClass: ""
```

## Advanced Persistence Options[​](#advanced-persistence-options "Direct link to Advanced Persistence Options")

### Storage Class Configuration[​](#storage-class-configuration "Direct link to Storage Class Configuration")

Specify a custom storage class for your cluster:

```
persistence:

  enabled: true

  size: 20Gi

  storageClass: "fast-ssd"

  accessModes:

    - ReadWriteOnce
```

### Using Existing PVC[​](#using-existing-pvc "Direct link to Using Existing PVC")

Attach to an existing PersistentVolumeClaim:

```
persistence:

  enabled: true

  existingClaim: "my-actualbudget-data"

  # Other settings are ignored when using existingClaim
```

### Multiple Access Modes[​](#multiple-access-modes "Direct link to Multiple Access Modes")

For shared storage scenarios:

```
persistence:

  enabled: true

  size: 50Gi

  accessModes:

    - ReadWriteMany  # For NFS or similar shared storage

  storageClass: "nfs-storage"
```

### Subpath Configuration[​](#subpath-configuration "Direct link to Subpath Configuration")

Mount to a subdirectory within the PVC:

```
persistence:

  enabled: true

  size: 100Gi

  subPath: "actualbudget"

  accessModes:

    - ReadWriteOnce
```

## File Storage Configuration[​](#file-storage-configuration "Direct link to File Storage Configuration")

Configure the directory structure for data storage:

```
files:

  dataDirectory: /data

  server: /data/server-files

  user: /data/user-files
```

info

The `dataDirectory` is the base mount point, while `server` and `user` are subdirectories within it.

## Storage Recommendations[​](#storage-recommendations "Direct link to Storage Recommendations")

### Development Environment[​](#development-environment "Direct link to Development Environment")

```
persistence:

  enabled: true

  size: 5Gi

  accessModes:

    - ReadWriteOnce

  storageClass: "standard"
```

### Production Environment[​](#production-environment "Direct link to Production Environment")

```
persistence:

  enabled: true

  size: 50Gi

  accessModes:

    - ReadWriteOnce

  storageClass: "fast-ssd"

  annotations:

    backup.kubernetes.io/enabled: "true"
```

### High Availability Setup[​](#high-availability-setup "Direct link to High Availability Setup")

```
persistence:

  enabled: true

  size: 100Gi

  accessModes:

    - ReadWriteMany  # For shared storage

  storageClass: "nfs-storage"
```

## Backup and Recovery[​](#backup-and-recovery "Direct link to Backup and Recovery")

### Manual Backup[​](#manual-backup "Direct link to Manual Backup")

Create a backup of your data:

```
# Create a backup pod

kubectl run backup-actualbudget --rm -it --image=busybox --restart=Never --overrides='

{

  "spec": {

    "volumes": [

      {

        "name": "data",

        "persistentVolumeClaim": {

          "claimName": "actualbudget-data"

        }

      }

    ],

    "containers": [

      {

        "name": "backup",

        "image": "busybox",

        "command": ["tar", "czf", "/backup/actualbudget-backup.tar.gz", "/data"],

        "volumeMounts": [

          {

            "name": "data",

            "mountPath": "/data"

          }

        ]

      }

    ]

  }

}'



# Copy backup from pod

kubectl cp backup-actualbudget:/backup/actualbudget-backup.tar.gz ./actualbudget-backup.tar.gz
```

### Automated Backup with CronJob[​](#automated-backup-with-cronjob "Direct link to Automated Backup with CronJob")

Create a CronJob for automated backups:

```
apiVersion: batch/v1

kind: CronJob

metadata:

  name: actualbudget-backup

spec:

  schedule: "0 2 * * *"  # Daily at 2 AM

  jobTemplate:

    spec:

      template:

        spec:

          containers:

          - name: backup

            image: busybox

            command:

            - /bin/sh

            - -c

            - |

              tar czf /backup/actualbudget-$(date +%Y%m%d).tar.gz /data

            volumeMounts:

            - name: data

              mountPath: /data

            - name: backup-storage

              mountPath: /backup

          volumes:

          - name: data

            persistentVolumeClaim:

              claimName: actualbudget-data

          - name: backup-storage

            persistentVolumeClaim:

              claimName: backup-storage

          restartPolicy: OnFailure
```

## Storage Performance Optimization[​](#storage-performance-optimization "Direct link to Storage Performance Optimization")

### Resource Allocation[​](#resource-allocation "Direct link to Resource Allocation")

Ensure adequate resources for storage operations:

```
resources:

  limits:

    cpu: 500m

    memory: 1Gi

  requests:

    cpu: 200m

    memory: 512Mi
```

### Volume Mounts[​](#volume-mounts "Direct link to Volume Mounts")

For additional storage volumes:

```
volumeMounts:

  - name: additional-storage

    mountPath: /data/exports

    subPath: exports



volumes:

  - name: additional-storage

    persistentVolumeClaim:

      claimName: additional-storage-pvc
```

## Troubleshooting Storage Issues[​](#troubleshooting-storage-issues "Direct link to Troubleshooting Storage Issues")

### Common Problems[​](#common-problems "Direct link to Common Problems")

1. **PVC Pending**: Check storage class availability and capacity
2. **Permission Denied**: Verify security context and file permissions
3. **Storage Full**: Monitor disk usage and increase PVC size
4. **Data Loss**: Ensure persistence is enabled and properly configured

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check PVC status

kubectl get pvc



# Check pod storage

kubectl exec -it actualbudget-pod -- df -h



# Check file permissions

kubectl exec -it actualbudget-pod -- ls -la /data



# View storage events

kubectl get events --sort-by='.lastTimestamp' | grep -i storage
```

### Storage Monitoring[​](#storage-monitoring "Direct link to Storage Monitoring")

Add monitoring annotations for storage tracking:

```
persistence:

  enabled: true

  annotations:

    monitoring.kubernetes.io/enabled: "true"

    backup.kubernetes.io/schedule: "daily"
```

## Migration and Scaling[​](#migration-and-scaling "Direct link to Migration and Scaling")

### PVC Expansion[​](#pvc-expansion "Direct link to PVC Expansion")

Expand existing PVC (if supported by storage class):

```
# Patch PVC to increase size

kubectl patch pvc actualbudget-data -p '{"spec":{"resources":{"requests":{"storage":"50Gi"}}}}'
```

### Data Migration[​](#data-migration "Direct link to Data Migration")

Migrate data between storage classes:

```
# Create new PVC with different storage class

kubectl apply -f new-storage-pvc.yaml



# Copy data using a migration pod

kubectl run migration --rm -it --image=busybox --restart=Never --overrides='

{

  "spec": {

    "volumes": [

      {"name": "old", "persistentVolumeClaim": {"claimName": "old-pvc"}},

      {"name": "new", "persistentVolumeClaim": {"claimName": "new-pvc"}}

    ],

    "containers": [{

      "name": "migration",

      "image": "busybox",

      "command": ["cp", "-r", "/old", "/new"],

      "volumeMounts": [

        {"name": "old", "mountPath": "/old"},

        {"name": "new", "mountPath": "/new"}

      ]

    }]

  }

}'
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Configure [advanced configuration options](/docs/charts/actualbudget/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/actualbudget/troubleshooting.md)
* Set up [authentication methods](/docs/charts/actualbudget/authentication.md)


---

# Troubleshooting

This guide covers common issues and their solutions when deploying Actual Budget using the Helm chart.

## Pod Issues[​](#pod-issues "Direct link to Pod Issues")

### Pod Stuck in Pending State[​](#pod-stuck-in-pending-state "Direct link to Pod Stuck in Pending State")

**Symptoms**: Pod remains in `Pending` status

**Common Causes**:

* Insufficient cluster resources
* PVC binding issues
* Node selector constraints

**Solutions**:

```
# Check pod events

kubectl describe pod <pod-name>



# Check resource availability

kubectl get nodes -o custom-columns="NAME:.metadata.name,CPU:.status.capacity.cpu,MEMORY:.status.capacity.memory"



# Check PVC status

kubectl get pvc

kubectl describe pvc <pvc-name>
```

### Pod CrashLoopBackOff[​](#pod-crashloopbackoff "Direct link to Pod CrashLoopBackOff")

**Symptoms**: Pod repeatedly crashes and restarts

**Solutions**:

```
# Check pod logs

kubectl logs <pod-name> --previous



# Check pod events

kubectl describe pod <pod-name>



# Check resource limits

kubectl top pod <pod-name>
```

**Common Fixes**:

```
# Increase resource limits

resources:

  limits:

    cpu: "1"

    memory: "2Gi"

  requests:

    cpu: "500m"

    memory: "1Gi"



# Add startup probe for slow startup

startupProbe:

  httpGet:

    path: /

    port: http

  initialDelaySeconds: 60

  periodSeconds: 10

  failureThreshold: 30
```

## Storage Issues[​](#storage-issues "Direct link to Storage Issues")

### PVC Binding Failures[​](#pvc-binding-failures "Direct link to PVC Binding Failures")

**Symptoms**: PVC remains in `Pending` status

**Solutions**:

```
# Check storage classes

kubectl get storageclass



# Check PVC details

kubectl describe pvc <pvc-name>



# Check cluster capacity

kubectl get nodes -o custom-columns="NAME:.metadata.name,STORAGE:.status.capacity.ephemeral-storage"
```

**Common Fixes**:

```
# Specify available storage class

persistence:

  enabled: true

  storageClass: "standard"  # Use available storage class

  size: 10Gi



# Or disable persistence for testing

persistence:

  enabled: false
```

### Permission Denied Errors[​](#permission-denied-errors "Direct link to Permission Denied Errors")

**Symptoms**: Application can't write to storage

**Solutions**:

```
# Check file permissions

kubectl exec -it <pod-name> -- ls -la /data



# Check security context

kubectl get pod <pod-name> -o yaml | grep -A 10 securityContext
```

**Fix**:

```
# Configure proper security context

podSecurityContext:

  fsGroup: 1001

  fsGroupChangePolicy: "OnRootMismatch"



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

  readOnlyRootFilesystem: false

  runAsNonRoot: true

  privileged: false

  runAsUser: 1001

  runAsGroup: 1001
```

## Authentication Issues[​](#authentication-issues "Direct link to Authentication Issues")

### OpenID Connect Problems[​](#openid-connect-problems "Direct link to OpenID Connect Problems")

**Symptoms**: OIDC authentication fails

**Debug Steps**:

```
# Check OIDC secret

kubectl get secret <release-name>-openid-secret -o yaml



# Check pod environment variables

kubectl exec -it <pod-name> -- env | grep ACTUAL_OPENID



# Check application logs

kubectl logs <pod-name> | grep -i oidc
```

**Common Issues**:

1. **Invalid Discovery URL**:

   ```
   login:

     openid:

       discoveryUrl: "https://your-provider.com/.well-known/openid_configuration"
   ```

2. **Wrong Redirect URI**:

   * Configure redirect URI in OIDC provider as: `https://your-domain.com/oauth/callback`

3. **SSL Certificate Issues**:

   ```
   login:

     skipSSLVerification: true  # Only for development
   ```

### Password Authentication Issues[​](#password-authentication-issues "Direct link to Password Authentication Issues")

**Symptoms**: Can't create account or login

**Solutions**:

```
# Check if multi-user mode is enabled

kubectl exec -it <pod-name> -- env | grep ACTUAL_MULTIUSER



# Reset by deleting server files (WARNING: loses all data)

kubectl exec -it <pod-name> -- rm -rf /data/server-files/*
```

## Networking Issues[​](#networking-issues "Direct link to Networking Issues")

### Ingress Not Working[​](#ingress-not-working "Direct link to Ingress Not Working")

**Symptoms**: Can't access application via ingress

**Debug Steps**:

```
# Check ingress status

kubectl get ingress

kubectl describe ingress <ingress-name>



# Check ingress controller logs

kubectl logs -n ingress-nginx deployment/ingress-nginx-controller



# Test service directly

kubectl port-forward svc/<service-name> 5006:5006
```

**Common Fixes**:

```
# Ensure proper ingress configuration

ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

  hosts:

    - host: actualbudget.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific
```

### Service Connection Issues[​](#service-connection-issues "Direct link to Service Connection Issues")

**Symptoms**: Can't connect to service

**Debug Steps**:

```
# Check service

kubectl get svc

kubectl describe svc <service-name>



# Test service from within cluster

kubectl run test-pod --rm -it --image=busybox --restart=Never -- wget -O- http://<service-name>:5006



# Check endpoints

kubectl get endpoints <service-name>
```

## Resource Issues[​](#resource-issues "Direct link to Resource Issues")

### Out of Memory[​](#out-of-memory "Direct link to Out of Memory")

**Symptoms**: Pod crashes with OOM errors

**Solutions**:

```
# Check memory usage

kubectl top pod <pod-name>



# Check memory limits

kubectl get pod <pod-name> -o jsonpath='{.spec.containers[0].resources}'
```

**Fix**:

```
# Increase memory limits

resources:

  limits:

    memory: "2Gi"

  requests:

    memory: "1Gi"
```

### High CPU Usage[​](#high-cpu-usage "Direct link to High CPU Usage")

**Symptoms**: Slow performance, high CPU usage

**Solutions**:

```
# Check CPU usage

kubectl top pod <pod-name>



# Check CPU limits

kubectl get pod <pod-name> -o jsonpath='{.spec.containers[0].resources}'
```

**Fix**:

```
# Increase CPU limits

resources:

  limits:

    cpu: "1"

  requests:

    cpu: "500m"
```

## Health Check Issues[​](#health-check-issues "Direct link to Health Check Issues")

### Liveness Probe Failures[​](#liveness-probe-failures "Direct link to Liveness Probe Failures")

**Symptoms**: Pod restarts due to failed health checks

**Debug Steps**:

```
# Check probe configuration

kubectl get pod <pod-name> -o jsonpath='{.spec.containers[0].livenessProbe}'



# Test endpoint manually

kubectl exec -it <pod-name> -- wget -O- http://localhost:5006/
```

**Fix**:

```
# Adjust probe settings

livenessProbe:

  httpGet:

    path: /

    port: http

  initialDelaySeconds: 60

  periodSeconds: 30

  timeoutSeconds: 10

  failureThreshold: 3
```

## Upgrade Issues[​](#upgrade-issues "Direct link to Upgrade Issues")

### Helm Upgrade Failures[​](#helm-upgrade-failures "Direct link to Helm Upgrade Failures")

**Symptoms**: `helm upgrade` fails

**Solutions**:

```
# Check upgrade status

helm status <release-name>



# Rollback to previous version

helm rollback <release-name> <revision>



# Check values compatibility

helm template <release-name> . --debug
```

### Breaking Changes[​](#breaking-changes "Direct link to Breaking Changes")

**Version 1.5.x Upgrade**:

```
# Update deprecated field

login:

  openid:

    discoveryUrl: "https://your-provider.com/.well-known/openid_configuration"

    # Remove: dicovertUrl (deprecated)
```

## Data Issues[​](#data-issues "Direct link to Data Issues")

### Data Loss[​](#data-loss "Direct link to Data Loss")

**Symptoms**: Budget data missing after restart

**Causes**:

* Persistence not enabled
* Wrong PVC configuration
* Storage class issues

**Prevention**:

```
# Always enable persistence in production

persistence:

  enabled: true

  size: 20Gi

  storageClass: "reliable-storage"
```

### Data Corruption[​](#data-corruption "Direct link to Data Corruption")

**Symptoms**: Application errors or corrupted data

**Solutions**:

```
# Check data integrity

kubectl exec -it <pod-name> -- ls -la /data/



# Backup before attempting fixes

kubectl run backup --rm -it --image=busybox --restart=Never -- tar czf /backup/data.tar.gz /data

kubectl cp backup:/backup/data.tar.gz ./backup.tar.gz
```

## Monitoring and Logging[​](#monitoring-and-logging "Direct link to Monitoring and Logging")

### Check Application Logs[​](#check-application-logs "Direct link to Check Application Logs")

```
# Follow logs

kubectl logs -f <pod-name>



# Check previous logs

kubectl logs <pod-name> --previous



# Check specific time range

kubectl logs <pod-name> --since=1h
```

### Monitor Resources[​](#monitor-resources "Direct link to Monitor Resources")

```
# Check resource usage

kubectl top pod <pod-name>



# Check events

kubectl get events --sort-by='.lastTimestamp' | grep <pod-name>



# Check pod status

kubectl get pods -w
```

## Common Error Messages[​](#common-error-messages "Direct link to Common Error Messages")

### "ImagePullBackOff"[​](#imagepullbackoff "Direct link to \"ImagePullBackOff\"")

```
# Check image availability

kubectl describe pod <pod-name> | grep -A 10 Events



# Fix: Use correct image or configure imagePullSecrets

image:

  repository: actualbudget/actual-server

  tag: "25.6.1"
```

### "CrashLoopBackOff"[​](#crashloopbackoff "Direct link to \"CrashLoopBackOff\"")

```
# Check logs for root cause

kubectl logs <pod-name> --previous



# Common causes: resource limits, configuration errors, missing dependencies
```

### "Pending" Status[​](#pending-status "Direct link to \"Pending\" Status")

```
# Check scheduling events

kubectl describe pod <pod-name> | grep -A 20 Events



# Common causes: resource constraints, node selectors, PVC issues
```

## Getting Help[​](#getting-help "Direct link to Getting Help")

### Collect Debug Information[​](#collect-debug-information "Direct link to Collect Debug Information")

```
# Create debug bundle

kubectl get all -l app.kubernetes.io/name=actualbudget -o yaml > debug.yaml

kubectl describe pod <pod-name> > pod-description.txt

kubectl logs <pod-name> > pod-logs.txt

kubectl get events --sort-by='.lastTimestamp' > events.txt
```

### Useful Commands[​](#useful-commands "Direct link to Useful Commands")

```
# Quick health check

kubectl get pods,svc,ingress,pvc



# Check helm release

helm status <release-name>



# Validate values

helm template <release-name> . --validate



# Test connectivity

kubectl run test --rm -it --image=busybox --restart=Never -- wget -O- http://<service-name>:5006
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Review [configuration options](/docs/charts/actualbudget/configuration.md)
* Check [authentication setup](/docs/charts/actualbudget/authentication.md)
* Configure [storage properly](/docs/charts/actualbudget/storage.md)
* Explore [advanced configuration](/docs/charts/actualbudget/advanced-configuration.md)


---

# Actual Budget Chart Usage Guide

[Actual Budget](https://actualbudget.org) is a self-hosted personal finance manager that helps you track your spending, set budgets, and gain control over your finances. This Helm chart makes it easy to deploy Actual Budget on Kubernetes.

* **Official Website:** <https://actualbudget.org>
* **GitHub Repository:** <https://github.com/actualbudget/actual>
* **Documentation:** <https://actualbudget.org/docs>
* **ArtifactHub:** [Actual Budget Helm Chart](https://artifacthub.io/packages/helm/community-charts/actualbudget)

## Why use this chart?[​](#why-use-this-chart "Direct link to Why use this chart?")

* Quick, reliable deployment of Actual Budget on any Kubernetes cluster
* Community-maintained and up-to-date
* Great for self-hosters and teams needing private finance management
* Supports multiple authentication methods including OpenID Connect
* Configurable persistence and resource management

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

* Kubernetes cluster (1.16+)
* Helm 3.x
* Ingress controller (optional, for external access)
* Storage class (for persistent data)

## Quick Start[​](#quick-start "Direct link to Quick Start")

### 1. Add the Helm Repository[​](#1-add-the-helm-repository "Direct link to 1. Add the Helm Repository")

```
helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update
```

### 2. Basic Installation[​](#2-basic-installation "Direct link to 2. Basic Installation")

```
helm install my-actualbudget community-charts/actualbudget -n <your-namespace>
```

Replace `<your-namespace>` with your target namespace.

### 3. Access the Application[​](#3-access-the-application "Direct link to 3. Access the Application")

After installation, access Actual Budget:

```
# Port forward to access locally

kubectl port-forward svc/my-actualbudget 5006:5006



# Or access via ingress (if configured)

# Navigate to your configured domain
```

## Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

### Enable Persistence[​](#enable-persistence "Direct link to Enable Persistence")

For production deployments, always enable persistence:

```
persistence:

  enabled: true

  size: 20Gi

  storageClass: "standard"
```

### Configure Ingress[​](#configure-ingress "Direct link to Configure Ingress")

Enable external access via ingress:

```
ingress:

  enabled: true

  className: nginx

  hosts:

    - host: actualbudget.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: actualbudget-tls

      hosts:

        - actualbudget.yourdomain.com
```

### Set Resource Limits[​](#set-resource-limits "Direct link to Set Resource Limits")

Configure appropriate resource allocation:

```
resources:

  limits:

    cpu: 500m

    memory: 1Gi

  requests:

    cpu: 200m

    memory: 512Mi
```

## Complete Example[​](#complete-example "Direct link to Complete Example")

Here's a complete configuration for a production deployment:

```
# values.yaml

replicaCount: 1

strategy:

  type: Recreate



# Persistence

persistence:

  enabled: true

  size: 20Gi

  accessModes:

    - ReadWriteOnce



# File storage

files:

  dataDirectory: /data

  server: /data/server-files

  user: /data/user-files



# Ingress

ingress:

  enabled: true

  className: nginx

  hosts:

    - host: actualbudget.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific



# Resources

resources:

  limits:

    cpu: 500m

    memory: 1Gi

  requests:

    cpu: 200m

    memory: 512Mi



# Authentication (password-based)

login:

  method: password

  allowedLoginMethods:

    - password
```

Install with custom values:

```
helm install my-actualbudget community-charts/actualbudget \

  -f values.yaml \

  -n <your-namespace>
```

## Common Operations[​](#common-operations "Direct link to Common Operations")

### Upgrade the Chart[​](#upgrade-the-chart "Direct link to Upgrade the Chart")

```
helm repo update

helm upgrade my-actualbudget community-charts/actualbudget -n <your-namespace>
```

### Uninstall the Chart[​](#uninstall-the-chart "Direct link to Uninstall the Chart")

```
helm uninstall my-actualbudget -n <your-namespace>
```

warning

Uninstalling will remove all Kubernetes resources. If persistence is enabled, PVC data will be retained based on your storage class reclaim policy.

### Check Status[​](#check-status "Direct link to Check Status")

```
# Check release status

helm status my-actualbudget -n <your-namespace>



# Check resources

kubectl get all -l app.kubernetes.io/name=actualbudget -n <your-namespace>



# Check logs

kubectl logs -f deployment/my-actualbudget -n <your-namespace>
```

## First Time Setup[​](#first-time-setup "Direct link to First Time Setup")

1. **Access the Application**: Navigate to your configured URL or use port-forward
2. **Create Account**: On first access, create your admin account
3. **Import Data**: Import your existing budget data or start fresh
4. **Configure Sync**: Set up synchronization with your devices

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically configures these environment variables:

| Variable              | Description           | Default              |
| --------------------- | --------------------- | -------------------- |
| `ACTUAL_PORT`         | Server port           | `5006`               |
| `ACTUAL_DATA_DIR`     | Data directory        | `/data`              |
| `ACTUAL_SERVER_FILES` | Server files path     | `/data/server-files` |
| `ACTUAL_USER_FILES`   | User files path       | `/data/user-files`   |
| `ACTUAL_LOGIN_METHOD` | Authentication method | `password`           |

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Pod not starting**: Check resource limits and storage configuration
2. **Can't access application**: Verify ingress configuration and service
3. **Data not persisting**: Ensure persistence is enabled and PVC is bound

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check pod status

kubectl get pods -n <your-namespace>



# Check pod events

kubectl describe pod <pod-name> -n <your-namespace>



# Check logs

kubectl logs <pod-name> -n <your-namespace>



# Check PVC status

kubectl get pvc -n <your-namespace>
```

For detailed troubleshooting, see the [troubleshooting guide](/docs/charts/actualbudget/troubleshooting.md).

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [configuration options](/docs/charts/actualbudget/configuration.md)
* Set up [authentication methods](/docs/charts/actualbudget/authentication.md)
* Configure [storage and persistence](/docs/charts/actualbudget/storage.md)
* Explore [advanced configuration options](/docs/charts/actualbudget/advanced-configuration.md)
* Troubleshoot common issues in the [troubleshooting guide](/docs/charts/actualbudget/troubleshooting.md)


---

# Advanced Configuration

This guide covers advanced configuration options for production deployments and specialized use cases.

## High Availability Configuration[​](#high-availability-configuration "Direct link to High Availability Configuration")

### Multi-Node Deployment[​](#multi-node-deployment "Direct link to Multi-Node Deployment")

Deploy Cloudflared to all nodes for high availability:

```
replica:

  allNodes: true



updateStrategy:

  type: RollingUpdate

  rollingUpdate:

    maxUnavailable: 1



tolerations:

  - effect: NoSchedule

    operator: Exists
```

### Pod Anti-Affinity[​](#pod-anti-affinity "Direct link to Pod Anti-Affinity")

Ensure pods are distributed across nodes:

```
affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - cloudflared

        topologyKey: kubernetes.io/hostname
```

### Node Affinity[​](#node-affinity "Direct link to Node Affinity")

Deploy to specific node types:

```
affinity:

  nodeAffinity:

    requiredDuringSchedulingIgnoredDuringExecution:

      nodeSelectorTerms:

      - matchExpressions:

        - key: node-type

          operator: In

          values:

          - edge

          - ingress
```

## Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

### Resource Configuration[​](#resource-configuration "Direct link to Resource Configuration")

Optimize resource allocation for high-traffic scenarios:

```
resources:

  limits:

    cpu: "1000m"

    memory: "512Mi"

  requests:

    cpu: "500m"

    memory: "256Mi"
```

### Connection Pooling[​](#connection-pooling "Direct link to Connection Pooling")

Configure connection pooling for better performance:

```
tunnelConfig:

  protocol: "http2"  # Use HTTP/2 for better performance

  retries: 10

  connectTimeout: "15s"

  gracePeriod: "30s"
```

### Keep-Alive Settings[​](#keep-alive-settings "Direct link to Keep-Alive Settings")

Optimize keep-alive connections:

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      keepAliveConnections: 200

      keepAliveTimeout: 120s

      connectTimeout: 10s

      readTimeout: 60s
```

## Security Enhancements[​](#security-enhancements "Direct link to Security Enhancements")

### Network Policies[​](#network-policies "Direct link to Network Policies")

Create restrictive network policies:

```
apiVersion: networking.k8s.io/v1

kind: NetworkPolicy

metadata:

  name: cloudflared-network-policy

spec:

  podSelector:

    matchLabels:

      app.kubernetes.io/name: cloudflared

  policyTypes:

  - Ingress

  - Egress

  ingress:

  - from:

    - namespaceSelector:

        matchLabels:

          name: kube-system

    ports:

    - protocol: TCP

      port: 2000

  egress:

  - to:

    - namespaceSelector:

        matchLabels:

          name: default

    ports:

    - protocol: TCP

      port: 80

    - protocol: TCP

      port: 443

  - to:

    - namespaceSelector:

        matchLabels:

          name: kube-system

    ports:

    - protocol: TCP

      port: 53
```

### Pod Security Standards[​](#pod-security-standards "Direct link to Pod Security Standards")

Configure pod security standards:

```
podSecurityContext:

  fsGroup: 65532

  fsGroupChangePolicy: "OnRootMismatch"

  runAsUser: 65532

  runAsGroup: 65532

  runAsNonRoot: true

  sysctls:

    - name: net.ipv4.ping_group_range

      value: "0 2147483647"



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

    add:

      - NET_RAW

  readOnlyRootFilesystem: true

  runAsNonRoot: true

  privileged: false

  runAsUser: 65532

  runAsGroup: 65532
```

### RBAC Configuration[​](#rbac-configuration "Direct link to RBAC Configuration")

Configure proper RBAC:

```
apiVersion: rbac.authorization.k8s.io/v1

kind: ClusterRole

metadata:

  name: cloudflared-tunnel-role

rules:

- apiGroups: [""]

  resources: ["services", "endpoints"]

  verbs: ["get", "list", "watch"]

- apiGroups: [""]

  resources: ["pods"]

  verbs: ["get", "list"]

---

apiVersion: rbac.authorization.k8s.io/v1

kind: ClusterRoleBinding

metadata:

  name: cloudflared-tunnel-binding

subjects:

- kind: ServiceAccount

  name: my-cloudflared

  namespace: default

roleRef:

  kind: ClusterRole

  name: cloudflared-tunnel-role

  apiGroup: rbac.authorization.k8s.io
```

## Monitoring and Observability[​](#monitoring-and-observability "Direct link to Monitoring and Observability")

### Prometheus Integration[​](#prometheus-integration "Direct link to Prometheus Integration")

Enable Prometheus monitoring:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/metrics"

  prometheus.io/scheme: "http"
```

### Custom Metrics[​](#custom-metrics "Direct link to Custom Metrics")

Configure custom metrics collection:

```
tunnelConfig:

  metricsUpdateFrequency: "5s"

  logLevel: "info"

  transportLogLevel: "warn"
```

### Health Checks[​](#health-checks "Direct link to Health Checks")

Configure comprehensive health checks:

```
livenessProbe:

  httpGet:

    path: /ready

    port: 2000

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 3



readinessProbe:

  httpGet:

    path: /ready

    port: 2000

  initialDelaySeconds: 10

  periodSeconds: 5

  timeoutSeconds: 3

  failureThreshold: 3
```

### Log Aggregation[​](#log-aggregation "Direct link to Log Aggregation")

Configure log aggregation:

```
podAnnotations:

  fluentbit.io/parser: "cloudflared"

  logging.kubernetes.io/format: "json"
```

## Custom Environment Variables[​](#custom-environment-variables "Direct link to Custom Environment Variables")

### Additional Environment Variables[​](#additional-environment-variables "Direct link to Additional Environment Variables")

```
extraEnvVars:

  - name: TUNNEL_METRICS

    value: "0.0.0.0:2000"

  - name: TUNNEL_ORIGIN_CA_POOL

    value: "/etc/ssl/certs/ca-certificates.crt"

  - name: TUNNEL_PROTOCOL

    value: "http2"
```

### Using Existing Secrets[​](#using-existing-secrets "Direct link to Using Existing Secrets")

```
extraSecretNamesForEnvFrom:

  - name: cloudflared-config

    optional: false
```

## Custom Volumes and Configurations[​](#custom-volumes-and-configurations "Direct link to Custom Volumes and Configurations")

### Additional Volumes[​](#additional-volumes "Direct link to Additional Volumes")

```
volumes:

  - name: custom-config

    configMap:

      name: cloudflared-custom-config

  - name: ssl-certs

    secret:

      secretName: ssl-certificates



volumeMounts:

  - name: custom-config

    mountPath: /etc/cloudflared/custom

    readOnly: true

  - name: ssl-certs

    mountPath: /etc/ssl/certs

    readOnly: true
```

### Custom Configuration Files[​](#custom-configuration-files "Direct link to Custom Configuration Files")

Create custom configuration files:

```
apiVersion: v1

kind: ConfigMap

metadata:

  name: cloudflared-custom-config

data:

  custom-rules.yaml: |

    # Custom routing rules

    - hostname: custom.example.com

      service: http://custom-service.default.svc.cluster.local:8080
```

## Load Balancing and Traffic Management[​](#load-balancing-and-traffic-management "Direct link to Load Balancing and Traffic Management")

### Multiple Tunnel Instances[​](#multiple-tunnel-instances "Direct link to Multiple Tunnel Instances")

Deploy multiple tunnel instances for load balancing:

```
# Primary tunnel

replica:

  allNodes: false

  count: 3



# Secondary tunnel for backup

nameOverride: "cloudflared-backup"

fullnameOverride: "cloudflared-backup"



tunnelConfig:

  name: "backup-tunnel"
```

### Traffic Splitting[​](#traffic-splitting "Direct link to Traffic Splitting")

Configure traffic splitting between services:

```
ingress:

  - hostname: example.com

    service: http://web-service-1.default.svc.cluster.local:80

    originRequest:

      loadBalancer:

        pool: web-pool-1



  - hostname: example.com

    service: http://web-service-2.default.svc.cluster.local:80

    originRequest:

      loadBalancer:

        pool: web-pool-2
```

## Disaster Recovery[​](#disaster-recovery "Direct link to Disaster Recovery")

### Backup Configuration[​](#backup-configuration "Direct link to Backup Configuration")

Create backup tunnel configurations:

```
# Primary configuration

tunnelConfig:

  name: "primary-tunnel"

  retries: 5

  connectTimeout: "30s"



# Backup configuration

nameOverride: "cloudflared-backup"

tunnelConfig:

  name: "backup-tunnel"

  retries: 10

  connectTimeout: "60s"
```

### Geographic Distribution[​](#geographic-distribution "Direct link to Geographic Distribution")

Deploy tunnels across different regions:

```
# US region

nodeSelector:

  region: us-west-1



# EU region

nameOverride: "cloudflared-eu"

nodeSelector:

  region: eu-west-1
```

## Custom Init Containers[​](#custom-init-containers "Direct link to Custom Init Containers")

### Pre-flight Checks[​](#pre-flight-checks "Direct link to Pre-flight Checks")

Add init containers for pre-flight checks:

```
initContainers:

  - name: tunnel-check

    image: cloudflare/cloudflared:latest

    command:

      - /bin/sh

      - -c

      - |

        cloudflared tunnel info my-tunnel || exit 1

    env:

      - name: TUNNEL_TOKEN

        valueFrom:

          secretKeyRef:

            name: tunnel-credentials

            key: credentials.json
```

## Service Account Configuration[​](#service-account-configuration "Direct link to Service Account Configuration")

### Custom Service Account[​](#custom-service-account "Direct link to Custom Service Account")

```
serviceAccount:

  create: true

  name: "cloudflared-service-account"

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/cloudflared-role"

    iam.gke.io/gcp-service-account: "cloudflared@project.iam.gserviceaccount.com"
```

## Custom Labels and Annotations[​](#custom-labels-and-annotations "Direct link to Custom Labels and Annotations")

### Pod Labels[​](#pod-labels "Direct link to Pod Labels")

```
podLabels:

  app.kubernetes.io/component: tunnel

  environment: production

  team: infrastructure

  cost-center: networking
```

### Pod Annotations[​](#pod-annotations "Direct link to Pod Annotations")

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/metrics"

  backup.kubernetes.io/enabled: "true"

  backup.kubernetes.io/schedule: "daily"

  monitoring.kubernetes.io/enabled: "true"
```

## Complete Production Example[​](#complete-production-example "Direct link to Complete Production Example")

Here's a comprehensive production configuration:

```
# High availability deployment

replica:

  allNodes: true



# Image configuration

image:

  repository: cloudflare/cloudflared

  pullPolicy: IfNotPresent



# Update strategy

updateStrategy:

  type: RollingUpdate

  rollingUpdate:

    maxUnavailable: 1



# Tunnel configuration

tunnelConfig:

  name: "production-tunnel"

  logLevel: "info"

  transportLogLevel: "warn"

  protocol: "http2"

  retries: 10

  connectTimeout: "15s"

  gracePeriod: "30s"

  metricsUpdateFrequency: "5s"

  autoUpdateFrequency: "24h"

  noAutoUpdate: true

  warpRouting: false



# Tunnel secrets

tunnelSecrets:

  base64EncodedConfigJsonFile: "your-base64-encoded-credentials"

  base64EncodedPemFile: "your-base64-encoded-certificate"



# Ingress rules

ingress:

  - hostname: app.example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 10s

      readTimeout: 60s

      keepAliveConnections: 200

      keepAliveTimeout: 120s



  - hostname: api.example.com

    service: http://api-service.default.svc.cluster.local:8080

    originRequest:

      connectTimeout: 10s

      readTimeout: 30s



  - hostname: "*.example.com"

    service: http://wildcard-service.default.svc.cluster.local:80



  - service: http_status:404



# Resources

resources:

  limits:

    cpu: "1000m"

    memory: "512Mi"

  requests:

    cpu: "500m"

    memory: "256Mi"



# Security

podSecurityContext:

  fsGroup: 65532

  fsGroupChangePolicy: "OnRootMismatch"

  runAsUser: 65532

  runAsGroup: 65532

  runAsNonRoot: true

  sysctls:

    - name: net.ipv4.ping_group_range

      value: "0 2147483647"



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

    add:

      - NET_RAW

  readOnlyRootFilesystem: true

  runAsNonRoot: true

  privileged: false

  runAsUser: 65532

  runAsGroup: 65532



# Node selection

nodeSelector:

  kubernetes.io/os: linux

  node-type: edge



# Tolerations

tolerations:

  - effect: NoSchedule

    operator: Exists



# Affinity

affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - cloudflared

        topologyKey: kubernetes.io/hostname



# Service account

serviceAccount:

  create: true

  name: "cloudflared-service-account"

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/cloudflared-role"



# Monitoring

podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/metrics"

  backup.kubernetes.io/enabled: "true"

  backup.kubernetes.io/schedule: "daily"



# Labels

podLabels:

  app.kubernetes.io/component: tunnel

  environment: production

  team: infrastructure



# Termination

terminationGracePeriodSeconds: 30
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [tunnel setup](/docs/charts/cloudflared/tunnel-setup.md)
* Configure [ingress rules](/docs/charts/cloudflared/ingress-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/cloudflared/troubleshooting.md)
* Review [configuration options](/docs/charts/cloudflared/configuration.md)


---

# Configuration Guide

This guide covers the essential configuration options for deploying Cloudflared Tunnel using the Helm chart.

## Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

### Image Configuration[​](#image-configuration "Direct link to Image Configuration")

```
image:

  repository: cloudflare/cloudflared

  tag: ""  # Uses chart appVersion by default

  pullPolicy: IfNotPresent
```

### Replica Configuration[​](#replica-configuration "Direct link to Replica Configuration")

Choose between DaemonSet and Deployment modes:

```
replica:

  allNodes: true  # Use DaemonSet to deploy to all nodes

  count: 1        # Number of replicas (used when allNodes: false)
```

tip

Use `allNodes: true` for high availability across all cluster nodes, or `allNodes: false` with `count: N` for specific replica count.

### Update Strategy[​](#update-strategy "Direct link to Update Strategy")

Configure how updates are applied:

```
updateStrategy:

  type: RollingUpdate

  rollingUpdate:

    maxUnavailable: 1
```

## Tunnel Configuration[​](#tunnel-configuration "Direct link to Tunnel Configuration")

### Basic Tunnel Settings[​](#basic-tunnel-settings "Direct link to Basic Tunnel Settings")

```
tunnelConfig:

  name: "your-tunnel-name"

  logLevel: "info"  # info, warn, error, fatal, panic

  protocol: "auto"  # auto, http2, h2mux, quic

  retries: 5

  connectTimeout: "30s"

  gracePeriod: "30s"
```

### Advanced Tunnel Settings[​](#advanced-tunnel-settings "Direct link to Advanced Tunnel Settings")

```
tunnelConfig:

  name: "your-tunnel-name"

  logLevel: "info"

  transportLogLevel: "warn"  # debug, info, warn, error, fatal

  protocol: "auto"

  retries: 5

  connectTimeout: "30s"

  gracePeriod: "30s"

  metricsUpdateFrequency: "5s"

  autoUpdateFrequency: "24h"

  noAutoUpdate: true

  warpRouting: false
```

info

* **`protocol`**: Choose between `auto`, `http2`, `h2mux`, or `quic` for connection protocol
* **`logLevel`**: Set logging verbosity for the tunnel
* **`transportLogLevel`**: Set logging verbosity for transport layer
* **`warpRouting`**: Enable Cloudflare WARP routing features

## Tunnel Secrets[​](#tunnel-secrets "Direct link to Tunnel Secrets")

Configure tunnel credentials and certificates:

```
tunnelSecrets:

  base64EncodedConfigJsonFile: "base64-encoded-credentials-json"

  base64EncodedPemFile: "base64-encoded-certificate-pem"
```

warning

These secrets are required and must be base64-encoded versions of your Cloudflare tunnel files.

### Encoding Tunnel Files[​](#encoding-tunnel-files "Direct link to Encoding Tunnel Files")

Encode your tunnel files using these commands:

```
# Encode credentials JSON file

base64 -b 0 -i ~/.cloudflared/*.json



# Encode certificate PEM file

base64 -b 0 -i ~/.cloudflared/cert.pem
```

## Ingress Configuration[​](#ingress-configuration "Direct link to Ingress Configuration")

### Basic Ingress Rules[​](#basic-ingress-rules "Direct link to Basic Ingress Rules")

```
ingress:

  - hostname: example.com

    service: http://your-service.namespace.svc.cluster.local:80



  - hostname: api.example.com

    service: http://api-service.namespace.svc.cluster.local:8080



  - service: http_status:404
```

### Advanced Ingress Rules[​](#advanced-ingress-rules "Direct link to Advanced Ingress Rules")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 10s

      disableChunkedEncoding: true



  - hostname: "*.example.com"

    service: http://wildcard-service.default.svc.cluster.local:80



  - path: "\\.(jpg|png|css|js)$"

    service: http://static-service.default.svc.cluster.local:80



  - service: http_status:404
```

tip

The last rule with `http_status:404` is required to handle unmatched requests.

## Resource Management[​](#resource-management "Direct link to Resource Management")

### Resource Limits[​](#resource-limits "Direct link to Resource Limits")

```
resources:

  limits:

    cpu: "400m"

    memory: "128Mi"

  requests:

    cpu: "100m"

    memory: "64Mi"
```

### Recommended Resources[​](#recommended-resources "Direct link to Recommended Resources")

For production deployments:

```
resources:

  limits:

    cpu: "500m"

    memory: "256Mi"

  requests:

    cpu: "200m"

    memory: "128Mi"
```

## Security Configuration[​](#security-configuration "Direct link to Security Configuration")

### Pod Security Context[​](#pod-security-context "Direct link to Pod Security Context")

```
podSecurityContext:

  fsGroup: 65532

  fsGroupChangePolicy: "OnRootMismatch"

  sysctls:

    - name: net.ipv4.ping_group_range

      value: "0 2147483647"
```

### Container Security Context[​](#container-security-context "Direct link to Container Security Context")

```
securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

    add:

      - NET_RAW

  readOnlyRootFilesystem: true

  runAsNonRoot: true

  privileged: false

  runAsUser: 65532

  runAsGroup: 65532
```

info

The `NET_RAW` capability is required for Cloudflared to function properly.

## Node Selection and Scheduling[​](#node-selection-and-scheduling "Direct link to Node Selection and Scheduling")

### Node Selector[​](#node-selector "Direct link to Node Selector")

```
nodeSelector:

  kubernetes.io/os: linux

  node-type: edge
```

### Tolerations[​](#tolerations "Direct link to Tolerations")

```
tolerations:

  - effect: NoSchedule

    operator: Exists
```

### Affinity Rules[​](#affinity-rules "Direct link to Affinity Rules")

```
affinity:

  nodeAffinity:

    requiredDuringSchedulingIgnoredDuringExecution:

      nodeSelectorTerms:

      - matchExpressions:

        - key: kubernetes.io/os

          operator: In

          values:

          - linux

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - cloudflared

        topologyKey: kubernetes.io/hostname
```

## Service Account Configuration[​](#service-account-configuration "Direct link to Service Account Configuration")

```
serviceAccount:

  create: true

  automount: true

  name: ""

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/cloudflared-role"
```

## Pod Annotations and Labels[​](#pod-annotations-and-labels "Direct link to Pod Annotations and Labels")

### Pod Annotations[​](#pod-annotations "Direct link to Pod Annotations")

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/ready"

  backup.kubernetes.io/enabled: "true"
```

### Pod Labels[​](#pod-labels "Direct link to Pod Labels")

```
podLabels:

  app.kubernetes.io/component: tunnel

  environment: production
```

## Termination Grace Period[​](#termination-grace-period "Direct link to Termination Grace Period")

```
terminationGracePeriodSeconds: 30
```

## Complete Example[​](#complete-example "Direct link to Complete Example")

Here's a complete configuration example for a production deployment:

```
# Basic deployment

replica:

  allNodes: true



# Image configuration

image:

  repository: cloudflare/cloudflared

  pullPolicy: IfNotPresent



# Update strategy

updateStrategy:

  type: RollingUpdate

  rollingUpdate:

    maxUnavailable: 1



# Tunnel configuration

tunnelConfig:

  name: "production-tunnel"

  logLevel: "info"

  transportLogLevel: "warn"

  protocol: "auto"

  retries: 5

  connectTimeout: "30s"

  gracePeriod: "30s"

  metricsUpdateFrequency: "5s"

  autoUpdateFrequency: "24h"

  noAutoUpdate: true

  warpRouting: false



# Tunnel secrets (base64 encoded)

tunnelSecrets:

  base64EncodedConfigJsonFile: "your-base64-encoded-credentials"

  base64EncodedPemFile: "your-base64-encoded-certificate"



# Ingress rules

ingress:

  - hostname: app.example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 10s

      disableChunkedEncoding: true



  - hostname: api.example.com

    service: http://api-service.default.svc.cluster.local:8080



  - hostname: "*.example.com"

    service: http://wildcard-service.default.svc.cluster.local:80



  - service: http_status:404



# Resources

resources:

  limits:

    cpu: "500m"

    memory: "256Mi"

  requests:

    cpu: "200m"

    memory: "128Mi"



# Security

podSecurityContext:

  fsGroup: 65532

  fsGroupChangePolicy: "OnRootMismatch"

  sysctls:

    - name: net.ipv4.ping_group_range

      value: "0 2147483647"



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

    add:

      - NET_RAW

  readOnlyRootFilesystem: true

  runAsNonRoot: true

  privileged: false

  runAsUser: 65532

  runAsGroup: 65532



# Node selection

nodeSelector:

  kubernetes.io/os: linux

  node-type: edge



# Tolerations

tolerations:

  - effect: NoSchedule

    operator: Exists



# Service account

serviceAccount:

  create: true

  automount: true

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/cloudflared-role"



# Monitoring

podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/ready"



# Termination

terminationGracePeriodSeconds: 30
```

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically sets these environment variables:

| Variable                    | Description         | Source                           |
| --------------------------- | ------------------- | -------------------------------- |
| `TUNNEL_NAME`               | Tunnel name         | `tunnelConfig.name`              |
| `TUNNEL_PROTOCOL`           | Connection protocol | `tunnelConfig.protocol`          |
| `TUNNEL_LOGLEVEL`           | Logging level       | `tunnelConfig.logLevel`          |
| `TUNNEL_TRANSPORT_LOGLEVEL` | Transport logging   | `tunnelConfig.transportLogLevel` |
| `TUNNEL_RETRIES`            | Connection retries  | `tunnelConfig.retries`           |
| `TUNNEL_CONNECT_TIMEOUT`    | Connection timeout  | `tunnelConfig.connectTimeout`    |
| `TUNNEL_GRACE_PERIOD`       | Grace period        | `tunnelConfig.gracePeriod`       |

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [tunnel setup](/docs/charts/cloudflared/tunnel-setup.md)
* Configure [ingress rules](/docs/charts/cloudflared/ingress-configuration.md)
* Explore [advanced configuration options](/docs/charts/cloudflared/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/cloudflared/troubleshooting.md)


---

# Ingress Configuration

This guide covers how to configure ingress rules for Cloudflare Tunnel to route traffic to your Kubernetes services.

## Ingress Overview[​](#ingress-overview "Direct link to Ingress Overview")

Cloudflare Tunnel ingress rules define how traffic is routed from the internet to your internal services. Unlike traditional Kubernetes ingress, tunnel ingress rules are processed by Cloudflared and can route traffic to any service within your cluster.

## Basic Ingress Rules[​](#basic-ingress-rules "Direct link to Basic Ingress Rules")

### Simple Hostname Routing[​](#simple-hostname-routing "Direct link to Simple Hostname Routing")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80



  - hostname: api.example.com

    service: http://api-service.default.svc.cluster.local:8080



  - service: http_status:404
```

tip

The last rule with `http_status:404` is required to handle unmatched requests and should always be included.

### Wildcard Subdomain Routing[​](#wildcard-subdomain-routing "Direct link to Wildcard Subdomain Routing")

```
ingress:

  - hostname: "*.example.com"

    service: http://wildcard-service.default.svc.cluster.local:80



  - hostname: app.example.com

    service: http://app-service.default.svc.cluster.local:3000



  - service: http_status:404
```

info

Wildcard subdomains require a CNAME record for `*` in your DNS configuration.

## Advanced Ingress Rules[​](#advanced-ingress-rules "Direct link to Advanced Ingress Rules")

### Path-Based Routing[​](#path-based-routing "Direct link to Path-Based Routing")

```
ingress:

  - hostname: example.com

    path: "/api/*"

    service: http://api-service.default.svc.cluster.local:8080



  - hostname: example.com

    path: "/admin/*"

    service: http://admin-service.default.svc.cluster.local:8080



  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80



  - service: http_status:404
```

### Static File Routing[​](#static-file-routing "Direct link to Static File Routing")

```
ingress:

  - hostname: example.com

    path: "\\.(jpg|jpeg|png|gif|ico|css|js|woff|woff2|ttf|eot)$"

    service: http://static-service.default.svc.cluster.local:80



  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80



  - service: http_status:404
```

### Multiple Services with Load Balancing[​](#multiple-services-with-load-balancing "Direct link to Multiple Services with Load Balancing")

```
ingress:

  - hostname: example.com

    service: http://web-service-1.default.svc.cluster.local:80

    originRequest:

      loadBalancer:

        pool: web-pool



  - hostname: example.com

    service: http://web-service-2.default.svc.cluster.local:80

    originRequest:

      loadBalancer:

        pool: web-pool



  - service: http_status:404
```

## Origin Request Configuration[​](#origin-request-configuration "Direct link to Origin Request Configuration")

### Connection Settings[​](#connection-settings "Direct link to Connection Settings")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 10s

      readTimeout: 30s

      keepAliveConnections: 100

      keepAliveTimeout: 90s

      disableChunkedEncoding: true

      httpHostHeader: "internal.example.com"
```

### TLS Settings[​](#tls-settings "Direct link to TLS Settings")

```
ingress:

  - hostname: example.com

    service: https://secure-service.default.svc.cluster.local:443

    originRequest:

      noTLSVerify: true

      caPool: /etc/ssl/certs/ca-certificates.crt

      clientTLS:

        cert: /etc/ssl/client.crt

        key: /etc/ssl/client.key
```

### HTTP Headers[​](#http-headers "Direct link to HTTP Headers")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      httpHostHeader: "internal.example.com"

      noTLSVerify: true

      headers:

        - name: X-Forwarded-For

          value: "{{ .ClientIP }}"

        - name: X-Real-IP

          value: "{{ .ClientIP }}"

        - name: X-Forwarded-Proto

          value: "{{ .Protocol }}"
```

## Service Types[​](#service-types "Direct link to Service Types")

### HTTP Services[​](#http-services "Direct link to HTTP Services")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80
```

### HTTPS Services[​](#https-services "Direct link to HTTPS Services")

```
ingress:

  - hostname: example.com

    service: https://secure-service.default.svc.cluster.local:443

    originRequest:

      noTLSVerify: true
```

### TCP Services[​](#tcp-services "Direct link to TCP Services")

```
ingress:

  - hostname: example.com

    service: tcp://database-service.default.svc.cluster.local:5432
```

### Unix Socket Services[​](#unix-socket-services "Direct link to Unix Socket Services")

```
ingress:

  - hostname: example.com

    service: unix:///var/run/myapp.sock
```

## Error Handling[​](#error-handling "Direct link to Error Handling")

### Custom Error Responses[​](#custom-error-responses "Direct link to Custom Error Responses")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80



  - hostname: api.example.com

    service: http://api-service.default.svc.cluster.local:8080



  # Custom error responses

  - service: http_status:404

  - service: http_status:500

  - service: http_status:503
```

### Fallback Services[​](#fallback-services "Direct link to Fallback Services")

```
ingress:

  - hostname: example.com

    service: http://primary-service.default.svc.cluster.local:80



  - hostname: example.com

    service: http://fallback-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 5s



  - service: http_status:404
```

## Load Balancing and High Availability[​](#load-balancing-and-high-availability "Direct link to Load Balancing and High Availability")

### Multiple Backend Services[​](#multiple-backend-services "Direct link to Multiple Backend Services")

```
ingress:

  - hostname: example.com

    service: http://web-service-1.default.svc.cluster.local:80



  - hostname: example.com

    service: http://web-service-2.default.svc.cluster.local:80



  - hostname: example.com

    service: http://web-service-3.default.svc.cluster.local:80



  - service: http_status:404
```

### Health Check Configuration[​](#health-check-configuration "Direct link to Health Check Configuration")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 10s

      readTimeout: 30s

      keepAliveConnections: 100

      keepAliveTimeout: 90s
```

## Security Configuration[​](#security-configuration "Direct link to Security Configuration")

### Access Control[​](#access-control "Direct link to Access Control")

```
ingress:

  - hostname: admin.example.com

    service: http://admin-service.default.svc.cluster.local:8080

    originRequest:

      headers:

        - name: X-API-Key

          value: "your-api-key"
```

### IP Filtering[​](#ip-filtering "Direct link to IP Filtering")

```
ingress:

  - hostname: internal.example.com

    service: http://internal-service.default.svc.cluster.local:80

    originRequest:

      ipRules:

        - prefix: "192.168.1.0/24"

          allow: true

        - prefix: "10.0.0.0/8"

          allow: true

        - prefix: "0.0.0.0/0"

          allow: false
```

## Monitoring and Logging[​](#monitoring-and-logging "Direct link to Monitoring and Logging")

### Request Logging[​](#request-logging "Direct link to Request Logging")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 10s

      readTimeout: 30s
```

### Metrics Collection[​](#metrics-collection "Direct link to Metrics Collection")

Enable metrics for monitoring:

```
tunnelConfig:

  metricsUpdateFrequency: "5s"

  logLevel: "info"

  transportLogLevel: "warn"
```

## Complete Examples[​](#complete-examples "Direct link to Complete Examples")

### Multi-Service Application[​](#multi-service-application "Direct link to Multi-Service Application")

```
ingress:

  # Web application

  - hostname: app.example.com

    service: http://web-service.default.svc.cluster.local:80



  # API service

  - hostname: api.example.com

    service: http://api-service.default.svc.cluster.local:8080

    originRequest:

      connectTimeout: 10s

      readTimeout: 30s



  # Admin panel

  - hostname: admin.example.com

    service: http://admin-service.default.svc.cluster.local:8080

    originRequest:

      headers:

        - name: X-API-Key

          value: "admin-key"



  # Static assets

  - hostname: app.example.com

    path: "\\.(css|js|png|jpg|ico)$"

    service: http://static-service.default.svc.cluster.local:80



  # Health check

  - hostname: health.example.com

    service: http://health-service.default.svc.cluster.local:8080



  # Default error response

  - service: http_status:404
```

### Microservices Architecture[​](#microservices-architecture "Direct link to Microservices Architecture")

```
ingress:

  # Frontend

  - hostname: frontend.example.com

    service: http://frontend-service.default.svc.cluster.local:3000



  # User service

  - hostname: users.example.com

    service: http://user-service.default.svc.cluster.local:8080



  # Product service

  - hostname: products.example.com

    service: http://product-service.default.svc.cluster.local:8080



  # Order service

  - hostname: orders.example.com

    service: http://order-service.default.svc.cluster.local:8080



  # Payment service

  - hostname: payments.example.com

    service: https://payment-service.default.svc.cluster.local:443

    originRequest:

      noTLSVerify: true



  # Monitoring

  - hostname: monitoring.example.com

    service: http://monitoring-service.default.svc.cluster.local:9090



  # Error handling

  - service: http_status:404
```

### Development Environment[​](#development-environment "Direct link to Development Environment")

```
ingress:

  # Development app

  - hostname: dev.example.com

    service: http://dev-service.default.svc.cluster.local:3000



  # Development API

  - hostname: dev-api.example.com

    service: http://dev-api-service.default.svc.cluster.local:8080



  # Development database (read-only)

  - hostname: dev-db.example.com

    service: tcp://dev-db-service.default.svc.cluster.local:5432



  # Development tools

  - hostname: dev-tools.example.com

    service: http://dev-tools-service.default.svc.cluster.local:8080



  # Error handling

  - service: http_status:404
```

## Best Practices[​](#best-practices "Direct link to Best Practices")

### 1. Always Include Error Handler[​](#1-always-include-error-handler "Direct link to 1. Always Include Error Handler")

```
ingress:

  # Your service rules here

  - service: http_status:404  # Required
```

### 2. Use Specific Hostnames[​](#2-use-specific-hostnames "Direct link to 2. Use Specific Hostnames")

```
# Good

- hostname: api.example.com

  service: http://api-service.default.svc.cluster.local:8080



# Avoid overly broad wildcards

- hostname: "*.example.com"

  service: http://catch-all-service.default.svc.cluster.local:80
```

### 3. Configure Timeouts[​](#3-configure-timeouts "Direct link to 3. Configure Timeouts")

```
ingress:

  - hostname: example.com

    service: http://web-service.default.svc.cluster.local:80

    originRequest:

      connectTimeout: 10s

      readTimeout: 30s
```

### 4. Use Health Checks[​](#4-use-health-checks "Direct link to 4. Use Health Checks")

```
ingress:

  - hostname: health.example.com

    service: http://health-service.default.svc.cluster.local:8080
```

### 5. Secure Sensitive Services[​](#5-secure-sensitive-services "Direct link to 5. Secure Sensitive Services")

```
ingress:

  - hostname: admin.example.com

    service: http://admin-service.default.svc.cluster.local:8080

    originRequest:

      headers:

        - name: X-API-Key

          value: "secure-key"
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Service Not Reachable**

   * Verify service name and namespace
   * Check service port
   * Ensure service is running

2. **DNS Resolution Issues**

   * Verify DNS records in Cloudflare
   * Check tunnel DNS configuration

3. **Timeout Issues**

   * Increase connection and read timeouts
   * Check service health

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check tunnel logs

kubectl logs -f deployment/my-cloudflared



# Test service connectivity

kubectl exec -it <pod-name> -- curl http://service-name.namespace.svc.cluster.local:port



# Check tunnel status

kubectl exec -it <pod-name> -- cloudflared tunnel info my-tunnel
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [tunnel setup](/docs/charts/cloudflared/tunnel-setup.md)
* Explore [advanced configuration options](/docs/charts/cloudflared/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/cloudflared/troubleshooting.md)
* Review [configuration options](/docs/charts/cloudflared/configuration.md)


---

# Troubleshooting

This guide covers common issues and their solutions when deploying Cloudflared Tunnel using the Helm chart.

## Pod Issues[​](#pod-issues "Direct link to Pod Issues")

### Pod Stuck in Pending State[​](#pod-stuck-in-pending-state "Direct link to Pod Stuck in Pending State")

**Symptoms**: Pod remains in `Pending` status

**Common Causes**:

* Insufficient cluster resources
* Node selector constraints
* Taint/toleration issues

**Solutions**:

```
# Check pod events

kubectl describe pod <pod-name>



# Check resource availability

kubectl get nodes -o custom-columns="NAME:.metadata.name,CPU:.status.capacity.cpu,MEMORY:.status.capacity.memory"



# Check node selector

kubectl get nodes --show-labels | grep -E "(kubernetes.io/os|node-type)"



# Check taints

kubectl get nodes -o custom-columns="NAME:.metadata.name,TAINTS:.spec.taints"
```

### Pod CrashLoopBackOff[​](#pod-crashloopbackoff "Direct link to Pod CrashLoopBackOff")

**Symptoms**: Pod repeatedly crashes and restarts

**Common Causes**:

* Invalid tunnel configuration
* Missing or incorrect credentials
* Configuration errors

**Solutions**:

```
# Check pod logs

kubectl logs <pod-name> --previous



# Check pod events

kubectl describe pod <pod-name>



# Check tunnel configuration

kubectl get configmap <release-name> -o yaml



# Check tunnel secrets

kubectl get secret tunnel-credentials -o yaml
```

### Pod Not Ready[​](#pod-not-ready "Direct link to Pod Not Ready")

**Symptoms**: Pod is running but not ready

**Common Causes**:

* Health check failures
* Tunnel connection issues
* Configuration problems

**Solutions**:

```
# Check readiness probe

kubectl describe pod <pod-name> | grep -A 10 "Readiness"



# Check tunnel health

kubectl exec -it <pod-name> -- curl -f http://localhost:2000/ready



# Check tunnel logs

kubectl logs <pod-name> | grep -i "ready\|health"
```

## Tunnel Connection Issues[​](#tunnel-connection-issues "Direct link to Tunnel Connection Issues")

### Tunnel Not Connecting[​](#tunnel-not-connecting "Direct link to Tunnel Not Connecting")

**Symptoms**: Tunnel fails to establish connection with Cloudflare

**Common Causes**:

* Invalid tunnel credentials
* Network connectivity issues
* DNS resolution problems

**Solutions**:

```
# Check tunnel status

kubectl exec -it <pod-name> -- cloudflared tunnel info <tunnel-name>



# Check tunnel logs

kubectl logs <pod-name> | grep -i "connection\|connect"



# Verify credentials

kubectl exec -it <pod-name> -- ls -la /etc/cloudflared/creds/



# Test tunnel locally

cloudflared tunnel run <tunnel-name>
```

### Authentication Failed[​](#authentication-failed "Direct link to Authentication Failed")

**Symptoms**: Tunnel authentication errors

**Common Causes**:

* Invalid or expired credentials
* Incorrect certificate
* Permission issues

**Solutions**:

```
# Re-authenticate with Cloudflare

cloudflared tunnel login



# Regenerate tunnel credentials

cloudflared tunnel create <tunnel-name>



# Update base64 encoded values

base64 -b 0 -i ~/.cloudflared/*.json

base64 -b 0 -i ~/.cloudflared/cert.pem



# Update Helm release

helm upgrade <release-name> community-charts/cloudflared \

  --set tunnelSecrets.base64EncodedConfigJsonFile="new-encoded-credentials" \

  --set tunnelSecrets.base64EncodedPemFile="new-encoded-certificate"
```

### DNS Resolution Issues[​](#dns-resolution-issues "Direct link to DNS Resolution Issues")

**Symptoms**: Cannot access services via tunnel hostnames

**Common Causes**:

* Missing DNS records
* Incorrect CNAME configuration
* DNS propagation delays

**Solutions**:

```
# Check DNS records

cloudflared tunnel route dns list



# Verify DNS resolution

nslookup <hostname>

dig <hostname>



# Check tunnel DNS configuration

kubectl exec -it <pod-name> -- cloudflared tunnel route ip show
```

## Service Routing Issues[​](#service-routing-issues "Direct link to Service Routing Issues")

### Service Not Reachable[​](#service-not-reachable "Direct link to Service Not Reachable")

**Symptoms**: Cannot access services through tunnel

**Common Causes**:

* Incorrect service name/namespace
* Service not running
* Port configuration issues

**Solutions**:

```
# Check service status

kubectl get svc -A



# Test service connectivity from pod

kubectl exec -it <pod-name> -- curl http://service-name.namespace.svc.cluster.local:port



# Check ingress configuration

kubectl get configmap <release-name> -o yaml



# Verify service endpoints

kubectl get endpoints <service-name> -n <namespace>
```

### Wrong Service Routing[​](#wrong-service-routing "Direct link to Wrong Service Routing")

**Symptoms**: Traffic routed to incorrect service

**Common Causes**:

* Incorrect ingress rules
* Hostname conflicts
* Path matching issues

**Solutions**:

```
# Check ingress configuration

kubectl get configmap <release-name> -o yaml



# Review ingress rules order

# Rules are processed in order, most specific first



# Test specific hostname

curl -H "Host: <hostname>" http://localhost
```

## Performance Issues[​](#performance-issues "Direct link to Performance Issues")

### High Latency[​](#high-latency "Direct link to High Latency")

**Symptoms**: Slow response times through tunnel

**Common Causes**:

* Network congestion
* Resource constraints
* Suboptimal protocol

**Solutions**:

```
# Check resource usage

kubectl top pod <pod-name>



# Monitor tunnel metrics

kubectl exec -it <pod-name> -- curl http://localhost:2000/metrics



# Optimize protocol

# Change tunnelConfig.protocol to "http2" or "quic"



# Check connection pooling

# Increase keepAliveConnections and keepAliveTimeout
```

### Connection Drops[​](#connection-drops "Direct link to Connection Drops")

**Symptoms**: Intermittent connection failures

**Common Causes**:

* Network instability
* Resource exhaustion
* Timeout issues

**Solutions**:

```
# Check tunnel logs for connection errors

kubectl logs <pod-name> | grep -i "connection\|timeout"



# Increase retry settings

# Set tunnelConfig.retries to higher value



# Adjust timeouts

# Increase connectTimeout and gracePeriod



# Check network policies

kubectl get networkpolicy
```

## Security Issues[​](#security-issues "Direct link to Security Issues")

### Permission Denied[​](#permission-denied "Direct link to Permission Denied")

**Symptoms**: Permission errors in logs

**Common Causes**:

* Incorrect security context
* File permission issues
* Service account problems

**Solutions**:

```
# Check security context

kubectl describe pod <pod-name> | grep -A 10 "Security Context"



# Verify file permissions

kubectl exec -it <pod-name> -- ls -la /etc/cloudflared/



# Check service account

kubectl get serviceaccount

kubectl describe serviceaccount <service-account-name>
```

### Network Policy Issues[​](#network-policy-issues "Direct link to Network Policy Issues")

**Symptoms**: Network connectivity blocked

**Common Causes**:

* Restrictive network policies
* Missing egress rules
* Incorrect namespace selectors

**Solutions**:

```
# Check network policies

kubectl get networkpolicy -A



# Test connectivity

kubectl exec -it <pod-name> -- curl http://service-name.namespace.svc.cluster.local:port



# Review network policy rules

kubectl describe networkpolicy <policy-name>
```

## Configuration Issues[​](#configuration-issues "Direct link to Configuration Issues")

### Invalid YAML Configuration[​](#invalid-yaml-configuration "Direct link to Invalid YAML Configuration")

**Symptoms**: Helm installation fails with YAML errors

**Common Causes**:

* Syntax errors in values.yaml
* Invalid ingress rules
* Missing required fields

**Solutions**:

```
# Validate Helm chart

helm template <release-name> community-charts/cloudflared -f values.yaml



# Check YAML syntax

yamllint values.yaml



# Validate ingress rules

# Ensure all required fields are present
```

### Missing Required Values[​](#missing-required-values "Direct link to Missing Required Values")

**Symptoms**: Chart installation fails with missing values

**Common Causes**:

* Missing tunnel name
* Missing credentials
* Incomplete configuration

**Solutions**:

```
# Check required values

helm template <release-name> community-charts/cloudflared -f values.yaml --debug



# Verify tunnel configuration

# Ensure tunnelConfig.name is set

# Ensure tunnelSecrets are provided



# Check values schema

helm template <release-name> community-charts/cloudflared --validate
```

## Common Error Messages[​](#common-error-messages "Direct link to Common Error Messages")

### "Base64 encoded config file string is required"[​](#base64-encoded-config-file-string-is-required "Direct link to \"Base64 encoded config file string is required\"")

```
# Encode credentials file

base64 -b 0 -i ~/.cloudflared/*.json



# Update values.yaml

tunnelSecrets:

  base64EncodedConfigJsonFile: "your-encoded-value"
```

### "Base64 encoded certificate pem file string is required"[​](#base64-encoded-certificate-pem-file-string-is-required "Direct link to \"Base64 encoded certificate pem file string is required\"")

```
# Encode certificate file

base64 -b 0 -i ~/.cloudflared/cert.pem



# Update values.yaml

tunnelSecrets:

  base64EncodedPemFile: "your-encoded-value"
```

### "A valid tunnelConfig.name entry required"[​](#a-valid-tunnelconfigname-entry-required "Direct link to \"A valid tunnelConfig.name entry required\"")

```
# Set tunnel name in values.yaml

tunnelConfig:

  name: "your-tunnel-name"
```

### "Tunnel not found"[​](#tunnel-not-found "Direct link to \"Tunnel not found\"")

```
# Verify tunnel exists

cloudflared tunnel list



# Check tunnel name

kubectl exec -it <pod-name> -- cloudflared tunnel info <tunnel-name>



# Recreate tunnel if needed

cloudflared tunnel create <tunnel-name>
```

## Debug Commands[​](#debug-commands "Direct link to Debug Commands")

### General Debugging[​](#general-debugging "Direct link to General Debugging")

```
# Check all resources

kubectl get all -l app.kubernetes.io/name=cloudflared



# Check events

kubectl get events --sort-by='.lastTimestamp' | grep cloudflared



# Check logs

kubectl logs -f deployment/<release-name>



# Check configuration

kubectl get configmap <release-name> -o yaml

kubectl get secret tunnel-credentials -o yaml
```

### Tunnel-Specific Debugging[​](#tunnel-specific-debugging "Direct link to Tunnel-Specific Debugging")

```
# Check tunnel status

kubectl exec -it <pod-name> -- cloudflared tunnel info <tunnel-name>



# Check tunnel logs

kubectl exec -it <pod-name> -- cloudflared tunnel logs <tunnel-name>



# Test tunnel locally

cloudflared tunnel run <tunnel-name>



# Check DNS routes

cloudflared tunnel route dns list
```

### Network Debugging[​](#network-debugging "Direct link to Network Debugging")

```
# Test DNS resolution

nslookup <hostname>

dig <hostname>



# Test service connectivity

kubectl exec -it <pod-name> -- curl -v http://service-name.namespace.svc.cluster.local:port



# Check network policies

kubectl get networkpolicy -A

kubectl describe networkpolicy <policy-name>
```

## Monitoring and Health Checks[​](#monitoring-and-health-checks "Direct link to Monitoring and Health Checks")

### Health Check Endpoints[​](#health-check-endpoints "Direct link to Health Check Endpoints")

```
# Check tunnel health

kubectl exec -it <pod-name> -- curl http://localhost:2000/ready



# Check metrics

kubectl exec -it <pod-name> -- curl http://localhost:2000/metrics



# Check tunnel info

kubectl exec -it <pod-name> -- cloudflared tunnel info <tunnel-name>
```

### Prometheus Monitoring[​](#prometheus-monitoring "Direct link to Prometheus Monitoring")

Enable monitoring for better debugging:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/metrics"
```

## Recovery Procedures[​](#recovery-procedures "Direct link to Recovery Procedures")

### Tunnel Recovery[​](#tunnel-recovery "Direct link to Tunnel Recovery")

```
# Restart tunnel

kubectl rollout restart deployment/<release-name>



# Check rollout status

kubectl rollout status deployment/<release-name>



# Rollback if needed

kubectl rollout undo deployment/<release-name>
```

### Credential Recovery[​](#credential-recovery "Direct link to Credential Recovery")

```
# Backup current credentials

kubectl get secret tunnel-credentials -o yaml > backup-credentials.yaml



# Regenerate credentials

cloudflared tunnel login

cloudflared tunnel create <tunnel-name>



# Update Helm release with new credentials

helm upgrade <release-name> community-charts/cloudflared \

  --set tunnelSecrets.base64EncodedConfigJsonFile="new-credentials" \

  --set tunnelSecrets.base64EncodedPemFile="new-certificate"
```

### Configuration Recovery[​](#configuration-recovery "Direct link to Configuration Recovery")

```
# Backup current configuration

kubectl get configmap <release-name> -o yaml > backup-config.yaml



# Restore configuration

kubectl apply -f backup-config.yaml



# Restart deployment

kubectl rollout restart deployment/<release-name>
```

## Getting Help[​](#getting-help "Direct link to Getting Help")

### Collecting Debug Information[​](#collecting-debug-information "Direct link to Collecting Debug Information")

```
# Collect all relevant information

kubectl get all -l app.kubernetes.io/name=cloudflared

kubectl get configmap -l app.kubernetes.io/name=cloudflared

kubectl get secret -l app.kubernetes.io/name=cloudflared

kubectl describe pod <pod-name>

kubectl logs <pod-name> --previous

kubectl exec -it <pod-name> -- env | sort
```

### Useful Commands[​](#useful-commands "Direct link to Useful Commands")

```
# Check all resources

kubectl get all -l app.kubernetes.io/name=cloudflared



# Check events

kubectl get events --sort-by='.lastTimestamp'



# Check resource usage

kubectl top pods -l app.kubernetes.io/name=cloudflared



# Check configuration

kubectl get configmap -l app.kubernetes.io/name=cloudflared

kubectl get secret -l app.kubernetes.io/name=cloudflared
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Review [configuration options](/docs/charts/cloudflared/configuration.md)
* Check [tunnel setup](/docs/charts/cloudflared/tunnel-setup.md)
* Verify [ingress configuration](/docs/charts/cloudflared/ingress-configuration.md)
* Explore [advanced configuration options](/docs/charts/cloudflared/advanced-configuration.md)


---

# Tunnel Setup Guide

This guide covers the complete process of setting up a Cloudflare Tunnel for use with the Helm chart.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

### 1. Cloudflare Account[​](#1-cloudflare-account "Direct link to 1. Cloudflare Account")

If you don't have a Cloudflare account, create one at [Cloudflare's official documentation](https://developers.cloudflare.com/fundamentals/setup/account/create-account/).

### 2. Domain Configuration[​](#2-domain-configuration "Direct link to 2. Domain Configuration")

Ensure your domain is added to your Cloudflare account and the nameservers are properly configured.

### 3. Cloudflared CLI[​](#3-cloudflared-cli "Direct link to 3. Cloudflared CLI")

Install the Cloudflared CLI tool:

```
# macOS

brew install cloudflare/cloudflare/cloudflared



# Linux

wget -q https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb

sudo dpkg -i cloudflared-linux-amd64.deb



# Windows

# Download from https://github.com/cloudflare/cloudflared/releases
```

## Creating a Tunnel[​](#creating-a-tunnel "Direct link to Creating a Tunnel")

### Step 1: Authenticate with Cloudflare[​](#step-1-authenticate-with-cloudflare "Direct link to Step 1: Authenticate with Cloudflare")

```
cloudflared tunnel login
```

This command will:

1. Open your browser to authenticate with Cloudflare
2. Download a certificate file (`cert.pem`) to `~/.cloudflared/`
3. Create the necessary permissions for tunnel management

### Step 2: Create a Tunnel[​](#step-2-create-a-tunnel "Direct link to Step 2: Create a Tunnel")

```
cloudflared tunnel create my-tunnel
```

This creates a tunnel and generates a credentials file in `~/.cloudflared/`.

### Step 3: Verify Tunnel Creation[​](#step-3-verify-tunnel-creation "Direct link to Step 3: Verify Tunnel Creation")

```
# List all tunnels

cloudflared tunnel list



# Get tunnel details

cloudflared tunnel info my-tunnel
```

## Configuring DNS Records[​](#configuring-dns-records "Direct link to Configuring DNS Records")

### Automatic DNS Configuration[​](#automatic-dns-configuration "Direct link to Automatic DNS Configuration")

```
# Create DNS record for your tunnel

cloudflared tunnel route dns my-tunnel example.com



# For wildcard subdomains

cloudflared tunnel route dns my-tunnel *.example.com
```

### Manual DNS Configuration[​](#manual-dns-configuration "Direct link to Manual DNS Configuration")

If you prefer manual DNS configuration:

1. Go to your Cloudflare dashboard

2. Navigate to DNS settings for your domain

3. Add a CNAME record:

   <!-- -->

   * **Name**: `example.com` or `*` for wildcard
   * **Target**: `<tunnel-id>.cfargotunnel.com`
   * **Proxy status**: Proxied (orange cloud)

## Preparing Tunnel Files[​](#preparing-tunnel-files "Direct link to Preparing Tunnel Files")

### Step 1: Locate Tunnel Files[​](#step-1-locate-tunnel-files "Direct link to Step 1: Locate Tunnel Files")

After creating the tunnel, you'll have these files in `~/.cloudflared/`:

* `cert.pem` - Certificate file
* `<tunnel-id>.json` - Credentials file

### Step 2: Encode Files for Helm[​](#step-2-encode-files-for-helm "Direct link to Step 2: Encode Files for Helm")

Encode the files using base64:

```
# Encode credentials JSON file

base64 -b 0 -i ~/.cloudflared/*.json



# Encode certificate PEM file

base64 -b 0 -i ~/.cloudflared/cert.pem
```

tip

Alternative encoding commands for different operating systems:

```
# macOS/Linux alternative

cat ~/.cloudflared/*.json | base64

cat ~/.cloudflared/cert.pem | base64



# Windows PowerShell

[Convert]::ToBase64String([IO.File]::ReadAllBytes("$env:USERPROFILE\.cloudflared\*.json"))

[Convert]::ToBase64String([IO.File]::ReadAllBytes("$env:USERPROFILE\.cloudflared\cert.pem"))
```

## Helm Chart Configuration[​](#helm-chart-configuration "Direct link to Helm Chart Configuration")

### Step 1: Create Values File[​](#step-1-create-values-file "Direct link to Step 1: Create Values File")

Create a `values.yaml` file with your tunnel configuration:

```
# Tunnel configuration

tunnelConfig:

  name: "my-tunnel"

  logLevel: "info"

  protocol: "auto"

  retries: 5

  connectTimeout: "30s"

  gracePeriod: "30s"



# Tunnel secrets (replace with your encoded values)

tunnelSecrets:

  base64EncodedConfigJsonFile: "your-base64-encoded-credentials"

  base64EncodedPemFile: "your-base64-encoded-certificate"



# Ingress rules

ingress:

  - hostname: example.com

    service: http://your-service.namespace.svc.cluster.local:80



  - service: http_status:404
```

### Step 2: Install the Chart[​](#step-2-install-the-chart "Direct link to Step 2: Install the Chart")

```
# Add the repository

helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update



# Install with your values

helm install my-cloudflared community-charts/cloudflared \

  -f values.yaml \

  -n <your-namespace> \

  --create-namespace
```

### Step 3: Verify Installation[​](#step-3-verify-installation "Direct link to Step 3: Verify Installation")

```
# Check pod status

kubectl get pods -l app.kubernetes.io/name=cloudflared



# Check tunnel logs

kubectl logs -f deployment/my-cloudflared



# Check tunnel status

kubectl exec -it <pod-name> -- cloudflared tunnel info my-tunnel
```

## Advanced Tunnel Configuration[​](#advanced-tunnel-configuration "Direct link to Advanced Tunnel Configuration")

### Multiple Tunnels[​](#multiple-tunnels "Direct link to Multiple Tunnels")

You can create multiple tunnels for different purposes:

```
# Create tunnels for different environments

cloudflared tunnel create production-tunnel

cloudflared tunnel create staging-tunnel

cloudflared tunnel create development-tunnel



# Configure DNS for each

cloudflared tunnel route dns production-tunnel app.example.com

cloudflared tunnel route dns staging-tunnel staging.example.com

cloudflared tunnel route dns development-tunnel dev.example.com
```

### Tunnel with Custom Configuration[​](#tunnel-with-custom-configuration "Direct link to Tunnel with Custom Configuration")

Create a custom tunnel configuration file:

```
# ~/.cloudflared/config.yml

tunnel: my-tunnel

credentials-file: /etc/cloudflared/creds/credentials.json



ingress:

  - hostname: example.com

    service: http://localhost:8080

  - hostname: api.example.com

    service: http://localhost:3000

  - service: http_status:404



metrics: 0.0.0.0:2000

loglevel: info
```

## Security Best Practices[​](#security-best-practices "Direct link to Security Best Practices")

### 1. Secure Credential Storage[​](#1-secure-credential-storage "Direct link to 1. Secure Credential Storage")

warning

Never commit tunnel credentials to version control. Use Kubernetes secrets or external secret management.

### 2. Network Policies[​](#2-network-policies "Direct link to 2. Network Policies")

Create network policies to restrict tunnel access:

```
apiVersion: networking.k8s.io/v1

kind: NetworkPolicy

metadata:

  name: cloudflared-network-policy

spec:

  podSelector:

    matchLabels:

      app.kubernetes.io/name: cloudflared

  policyTypes:

  - Ingress

  - Egress

  ingress:

  - from:

    - namespaceSelector:

        matchLabels:

          name: kube-system

    ports:

    - protocol: TCP

      port: 2000

  egress:

  - to:

    - namespaceSelector:

        matchLabels:

          name: default

    ports:

    - protocol: TCP

      port: 80

    - protocol: TCP

      port: 443
```

### 3. RBAC Configuration[​](#3-rbac-configuration "Direct link to 3. RBAC Configuration")

Configure proper RBAC for the tunnel service account:

```
apiVersion: rbac.authorization.k8s.io/v1

kind: ClusterRole

metadata:

  name: cloudflared-tunnel-role

rules:

- apiGroups: [""]

  resources: ["services", "endpoints"]

  verbs: ["get", "list", "watch"]

---

apiVersion: rbac.authorization.k8s.io/v1

kind: ClusterRoleBinding

metadata:

  name: cloudflared-tunnel-binding

subjects:

- kind: ServiceAccount

  name: my-cloudflared

  namespace: default

roleRef:

  kind: ClusterRole

  name: cloudflared-tunnel-role

  apiGroup: rbac.authorization.k8s.io
```

## Monitoring and Health Checks[​](#monitoring-and-health-checks "Direct link to Monitoring and Health Checks")

### Health Check Endpoint[​](#health-check-endpoint "Direct link to Health Check Endpoint")

The tunnel provides a health check endpoint at port 2000:

```
# Check tunnel health

kubectl exec -it <pod-name> -- curl http://localhost:2000/ready



# Check metrics

kubectl exec -it <pod-name> -- curl http://localhost:2000/metrics
```

### Prometheus Monitoring[​](#prometheus-monitoring "Direct link to Prometheus Monitoring")

Enable Prometheus monitoring:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/metrics"
```

## Troubleshooting Tunnel Setup[​](#troubleshooting-tunnel-setup "Direct link to Troubleshooting Tunnel Setup")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Authentication Failed**

   ```
   # Re-authenticate

   cloudflared tunnel login
   ```

2. **Tunnel Not Connecting**

   ```
   # Check tunnel status

   cloudflared tunnel info my-tunnel



   # Check DNS configuration

   cloudflared tunnel route ip show
   ```

3. **Certificate Issues**

   ```
   # Regenerate certificate

   cloudflared tunnel login
   ```

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Test tunnel locally

cloudflared tunnel --config ~/.cloudflared/config.yml run my-tunnel



# Check tunnel logs

cloudflared tunnel logs my-tunnel



# Verify DNS resolution

nslookup example.com

dig example.com
```

## Tunnel Management[​](#tunnel-management "Direct link to Tunnel Management")

### Updating Tunnel Configuration[​](#updating-tunnel-configuration "Direct link to Updating Tunnel Configuration")

```
# Update tunnel settings

cloudflared tunnel update my-tunnel



# Update DNS routes

cloudflared tunnel route dns my-tunnel new-subdomain.example.com
```

### Deleting Tunnels[​](#deleting-tunnels "Direct link to Deleting Tunnels")

```
# Delete DNS routes first

cloudflared tunnel route dns my-tunnel example.com --delete



# Delete the tunnel

cloudflared tunnel delete my-tunnel
```

### Backup and Recovery[​](#backup-and-recovery "Direct link to Backup and Recovery")

```
# Backup tunnel configuration

cp ~/.cloudflared/*.json ./backup/

cp ~/.cloudflared/cert.pem ./backup/



# Restore tunnel configuration

cp ./backup/*.json ~/.cloudflared/

cp ./backup/cert.pem ~/.cloudflared/
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Configure [ingress rules](/docs/charts/cloudflared/ingress-configuration.md)
* Set up [advanced configuration options](/docs/charts/cloudflared/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/cloudflared/troubleshooting.md)
* Review [configuration options](/docs/charts/cloudflared/configuration.md)


---

# Cloudflared Chart Usage Guide

[Cloudflared](https://github.com/cloudflare/cloudflared) is a tool from Cloudflare to create secure tunnels from your Kubernetes cluster to the Cloudflare network, exposing services without opening public ports.

* **Official Website:** <https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/>
* **GitHub Repository:** <https://github.com/cloudflare/cloudflared>
* **Documentation:** [Cloudflare Tunnel Docs](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/)
* **ArtifactHub:** [Cloudflared Helm Chart](https://artifacthub.io/packages/helm/community-charts/cloudflared)

## Why Use This Chart?[​](#why-use-this-chart "Direct link to Why Use This Chart?")

* **Secure Access**: Expose Kubernetes services securely without opening public ports
* **No Ingress Required**: Bypass traditional ingress controllers and load balancers
* **Global Network**: Leverage Cloudflare's global network for optimal performance
* **Community Maintained**: Open-source Helm chart with active community support
* **Easy Deployment**: Simple Helm-based deployment with comprehensive configuration options

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

Before deploying the Cloudflared Tunnel chart, ensure you have:

1. **Kubernetes Cluster**: Version 1.21 or later
2. **Helm**: Version 3.0 or later
3. **Cloudflare Account**: With a domain added and configured
4. **Cloudflared CLI**: For tunnel setup and management

## Quick Start[​](#quick-start "Direct link to Quick Start")

### 1. Add the Helm Repository[​](#1-add-the-helm-repository "Direct link to 1. Add the Helm Repository")

```
helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update
```

### 2. Create a Tunnel[​](#2-create-a-tunnel "Direct link to 2. Create a Tunnel")

```
# Authenticate with Cloudflare

cloudflared tunnel login



# Create a tunnel

cloudflared tunnel create my-tunnel



# Configure DNS (optional)

cloudflared tunnel route dns my-tunnel example.com
```

### 3. Prepare Tunnel Files[​](#3-prepare-tunnel-files "Direct link to 3. Prepare Tunnel Files")

```
# Encode credentials file

base64 -b 0 -i ~/.cloudflared/*.json



# Encode certificate file

base64 -b 0 -i ~/.cloudflared/cert.pem
```

### 4. Create Values File[​](#4-create-values-file "Direct link to 4. Create Values File")

Create a `values.yaml` file:

```
# Tunnel configuration

tunnelConfig:

  name: "my-tunnel"

  logLevel: "info"

  protocol: "auto"

  retries: 5

  connectTimeout: "30s"

  gracePeriod: "30s"



# Tunnel secrets (replace with your encoded values)

tunnelSecrets:

  base64EncodedConfigJsonFile: "your-base64-encoded-credentials"

  base64EncodedPemFile: "your-base64-encoded-certificate"



# Ingress rules

ingress:

  - hostname: example.com

    service: http://your-service.namespace.svc.cluster.local:80



  - service: http_status:404
```

### 5. Install the Chart[​](#5-install-the-chart "Direct link to 5. Install the Chart")

```
helm install my-cloudflared community-charts/cloudflared \

  -f values.yaml \

  -n <your-namespace> \

  --create-namespace
```

### 6. Verify Installation[​](#6-verify-installation "Direct link to 6. Verify Installation")

```
# Check pod status

kubectl get pods -l app.kubernetes.io/name=cloudflared



# Check tunnel logs

kubectl logs -f deployment/my-cloudflared



# Test access

curl https://example.com
```

## Deployment Modes[​](#deployment-modes "Direct link to Deployment Modes")

### DaemonSet Mode (Recommended)[​](#daemonset-mode-recommended "Direct link to DaemonSet Mode (Recommended)")

Deploy to all nodes for high availability:

```
replica:

  allNodes: true
```

### Deployment Mode[​](#deployment-mode "Direct link to Deployment Mode")

Deploy specific number of replicas:

```
replica:

  allNodes: false

  count: 3
```

## Basic Configuration Examples[​](#basic-configuration-examples "Direct link to Basic Configuration Examples")

### Simple Web Application[​](#simple-web-application "Direct link to Simple Web Application")

```
tunnelConfig:

  name: "web-app-tunnel"

  logLevel: "info"



tunnelSecrets:

  base64EncodedConfigJsonFile: "your-credentials"

  base64EncodedPemFile: "your-certificate"



ingress:

  - hostname: app.example.com

    service: http://web-service.default.svc.cluster.local:80



  - service: http_status:404
```

### Multi-Service Application[​](#multi-service-application "Direct link to Multi-Service Application")

```
tunnelConfig:

  name: "multi-service-tunnel"

  logLevel: "info"



tunnelSecrets:

  base64EncodedConfigJsonFile: "your-credentials"

  base64EncodedPemFile: "your-certificate"



ingress:

  - hostname: app.example.com

    service: http://frontend-service.default.svc.cluster.local:3000



  - hostname: api.example.com

    service: http://api-service.default.svc.cluster.local:8080



  - hostname: admin.example.com

    service: http://admin-service.default.svc.cluster.local:8080



  - service: http_status:404
```

### Development Environment[​](#development-environment "Direct link to Development Environment")

```
replica:

  allNodes: false

  count: 1



tunnelConfig:

  name: "dev-tunnel"

  logLevel: "debug"



tunnelSecrets:

  base64EncodedConfigJsonFile: "your-credentials"

  base64EncodedPemFile: "your-certificate"



ingress:

  - hostname: dev.example.com

    service: http://dev-service.default.svc.cluster.local:3000



  - hostname: dev-api.example.com

    service: http://dev-api-service.default.svc.cluster.local:8080



  - service: http_status:404



resources:

  limits:

    cpu: "200m"

    memory: "128Mi"

  requests:

    cpu: "100m"

    memory: "64Mi"
```

## Common Operations[​](#common-operations "Direct link to Common Operations")

### Upgrading the Chart[​](#upgrading-the-chart "Direct link to Upgrading the Chart")

```
# Update repository

helm repo update



# Upgrade installation

helm upgrade my-cloudflared community-charts/cloudflared \

  -f values.yaml \

  -n <your-namespace>
```

### Scaling the Deployment[​](#scaling-the-deployment "Direct link to Scaling the Deployment")

```
# Scale to specific number of replicas

kubectl scale deployment my-cloudflared --replicas=3



# Or update values and upgrade

helm upgrade my-cloudflared community-charts/cloudflared \

  --set replica.count=3 \

  -n <your-namespace>
```

### Rolling Back[​](#rolling-back "Direct link to Rolling Back")

```
# Rollback to previous version

helm rollback my-cloudflared -n <your-namespace>



# Or rollback to specific revision

helm rollback my-cloudflared 2 -n <your-namespace>
```

### Uninstalling[​](#uninstalling "Direct link to Uninstalling")

```
# Uninstall the chart

helm uninstall my-cloudflared -n <your-namespace>



# Delete tunnel (optional)

cloudflared tunnel delete my-tunnel
```

## Monitoring and Health Checks[​](#monitoring-and-health-checks "Direct link to Monitoring and Health Checks")

### Health Check Endpoint[​](#health-check-endpoint "Direct link to Health Check Endpoint")

The tunnel provides a health check endpoint:

```
# Check tunnel health

kubectl exec -it <pod-name> -- curl http://localhost:2000/ready



# Check metrics

kubectl exec -it <pod-name> -- curl http://localhost:2000/metrics
```

### Prometheus Monitoring[​](#prometheus-monitoring "Direct link to Prometheus Monitoring")

Enable Prometheus monitoring:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/metrics"
```

### Log Monitoring[​](#log-monitoring "Direct link to Log Monitoring")

```
# Follow tunnel logs

kubectl logs -f deployment/my-cloudflared



# Check specific log levels

kubectl logs deployment/my-cloudflared | grep -i "error\|warn"
```

## Security Considerations[​](#security-considerations "Direct link to Security Considerations")

### Network Policies[​](#network-policies "Direct link to Network Policies")

Create network policies to restrict access:

```
apiVersion: networking.k8s.io/v1

kind: NetworkPolicy

metadata:

  name: cloudflared-network-policy

spec:

  podSelector:

    matchLabels:

      app.kubernetes.io/name: cloudflared

  policyTypes:

  - Ingress

  - Egress

  ingress:

  - from:

    - namespaceSelector:

        matchLabels:

          name: kube-system

    ports:

    - protocol: TCP

      port: 2000

  egress:

  - to:

    - namespaceSelector:

        matchLabels:

          name: default

    ports:

    - protocol: TCP

      port: 80

    - protocol: TCP

      port: 443
```

### RBAC Configuration[​](#rbac-configuration "Direct link to RBAC Configuration")

Configure proper RBAC:

```
serviceAccount:

  create: true

  name: "cloudflared-service-account"

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/cloudflared-role"
```

## Best Practices[​](#best-practices "Direct link to Best Practices")

### 1. Use DaemonSet for High Availability[​](#1-use-daemonset-for-high-availability "Direct link to 1. Use DaemonSet for High Availability")

```
replica:

  allNodes: true
```

### 2. Configure Resource Limits[​](#2-configure-resource-limits "Direct link to 2. Configure Resource Limits")

```
resources:

  limits:

    cpu: "500m"

    memory: "256Mi"

  requests:

    cpu: "200m"

    memory: "128Mi"
```

### 3. Enable Monitoring[​](#3-enable-monitoring "Direct link to 3. Enable Monitoring")

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "2000"

  prometheus.io/path: "/metrics"
```

### 4. Use Specific Hostnames[​](#4-use-specific-hostnames "Direct link to 4. Use Specific Hostnames")

```
ingress:

  - hostname: app.example.com

    service: http://app-service.default.svc.cluster.local:80



  - hostname: api.example.com

    service: http://api-service.default.svc.cluster.local:8080
```

### 5. Always Include Error Handler[​](#5-always-include-error-handler "Direct link to 5. Always Include Error Handler")

```
ingress:

  # Your service rules here

  - service: http_status:404  # Required
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Pod Not Starting**: Check tunnel credentials and configuration
2. **Service Not Accessible**: Verify ingress rules and service endpoints
3. **High Latency**: Optimize protocol and connection settings
4. **Authentication Errors**: Regenerate tunnel credentials

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check pod status

kubectl get pods -l app.kubernetes.io/name=cloudflared



# Check tunnel logs

kubectl logs -f deployment/my-cloudflared



# Check tunnel status

kubectl exec -it <pod-name> -- cloudflared tunnel info my-tunnel



# Test service connectivity

kubectl exec -it <pod-name> -- curl http://service-name.namespace.svc.cluster.local:port
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [tunnel setup](/docs/charts/cloudflared/tunnel-setup.md)
* Configure [ingress rules](/docs/charts/cloudflared/ingress-configuration.md)
* Explore [advanced configuration options](/docs/charts/cloudflared/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/cloudflared/troubleshooting.md)
* Review [configuration options](/docs/charts/cloudflared/configuration.md)


---

# Advanced Configuration

This guide covers advanced options for customizing your Drone deployment on Kubernetes.

## Kubernetes Runner[​](#kubernetes-runner "Direct link to Kubernetes Runner")

* Enable/disable runner: `kubeRunner.enabled`

* Set runner replicas: `kubeRunner.replicaCount`

* Set default build namespace: `kubeRunner.env.DRONE_NAMESPACE_DEFAULT`

* Custom runner image:

  ```
  kubeRunner:

    image:

      repository: drone/drone-runner-kube

      tag: 1.0.0-rc.3
  ```

## RBAC and Namespaces[​](#rbac-and-namespaces "Direct link to RBAC and Namespaces")

* Control which namespaces the runner can build in:

  ```
  kubeRunner:

    rbac:

      buildNamespaces:

        - default

        - ci-builds
  ```

## Customizing Pod Specs[​](#customizing-pod-specs "Direct link to Customizing Pod Specs")

* Node selectors, tolerations, affinity:

  <!-- -->

  * `server.nodeSelector`, `server.tolerations`, `server.affinity`
  * `kubeRunner.nodeSelector`, `kubeRunner.tolerations`, `kubeRunner.affinity`

* Extra volumes and mounts:

  <!-- -->

  * `server.extraVolumes`, `server.extraVolumeMounts`
  * `kubeRunner.extraVolumes`, `kubeRunner.extraVolumeMounts`

## Service and Ingress[​](#service-and-ingress "Direct link to Service and Ingress")

* Customize service type/port:

  <!-- -->

  * `server.service.type`, `server.service.port`
  * `kubeRunner.service.type`, `kubeRunner.service.port`

* Ingress options for both server and runner

## Security Contexts[​](#security-contexts "Direct link to Security Contexts")

* Harden containers with `securityContext` and `podSecurityContext` for both server and runner

## Example: Customizing Security Context[​](#example-customizing-security-context "Direct link to Example: Customizing Security Context")

```
server:

  securityContext:

    runAsNonRoot: true

    readOnlyRootFilesystem: true

kubeRunner:

  securityContext:

    runAsNonRoot: true

    readOnlyRootFilesystem: true
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Configuration](/docs/charts/drone/configuration.md)
* [Authentication](/docs/charts/drone/authentication.md)
* [Storage](/docs/charts/drone/storage.md)
* [Troubleshooting](/docs/charts/drone/troubleshooting.md)


---

# Authentication Guide

Drone supports multiple authentication providers (GitHub, GitLab, Gitea, Bitbucket, etc). This guide explains how to configure them securely using the Helm chart.

## Supported Providers[​](#supported-providers "Direct link to Supported Providers")

* GitHub / GitHub Enterprise
* GitLab
* Gitea
* Bitbucket Cloud / Server
* Gitee
* Gogs

## Example: GitHub OAuth[​](#example-github-oauth "Direct link to Example: GitHub OAuth")

Set the following secrets (via `values.yaml` or `--set`):

```
server:

  secrets:

    DRONE_GITHUB_CLIENT_ID: <your-client-id>

    DRONE_GITHUB_CLIENT_SECRET: <your-client-secret>
```

## Example: Gitea[​](#example-gitea "Direct link to Example: Gitea")

```
server:

  secrets:

    DRONE_GITEA_CLIENT_ID: <your-client-id>

    DRONE_GITEA_CLIENT_SECRET: <your-client-secret>

    DRONE_GITEA_SERVER: https://gitea.example.com
```

## User Management[​](#user-management "Direct link to User Management")

* Create an initial admin user:

  ```
  server:

    secrets:

      DRONE_USER_CREATE: "username:adminuser,admin:true"
  ```

* Restrict user access:

  ```
  server:

    secrets:

      DRONE_USER_FILTER: adminuser
  ```

warning

Never store secrets in your git repository. Use Kubernetes secrets or Helm `--set` for sensitive values.

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Configuration](/docs/charts/drone/configuration.md)
* [Storage](/docs/charts/drone/storage.md)
* [Advanced Configuration](/docs/charts/drone/advanced-configuration.md)
* [Troubleshooting](/docs/charts/drone/troubleshooting.md)


---

# Configuration Guide

This guide covers all major configuration options for the Drone Helm chart, including server and runner settings, environment variables, and best practices for production deployments.

## Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

Set the most important values in your `values.yaml` or via `--set`:

```
server:

  env:

    DRONE_SERVER_HOST: drone.example.com

    DRONE_SERVER_PROTO: https

  ingress:

    enabled: true

    hosts:

      - host: drone.example.com

        paths:

          - path: /

            pathType: ImplementationSpecific
```

## Common Parameters[​](#common-parameters "Direct link to Common Parameters")

| Parameter                         | Description                                   | Default             |
| --------------------------------- | --------------------------------------------- | ------------------- |
| `server.env.DRONE_SERVER_HOST`    | Drone server hostname (no protocol)           | `drone.example.com` |
| `server.env.DRONE_SERVER_PROTO`   | Protocol for Drone server (`http` or `https`) | `http`              |
| `server.replicaCount`             | Number of Drone server replicas               | `1`                 |
| `server.image.repository`         | Drone server image                            | `drone/drone`       |
| `server.image.tag`                | Drone server image tag                        | Chart app version   |
| `server.persistentVolume.enabled` | Enable persistent storage                     | `true`              |
| `server.persistentVolume.size`    | PVC size                                      | `8Gi`               |
| `kubeRunner.enabled`              | Enable Kubernetes runner                      | `true`              |
| `kubeRunner.replicaCount`         | Number of runner replicas                     | `1`                 |

## Advanced Configuration[​](#advanced-configuration "Direct link to Advanced Configuration")

* **Node selectors, tolerations, affinity:**

  * `server.nodeSelector`, `server.tolerations`, `server.affinity`
  * `kubeRunner.nodeSelector`, `kubeRunner.tolerations`, `kubeRunner.affinity`

* **Resource requests/limits:**
  * `server.resources`, `kubeRunner.resources`

* **Custom ServiceAccount:**
  * `server.serviceAccount.*`, `kubeRunner.serviceAccount.*`

* **Ingress TLS:**
  * `server.ingress.tls`, `kubeRunner.ingress.tls`

## Example: Customizing the Runner[​](#example-customizing-the-runner "Direct link to Example: Customizing the Runner")

```
kubeRunner:

  enabled: true

  replicaCount: 2

  env:

    DRONE_NAMESPACE_DEFAULT: ci-builds

  ingress:

    enabled: true

    hosts:

      - host: runner.example.com

        paths:

          - path: /

            pathType: ImplementationSpecific
```

tip

For a full list of options, see the chart's `values.yaml` and `values.schema.json`.

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Authentication](/docs/charts/drone/authentication.md)
* [Storage](/docs/charts/drone/storage.md)
* [Advanced Configuration](/docs/charts/drone/advanced-configuration.md)
* [Troubleshooting](/docs/charts/drone/troubleshooting.md)


---

# Storage Guide

This guide covers persistent storage and database configuration for Drone deployments on Kubernetes.

## Persistent Volume (PVC)[​](#persistent-volume-pvc "Direct link to Persistent Volume (PVC)")

By default, Drone uses a PersistentVolumeClaim (PVC) for stateful data (e.g., SQLite database, logs):

```
server:

  persistentVolume:

    enabled: true

    size: 8Gi

    storageClass: ""

    accessModes:

      - ReadWriteOnce
```

* Set `enabled: false` if using an external database (Postgres, MySQL).
* Use `existingClaim` to use a pre-created PVC.

## Database Backend[​](#database-backend "Direct link to Database Backend")

Drone supports SQLite (default), Postgres, and MySQL. To use an external DB:

```
server:

  env:

    DRONE_DATABASE_DRIVER: postgres

  secrets:

    DRONE_DATABASE_DATASOURCE: "postgres://user:pass@host:5432/dbname?sslmode=disable"
```

* Supported drivers: `sqlite3`, `postgres`, `mysql`
* For production, use Postgres or MySQL.

## Encryption Secret[​](#encryption-secret "Direct link to Encryption Secret")

Set a database encryption secret for sensitive data:

```
server:

  secrets:

    DRONE_DATABASE_SECRET: <random-hex>
```

Generate with: `openssl rand -hex 16`

tip

Never store secrets in git. Use Kubernetes secrets or Helm `--set` for sensitive values.

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Configuration](/docs/charts/drone/configuration.md)
* [Authentication](/docs/charts/drone/authentication.md)
* [Advanced Configuration](/docs/charts/drone/advanced-configuration.md)
* [Troubleshooting](/docs/charts/drone/troubleshooting.md)


---

# Troubleshooting Guide

This guide helps you diagnose and resolve common issues with Drone deployments on Kubernetes.

## Common Issues[​](#common-issues "Direct link to Common Issues")

### 1. Drone Server Not Starting[​](#1-drone-server-not-starting "Direct link to 1. Drone Server Not Starting")

* Check pod logs: `kubectl logs <drone-server-pod>`
* Ensure required environment variables are set (`DRONE_SERVER_HOST`, `DRONE_SERVER_PROTO`)
* Check persistent volume status: `kubectl get pvc`

### 2. Runner Not Connecting[​](#2-runner-not-connecting "Direct link to 2. Runner Not Connecting")

* Ensure `DRONE_RPC_SECRET` matches between server and runner
* Check runner pod logs
* Verify network connectivity between runner and server

### 3. Authentication Failures[​](#3-authentication-failures "Direct link to 3. Authentication Failures")

* Double-check OAuth client IDs/secrets
* Ensure callback URLs are correct in your OAuth provider

### 4. Database Issues[​](#4-database-issues "Direct link to 4. Database Issues")

* Check DB connection string in `DRONE_DATABASE_DATASOURCE`
* Ensure DB is reachable from the cluster

## Useful Commands[​](#useful-commands "Direct link to Useful Commands")

```
kubectl get pods -n <namespace>

kubectl describe pod <pod-name> -n <namespace>

kubectl logs <pod-name> -n <namespace>
```

tip

For more help, check the [Drone community site](https://discourse.drone.io/).

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Configuration](/docs/charts/drone/configuration.md)
* [Authentication](/docs/charts/drone/authentication.md)
* [Storage](/docs/charts/drone/storage.md)
* [Advanced Configuration](/docs/charts/drone/advanced-configuration.md)


---

# Drone Chart Usage Guide

[Drone](https://drone.io) is a modern Continuous Integration and Continuous Deployment (CI/CD) platform built on container technology. This chart lets you deploy Drone on Kubernetes easily.

* **Official Website:** <https://drone.io>
* **GitHub Repository:** <https://github.com/harness/drone>
* **Documentation:** <https://docs.drone.io>
* **ArtifactHub:** [Drone Helm Chart](https://artifacthub.io/packages/helm/community-charts/drone)

## Why use this chart?[​](#why-use-this-chart "Direct link to Why use this chart?")

* Run CI/CD pipelines in your own Kubernetes cluster
* Community-maintained and up-to-date
* Supports plugins and custom runners

## Installation[​](#installation "Direct link to Installation")

```
helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update

helm install my-drone community-charts/drone -n <your-namespace>
```

Replace `<your-namespace>` with your target namespace.

tip

For advanced configuration, see the [Configuration](/docs/charts/drone/configuration.md) page.

## Upgrading[​](#upgrading "Direct link to Upgrading")

```
helm upgrade my-drone community-charts/drone -n <your-namespace>
```

## Uninstalling[​](#uninstalling "Direct link to Uninstalling")

```
helm uninstall my-drone -n <your-namespace>
```

This removes all Kubernetes resources created by the chart.

## Example: Install with Gitea and Postgres[​](#example-install-with-gitea-and-postgres "Direct link to Example: Install with Gitea and Postgres")

```
server:

  ingress:

    enabled: true

    hosts:

      - host: drone.example.com

        paths:

          - path: /

            pathType: ImplementationSpecific

  env:

    DRONE_SERVER_HOST: drone.example.com

    DRONE_SERVER_PROTO: http

    DRONE_DATABASE_DRIVER: postgres

    DRONE_GITEA_SERVER: http://gitea.example.com

  secrets:

    DRONE_DATABASE_DATASOURCE: "postgres://postgres:postgres@postgres-service:5432/postgres?sslmode=disable"

    DRONE_GITEA_CLIENT_ID: <client-id>

    DRONE_GITEA_CLIENT_SECRET: <client-secret>

    DRONE_USER_CREATE: "username:testuser,admin:true"

    DRONE_USER_FILTER: testuser
```

warning

Never store secrets in your git repository. Use Kubernetes secrets or Helm `--set` for sensitive values.

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Configuration](/docs/charts/drone/configuration.md)
* [Authentication](/docs/charts/drone/authentication.md)
* [Storage](/docs/charts/drone/storage.md)
* [Advanced Configuration](/docs/charts/drone/advanced-configuration.md)
* [Troubleshooting](/docs/charts/drone/troubleshooting.md)


---

# Authentication Configuration

This guide covers configuring authentication for MLflow to secure access to your MLflow tracking server. MLflow supports various authentication methods including basic authentication, and LDAP integration.

warning

**Security Requirement:** Authentication should always be enabled in production environments to secure your MLflow instance and protect sensitive ML data.

danger

**Production Security:** Never deploy MLflow without authentication in production. Unsecured MLflow instances can expose sensitive model data and credentials.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

info

**Setup Requirements:** Ensure you have the necessary infrastructure and access before configuring authentication.

* MLflow deployed on Kubernetes
* Access to MLflow configuration
* Authentication provider setup (if using LDAP)

tip

**Planning:** Choose the authentication method that best fits your organization's security policies and infrastructure.

## Basic Authentication[​](#basic-authentication "Direct link to Basic Authentication")

tip

**Quick Security:** Basic authentication is the simplest way to secure MLflow and is suitable for small teams or development environments.

warning

**Basic Auth Limitations:** Basic authentication stores credentials in plain text and doesn't support advanced features like password policies or account lockout.

### 1. Simple Basic Authentication[​](#1-simple-basic-authentication "Direct link to 1. Simple Basic Authentication")

```
auth:

  enabled: true

  adminUsername: admin

  adminPassword: S3cr3+
```

warning

**Password Security:** Use strong, unique passwords and consider using Kubernetes secrets instead of hardcoding credentials.

danger

**Credential Management:** Never hardcode passwords in configuration files. Use Kubernetes secrets for all sensitive data.

### 2. Create User Credentials Secret[​](#2-create-user-credentials-secret "Direct link to 2. Create User Credentials Secret")

```
kubectl create secret generic mlflow-auth \

  --namespace mlflow \

  --from-literal=admin-user=admin \

  --from-literal=admin-password=your-secure-password
```

tip

**Secret Management:** Using Kubernetes secrets provides better security and makes credential rotation easier.

### 3. Configure Basic Authentication with Secret[​](#3-configure-basic-authentication-with-secret "Direct link to 3. Configure Basic Authentication with Secret")

```
auth:

  enabled: true

  adminUsername: admin

  adminPassword: your-secure-password

  existingAdminSecret:

    name: "mlflow-auth"

    usernameKey: "admin-user"

    passwordKey: "admin-password"

  defaultPermission: READ

  appName: basic-auth

  authorizationFunction: mlflow.server.auth:authenticate_request_basic_auth

  configPath: /etc/mlflow/auth/

  configFile: basic_auth.ini

  sqliteFile: basic_auth.db

  sqliteFullPath: ""
```

info

**Permission Levels:** Configure appropriate default permissions based on your team's access requirements.

## PostgreSQL-Based Centralized Authentication[​](#postgresql-based-centralized-authentication "Direct link to PostgreSQL-Based Centralized Authentication")

<!-- -->

info

**Enterprise Authentication:** PostgreSQL-based authentication provides centralized user management and is suitable for larger organizations.

tip

**Scalability:** PostgreSQL authentication scales better than SQLite for organizations with many users.

### 1. Configure PostgreSQL Auth Backend[​](#1-configure-postgresql-auth-backend "Direct link to 1. Configure PostgreSQL Auth Backend")

```
auth:

  enabled: true

  adminUsername: admin

  adminPassword: S3cr3+

  postgres:

    enabled: true

    host: postgresql--auth-instance1.abcdef1234.eu-central-1.rds.amazonaws.com

    port: 5432

    database: auth

    user: mlflowauth

    password: A4m1nPa33w0rd!

    driver: psycopg2
```

warning

**Database Security:** Ensure the PostgreSQL instance is properly secured with network policies and strong authentication.

### 2. Create Auth Database[​](#2-create-auth-database "Direct link to 2. Create Auth Database")

```
CREATE DATABASE auth;

CREATE USER mlflowauth WITH PASSWORD 'A4m1nPa33w0rd!';

GRANT ALL PRIVILEGES ON DATABASE auth TO mlflowauth;
```

tip

**Database Setup:** Use dedicated databases for authentication to isolate security concerns and simplify management.

## LDAP Authentication[​](#ldap-authentication "Direct link to LDAP Authentication")

<!-- -->

info

**Enterprise Integration:** LDAP authentication integrates MLflow with existing enterprise directory services for centralized user management.

tip

**Single Sign-On:** LDAP integration enables users to access MLflow with their existing enterprise credentials.

### 1. Basic LDAP Configuration[​](#1-basic-ldap-configuration "Direct link to 1. Basic LDAP Configuration")

```
ldapAuth:

  enabled: true

  uri: ldap://lldap:3890/dc=mlflow,dc=test

  tlsVerification: required

  lookupBind: uid=%s,ou=people,dc=mlflow,dc=test

  groupAttribute: dn

  searchBaseDistinguishedName: ou=groups,dc=mlflow,dc=test

  searchFilter: "(&(objectclass=groupOfUniqueNames)(uniquemember=%s))"

  adminGroupDistinguishedName: cn=test-admin,ou=groups,dc=mlflow,dc=test

  userGroupDistinguishedName: cn=test-user,ou=groups,dc=mlflow,dc=test
```

warning

**LDAP Security:** Always use TLS/SSL for LDAP connections in production to protect user credentials in transit.

### 2. LDAP with Self-Signed CA Certificate[​](#2-ldap-with-self-signed-ca-certificate "Direct link to 2. LDAP with Self-Signed CA Certificate")

If you use self-signed certificate for your LDAP server:

```
ldapAuth:

  enabled: true

  uri: ldap://lldap:3890/dc=mlflow,dc=test

  tlsVerification: required

  lookupBind: uid=%s,ou=people,dc=mlflow,dc=test

  groupAttribute: dn

  searchBaseDistinguishedName: ou=groups,dc=mlflow,dc=test

  searchFilter: "(&(objectclass=groupOfUniqueNames)(uniquemember=%s))"

  adminGroupDistinguishedName: cn=test-admin,ou=groups,dc=mlflow,dc=test

  userGroupDistinguishedName: cn=test-user,ou=groups,dc=mlflow,dc=test

  encodedTrustedCACertificate: "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURoRENDQW15Z0F3SUJBZ0lSQUx1a3VyZnlCMFF0Z1FtbnphZDlMNWN3RFFZSktvWklodmNOQVFFTEJRQXcKU3pFZ01CNEdBMVVFQXd3WFRVeEdiRzkzSUV4RVFWQXRVMU5NTFZSbGMzUWdRMEV4RHpBTkJnTlZCQW9NQmsxTQpSbXh2ZHpFV01CUUdBMVVFQ3d3TlRFUkJVQzFUVTB3dFZHVnpkREFlRncweU5UQXpNRE14TnpJMU1qVmFGdzB5Ck5UQXpNRFF4TnpJMU1qVmFNRXN4SURBZUJnTlZCQU1NRjAxTVJteHZkeUJNUkVGUUxWTlRUQzFVWlhOMElFTkIKTVE4d0RRWURWUVFLREFaTlRFWnNiM2N4RmpBVUJnTlZCQXNNRFV4RVFWQXRVMU5NTFZSbGMzUXdnZ0VpTUEwRwpDU3FHU0liM0RRRUJBUVVBQTRJQkR3QXdnZ0VLQW9JQkFRRHNBNDc1NkRrZlVXRThZZjRHN0Z4ZFJkL0pnNXNkCjRJUVp1K3ZQcDRMTm5uM3E5VWlZeUtHZkVFRDJTMnRvYUVTS1VNakJyYWVRd3crUDV0dDVHcjNMQ3JQUmpjZTUKQ2xuMEh3NE5pRGJ5bkhWcDkxWXRjdHJObWtGMFRGdUYxNVE5OUMyR1lpbmNYUW93THduMWZXN2pTZjFuU3N1Kwpvek0veHFUa2FyQndtcVFkYTRlcW56cG5Xa2ZqL2ZHQTNVcnpwMHV6ZG1ZdnNhcmtiTkt0aGZSWTJ4UDhQZGc0Cm15dDJ6SmlycjN2MEo1OFNHeFN6ZWlab0tYUTNtTW5hRDZGTUVTcEg5THUydDVTRUVPZjlubFJLS2l4UzF0aWMKVHJUMDkzUVNKcWNRRkMyNTNwWmF1ZkpQNWR2SlVIR0NvcHFzVU5xc0Jkd2Ivd1grNnJFQm5YYUJBZ01CQUFHagpZekJoTUE4R0ExVWRFd0VCL3dRRk1BTUJBZjh3RGdZRFZSMFBBUUgvQkFRREFnRUdNQjBHQTFVZERnUVdCQlJsCnZVRmphb0c5NU1sWmxBSUs2SDRsaVlvMUNqQWZCZ05WSFNNRUdEQVdnQlJsdlVGamFvRzk1TWxabEFJSzZINGwKaVlvMUNqQU5CZ2txaGtpRzl3MEJBUXNGQUFPQ0FRRUFCNy96YWtlOHB6QWF3eHhvUW5mV3N1MkpSNWhyZkpjcQpjdCt1UEVnSWdnc3lFSmRGbndvbSt2UUV3a3NnT2tEYk10UGZnWTdRUVdUeHo4d1pQOXJDZVZaVUJ0T1FrdytKCjZCR2NLc1gwVnl5bUx5a1VOWUF5U2pEUE1Ma0NES2ZsRyt2eWFPWTZQbFdkZVJJTTVRMVZRL1B1SmQrbCtobEgKd2dFbU1RK2VjeVB2Wkhnd0t3cE41Zzh3YzI3bjI3RURqS29wUHpFMXpzRFN0MjFwUnMvcUdnZXZ6QTl2RlB5eAprWXdXdWJkblQ5NkwyTUUrVjcwTmJzbWt5ekl2T2NzajBlRnE0Z2EyNUQxQ2FhLzlyUnVOSlhwanYyQndYUm1tClNDNnBIV1dRWnh3NDRLQnJCM09EM1hLS25rMU94RFBDUzVwMzN2SHo4ZEZOMHNzb3EwV1VPUT09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K"
```

warning

**Certificate Security:** Always use proper TLS certificates in production. Self-signed certificates should only be used for testing.

danger

**Certificate Management:** Store CA certificates securely and rotate them regularly according to your security policies.

### 3. LDAP with External CA Certificate Secret[​](#3-ldap-with-external-ca-certificate-secret "Direct link to 3. LDAP with External CA Certificate Secret")

If you already stored your self-signed CA certificate in an external secret:

```
ldapAuth:

  enabled: true

  uri: ldap://lldap:3890/dc=mlflow,dc=test

  tlsVerification: required

  lookupBind: uid=%s,ou=people,dc=mlflow,dc=test

  groupAttribute: dn

  searchBaseDistinguishedName: ou=groups,dc=mlflow,dc=test

  searchFilter: "(&(objectclass=groupOfUniqueNames)(uniquemember=%s))"

  adminGroupDistinguishedName: cn=test-admin,ou=groups,dc=mlflow,dc=test

  userGroupDistinguishedName: cn=test-user,ou=groups,dc=mlflow,dc=test

  externalSecretForTrustedCACertificate: external-ca-certificate-secret
```

tip

**Secret Management:** Using external secrets for certificates provides better security and easier certificate rotation.

## Complete Configuration Examples[​](#complete-configuration-examples "Direct link to Complete Configuration Examples")

info

**Production Examples:** These examples demonstrate complete authentication setups for different enterprise scenarios.

### Basic Authentication with PostgreSQL Backend[​](#basic-authentication-with-postgresql-backend "Direct link to Basic Authentication with PostgreSQL Backend")

<!-- -->

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



auth:

  enabled: true

  adminUsername: admin

  adminPassword: S3cr3+

  postgres:

    enabled: true

    host: postgresql-auth-instance.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: auth

    user: mlflowauth

    password: A4m1nPa33w0rd!

    driver: psycopg2



ingress:

  enabled: true

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: ImplementationSpecific
```

### LDAP Authentication with PostgreSQL Backend[​](#ldap-authentication-with-postgresql-backend "Direct link to LDAP Authentication with PostgreSQL Backend")

<!-- -->

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



ldapAuth:

  enabled: true

  uri: ldap://lldap:3890/dc=mlflow,dc=test

  tlsVerification: required

  lookupBind: uid=%s,ou=people,dc=mlflow,dc=test

  groupAttribute: dn

  searchBaseDistinguishedName: ou=groups,dc=mlflow,dc=test

  searchFilter: "(&(objectclass=groupOfUniqueNames)(uniquemember=%s))"

  adminGroupDistinguishedName: cn=test-admin,ou=groups,dc=mlflow,dc=test

  userGroupDistinguishedName: cn=test-user,ou=groups,dc=mlflow,dc=test
```

### Production Authentication with S3 and Monitoring[​](#production-authentication-with-s3-and-monitoring "Direct link to Production Authentication with S3 and Monitoring")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  s3:

    enabled: true

    bucket: my-mlflow-artifact-root-backend

    awsAccessKeyId: a1b2c3d4

    awsSecretAccessKey: a1b2c3d4



auth:

  enabled: true

  adminUsername: admin

  adminPassword: S3cr3+

  postgres:

    enabled: true

    host: postgresql--auth-instance1.abcdef1234.eu-central-1.rds.amazonaws.com

    port: 5432

    database: auth

    user: mlflowauth

    password: A4m1nPa33w0rd!

    driver: psycopg2



serviceMonitor:

  enabled: true

  namespace: monitoring

  interval: 30s

  telemetryPath: /metrics

  labels:

    release: prometheus

  timeout: 10s

  targetLabels: []



ingress:

  enabled: true

  className: nginx

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: mlflow-tls

      hosts:

        - mlflow.your-domain.com
```

## Ingress with Authentication[​](#ingress-with-authentication "Direct link to Ingress with Authentication")

### 1. Configure Ingress with Auth[​](#1-configure-ingress-with-auth "Direct link to 1. Configure Ingress with Auth")

```
ingress:

  enabled: true

  className: nginx

  annotations:

    nginx.ingress.kubernetes.io/auth-type: basic

    nginx.ingress.kubernetes.io/auth-secret: mlflow-auth

    nginx.ingress.kubernetes.io/auth-realm: "MLflow Authentication Required"

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: Prefix
```

### 2. Create Ingress Auth Secret[​](#2-create-ingress-auth-secret "Direct link to 2. Create Ingress Auth Secret")

```
kubectl create secret generic mlflow-auth \

  --namespace mlflow \

  --from-literal=auth=admin:$apr1$hash_of_password
```

## Security Best Practices[​](#security-best-practices "Direct link to Security Best Practices")

### 1. Use HTTPS[​](#1-use-https "Direct link to 1. Use HTTPS")

Configure TLS for secure communication:

```
ingress:

  enabled: true

  tls:

    - secretName: mlflow-tls

      hosts:

        - mlflow.your-domain.com
```

### 2. Implement Rate Limiting[​](#2-implement-rate-limiting "Direct link to 2. Implement Rate Limiting")

```
ingress:

  annotations:

    nginx.ingress.kubernetes.io/rate-limit: "100"

    nginx.ingress.kubernetes.io/rate-limit-window: "1m"
```

## Monitoring Authentication[​](#monitoring-authentication "Direct link to Monitoring Authentication")

### 1. Enable Auth Logging[​](#1-enable-auth-logging "Direct link to 1. Enable Auth Logging")

```
extraEnvVars:

  MLFLOW_LOGGING_LEVEL: "INFO"  # MLflow logging level

  MLFLOW_CONFIGURE_LOGGING: "true"  # Configure MLflow logging on import
```

### 2. Configure Audit Logs[​](#2-configure-audit-logs "Direct link to 2. Configure Audit Logs")

```
extraEnvVars:

  MLFLOW_LOGGING_LEVEL: "DEBUG"  # Enable detailed logging for audit purposes

  MLFLOW_ENABLE_SYSTEM_METRICS_LOGGING: "true"  # Enable system metrics for monitoring
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Authentication Failed**: Check credentials and authentication provider configuration
2. **LDAP Connection Problems**: Check LDAP server connectivity and credentials
3. **Session Issues**: Verify session timeout and cookie settings
4. **PostgreSQL Auth Backend Issues**: Verify database connectivity and permissions

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check authentication configuration

kubectl exec -it deployment/mlflow -n mlflow -- env | grep MLFLOW



# View authentication logs

kubectl logs deployment/mlflow -n mlflow | grep -i "auth\|login"



# Test authentication endpoint

kubectl port-forward svc/mlflow -n mlflow 5000:5000

curl -u admin:password http://localhost:5000/health



# Check LDAP connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  ldapsearch -H ldap://your-ldap-server:389 -D "uid=test,ou=people,dc=example,dc=com" -w password -b "dc=example,dc=com"
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

tip

**Getting Started:** Follow these guides to enhance your MLflow security setup.

* [Basic Installation](/docs/charts/mlflow/basic-installation.md) - Set up MLflow with authentication
* [PostgreSQL Backend Installation](/docs/charts/mlflow/postgresql-backend-installation.md) - Production database setup
* [Autoscaling Setup](/docs/charts/mlflow/autoscaling-setup.md) - Scale with authentication
* [Monitoring Setup](/docs/charts/mlflow/troubleshooting-and-monitoring.md) - Monitor authentication events

info

**Security Enhancement:** Consider implementing additional security measures like OAuth, SAML, or multi-factor authentication for enhanced security.


---

# Autoscaling Setup

This guide covers configuring autoscaling for MLflow to handle varying workloads efficiently. We'll cover Horizontal Pod Autoscaler (HPA), and cluster autoscaling strategies.

info

**Production Scaling:** Autoscaling is essential for production MLflow deployments to handle varying workloads and ensure optimal resource utilization.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**Critical Requirements:** Autoscaling requires specific backend configurations. Ensure all prerequisites are met before enabling autoscaling.

* Kubernetes cluster with metrics server enabled
* MLflow deployed on Kubernetes
* Cluster autoscaler configured (for node scaling)
* Resource requests and limits defined for MLflow pods
* **Backend store enabled** (PostgreSQL or MySQL, not SQLite)
* **Artifact store enabled** (S3, Azure Blob, or GCS)
* **Authentication configured** (PostgreSQL auth backend or disabled)

tip

**Resource Planning:** Define appropriate resource requests and limits for your MLflow pods to enable effective autoscaling decisions.

## Horizontal Pod Autoscaler (HPA)[​](#horizontal-pod-autoscaler-hpa "Direct link to Horizontal Pod Autoscaler (HPA)")

### Prerequisites for HPA[​](#prerequisites-for-hpa "Direct link to Prerequisites for HPA")

warning

**HPA Requirements:** The HPA will only be created if all these conditions are met. Check your configuration carefully.

The HPA is created only if:

* `autoscaling.enabled: true`
* A backend store is enabled (`backendStore.postgres.enabled` or `backendStore.mysql.enabled`)
* An artifact store is enabled (`artifactRoot.azureBlob.enabled`, `artifactRoot.s3.enabled`, or `artifactRoot.gcs.enabled`)
* Auth is either enabled with Postgres (`auth.enabled` and `auth.postgres.enabled`) or disabled (`auth.enabled: false`)

### 1. Basic HPA Configuration[​](#1-basic-hpa-configuration "Direct link to 1. Basic HPA Configuration")

Create `values-autoscaling.yaml`:

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  s3:

    enabled: true

    bucket: my-mlflow-artifact-root-backend

    awsAccessKeyId: a1b2c3d4

    awsSecretAccessKey: a1b2c3d4



autoscaling:

  enabled: true

  minReplicas: 2

  maxReplicas: 10

  metrics:

    - type: Resource

      resource:

        name: memory

        target:

          type: Utilization

          averageUtilization: 80

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70
```

### 2. Deploy with Autoscaling[​](#2-deploy-with-autoscaling "Direct link to 2. Deploy with Autoscaling")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  -f values-autoscaling.yaml
```

### 3. Custom Scaling Behavior[​](#3-custom-scaling-behavior "Direct link to 3. Custom Scaling Behavior")

For more sophisticated scaling behavior (Kubernetes 1.18+):

```
autoscaling:

  enabled: true

  minReplicas: 2

  maxReplicas: 15

  metrics:

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70

  behavior:

    scaleUp:

      stabilizationWindowSeconds: 30

      policies:

        - type: Percent

          value: 100

          periodSeconds: 60

    scaleDown:

      stabilizationWindowSeconds: 300

      policies:

        - type: Percent

          value: 10

          periodSeconds: 60
```

tip

**Scaling Behavior:** Customize scaling behavior to prevent rapid scaling up/down and ensure stable performance during workload changes.

### 4. Custom Metrics HPA[​](#4-custom-metrics-hpa "Direct link to 4. Custom Metrics HPA")

For more sophisticated scaling based on custom metrics:

```
autoscaling:

  enabled: true

  minReplicas: 2

  maxReplicas: 15

  metrics:

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70

    - type: Object

      object:

        metric:

          name: requests-per-second

        describedObject:

          apiVersion: networking.k8s.io/v1

          kind: Ingress

          name: mlflow-ingress

        target:

          type: AverageValue

          averageValue: 100
```

info

**Custom Metrics:** Use custom metrics for more precise scaling decisions based on application-specific workload indicators.

## Complete Production Configuration[​](#complete-production-configuration "Direct link to Complete Production Configuration")

info

**Production Setup:** This example demonstrates a complete production-ready MLflow configuration with autoscaling enabled.

### PostgreSQL with S3 and Autoscaling[​](#postgresql-with-s3-and-autoscaling "Direct link to PostgreSQL with S3 and Autoscaling")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  s3:

    enabled: true

    bucket: my-mlflow-artifact-root-backend

    awsAccessKeyId: a1b2c3d4

    awsSecretAccessKey: a1b2c3d4



auth:

  enabled: true

  adminUsername: admin

  adminPassword: S3cr3+

  postgres:

    enabled: true

    host: postgresql--auth-instance1.abcdef1234.eu-central-1.rds.amazonaws.com

    port: 5432

    database: auth

    user: mlflowauth

    password: A4m1nPa33w0rd!



autoscaling:

  enabled: true

  minReplicas: 2

  maxReplicas: 10

  metrics:

    - type: Resource

      resource:

        name: memory

        target:

          type: Utilization

          averageUtilization: 80

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70

  behavior:

    scaleUp:

      stabilizationWindowSeconds: 30

      policies:

        - type: Percent

          value: 100

          periodSeconds: 60

    scaleDown:

      stabilizationWindowSeconds: 300

      policies:

        - type: Percent

          value: 10

          periodSeconds: 60



# Resource management for autoscaling

resources:

  requests:

    cpu: 500m

    memory: 1Gi

  limits:

    cpu: 2

    memory: 4Gi



# Health probes for reliability

livenessProbe:

  initialDelaySeconds: 30

  periodSeconds: 20

  timeoutSeconds: 6

  failureThreshold: 3



readinessProbe:

  initialDelaySeconds: 30

  periodSeconds: 20

  timeoutSeconds: 6

  failureThreshold: 3



# Monitoring integration

serviceMonitor:

  enabled: true

  namespace: monitoring

  interval: 30s

  telemetryPath: /metrics

  labels:

    release: prometheus

  timeout: 10s

  targetLabels: []
```

### MinIO with MySQL and Autoscaling[​](#minio-with-mysql-and-autoscaling "Direct link to MinIO with MySQL and Autoscaling")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  mysql:

    enabled: true

    host: mysql-service

    port: 3306

    database: mlflow

    user: mlflow

    password: mlflow



artifactRoot:

  s3:

    enabled: true

    bucket: mlflow

    awsAccessKeyId: minioadmin

    awsSecretAccessKey: minioadmin



extraEnvVars:

  MLFLOW_S3_ENDPOINT_URL: http://minio-service:9000



autoscaling:

  enabled: true

  minReplicas: 2

  maxReplicas: 8

  metrics:

    - type: Resource

      resource:

        name: memory

        target:

          type: Utilization

          averageUtilization: 85

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 75



resources:

  requests:

    cpu: 300m

    memory: 512Mi

  limits:

    cpu: 1

    memory: 2Gi
```

## Cluster Autoscaling[​](#cluster-autoscaling "Direct link to Cluster Autoscaling")

### 1. AWS EKS Cluster Autoscaler[​](#1-aws-eks-cluster-autoscaler "Direct link to 1. AWS EKS Cluster Autoscaler")

```
apiVersion: apps/v1

kind: Deployment

metadata:

  name: cluster-autoscaler

  namespace: kube-system

  labels:

    app: cluster-autoscaler

spec:

  replicas: 1

  selector:

    matchLabels:

      app: cluster-autoscaler

  template:

    metadata:

      labels:

        app: cluster-autoscaler

    spec:

      serviceAccountName: cluster-autoscaler

      containers:

      - image: k8s.gcr.io/autoscaling/cluster-autoscaler:v1.24.0

        name: cluster-autoscaler

        resources:

          limits:

            cpu: 100m

            memory: 300Mi

          requests:

            cpu: 100m

            memory: 300Mi

        command:

        - ./cluster-autoscaler

        - --v=4

        - --stderrthreshold=info

        - --cloud-provider=aws

        - --skip-nodes-with-local-storage=false

        - --expander=least-waste

        - --node-group-auto-discovery=asg:tag=k8s.io/cluster-autoscaler/enabled,k8s.io/cluster-autoscaler/your-cluster-name

        - --balance-similar-node-groups

        - --skip-nodes-with-system-pods=false

        volumeMounts:

        - name: ssl-certs

          mountPath: /etc/ssl/certs/ca-bundle.crt

          readOnly: true

      volumes:

      - name: ssl-certs

        hostPath:

          path: "/etc/ssl/certs/ca-bundle.crt"
```

### 2. GKE Cluster Autoscaling[​](#2-gke-cluster-autoscaling "Direct link to 2. GKE Cluster Autoscaling")

Enable cluster autoscaling in GKE:

```
gcloud container clusters update your-cluster \

  --enable-autoscaling \

  --min-nodes 1 \

  --max-nodes 10 \

  --zone your-zone
```

## MLflow-Specific Autoscaling Configuration[​](#mlflow-specific-autoscaling-configuration "Direct link to MLflow-Specific Autoscaling Configuration")

### 1. Resource Requirements[​](#1-resource-requirements "Direct link to 1. Resource Requirements")

Update MLflow deployment with proper resource requests and limits:

```
resources:

  requests:

    cpu: 500m

    memory: 1Gi

  limits:

    cpu: 2

    memory: 4Gi
```

### 2. Pod Disruption Budget[​](#2-pod-disruption-budget "Direct link to 2. Pod Disruption Budget")

Create a Pod Disruption Budget for high availability:

```
apiVersion: policy/v1

kind: PodDisruptionBudget

metadata:

  name: mlflow-pdb

  namespace: mlflow

spec:

  minAvailable: 1

  selector:

    matchLabels:

      app: mlflow
```

### 3. Advanced HPA with Custom Metrics[​](#3-advanced-hpa-with-custom-metrics "Direct link to 3. Advanced HPA with Custom Metrics")

Using Prometheus metrics for MLflow-specific scaling:

```
autoscaling:

  enabled: true

  minReplicas: 2

  maxReplicas: 20

  metrics:

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70

    - type: External

      external:

        metric:

          name: mlflow_active_experiments

          selector:

            matchLabels:

              app: mlflow

        target:

          type: AverageValue

          averageValue: 10
```

## Monitoring and Alerting[​](#monitoring-and-alerting "Direct link to Monitoring and Alerting")

### 1. HPA Metrics Monitoring[​](#1-hpa-metrics-monitoring "Direct link to 1. HPA Metrics Monitoring")

```
apiVersion: v1

kind: ConfigMap

metadata:

  name: prometheus-rules

  namespace: monitoring

data:

  mlflow-hpa-rules.yaml: |

    groups:

    - name: mlflow-hpa

      rules:

      - alert: MLflowHPAScaling

        expr: kube_horizontalpodautoscaler_status_current_replicas > 0

        for: 5m

        labels:

          severity: warning

        annotations:

          summary: "MLflow HPA is scaling"

          description: "MLflow HPA has {{ $value }} replicas"
```

### 2. Resource Usage Alerts[​](#2-resource-usage-alerts "Direct link to 2. Resource Usage Alerts")

```
- alert: MLflowHighCPU

  expr: container_cpu_usage_seconds_total{container="mlflow"} > 0.8

  for: 5m

  labels:

    severity: warning

  annotations:

    summary: "MLflow high CPU usage"

    description: "MLflow container CPU usage is {{ $value }}"



- alert: MLflowHighMemory

  expr: container_memory_usage_bytes{container="mlflow"} > 3.5e9

  for: 5m

  labels:

    severity: warning

  annotations:

    summary: "MLflow high memory usage"

    description: "MLflow container memory usage is {{ $value }}"
```

## Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

### 1. Pod Anti-Affinity[​](#1-pod-anti-affinity "Direct link to 1. Pod Anti-Affinity")

Ensure MLflow pods are distributed across nodes:

```
affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app

            operator: In

            values:

            - mlflow

        topologyKey: kubernetes.io/hostname
```

### 2. Resource Quotas[​](#2-resource-quotas "Direct link to 2. Resource Quotas")

Set resource quotas for the MLflow namespace:

```
apiVersion: v1

kind: ResourceQuota

metadata:

  name: mlflow-quota

  namespace: mlflow

spec:

  hard:

    requests.cpu: "4"

    requests.memory: 8Gi

    limits.cpu: "8"

    limits.memory: 16Gi

    pods: "10"
```

### 3. Network Policies[​](#3-network-policies "Direct link to 3. Network Policies")

Restrict network access for security:

```
apiVersion: networking.k8s.io/v1

kind: NetworkPolicy

metadata:

  name: mlflow-network-policy

  namespace: mlflow

spec:

  podSelector:

    matchLabels:

      app: mlflow

  policyTypes:

  - Ingress

  - Egress

  ingress:

  - from:

    - namespaceSelector:

        matchLabels:

          name: ingress-nginx

    ports:

    - protocol: TCP

      port: 5000

  egress:

  - to:

    - namespaceSelector:

        matchLabels:

          name: database

    ports:

    - protocol: TCP

      port: 5432
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **HPA not scaling**: Check metrics server and resource requests/limits
2. **Cluster autoscaler issues**: Verify node groups and IAM permissions
3. **Resource starvation**: Monitor cluster capacity and quotas
4. **Prerequisites not met**: Ensure backend store, artifact store, and auth are properly configured

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check HPA status

kubectl get hpa -n mlflow

kubectl describe hpa mlflow-hpa -n mlflow



# Check cluster autoscaler logs

kubectl logs -f deployment/cluster-autoscaler -n kube-system



# Check resource usage

kubectl top pods -n mlflow

kubectl top nodes



# Check metrics server

kubectl get apiservice v1beta1.metrics.k8s.io



# Verify prerequisites

kubectl get configmap -n mlflow mlflow -o yaml | grep -A 10 -B 10 "backend\|artifact\|auth"
```

## Best Practices[​](#best-practices "Direct link to Best Practices")

### 1. Gradual Scaling[​](#1-gradual-scaling "Direct link to 1. Gradual Scaling")

* Use appropriate stabilization windows
* Implement gradual scale-down policies
* Monitor scaling behavior and adjust thresholds

### 2. Resource Management[​](#2-resource-management "Direct link to 2. Resource Management")

* Set realistic resource requests and limits
* Monitor and adjust based on actual usage patterns

### 3. Cost Optimization[​](#3-cost-optimization "Direct link to 3. Cost Optimization")

* Set appropriate min/max replica counts
* Use spot instances where possible
* Monitor and optimize resource utilization

### 4. High Availability[​](#4-high-availability "Direct link to 4. High Availability")

* Deploy across multiple availability zones
* Use pod disruption budgets
* Implement proper health checks and readiness probes

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Set up comprehensive monitoring with Prometheus and Grafana
* Configure alerting for autoscaling events
* Implement cost monitoring and optimization
* Set up backup and disaster recovery strategies
* Configure [ServiceMonitor](/docs/charts/mlflow/usage.md#monitoring) for metrics collection


---

# AWS S3 Integration

This guide covers configuring MLflow to use AWS S3 for artifact storage. S3 provides scalable, durable storage for MLflow artifacts like models, datasets, and experiment outputs.

info

**Enterprise Storage:** AWS S3 is the most popular cloud storage solution for MLflow artifacts, providing high availability, durability, and scalability for production deployments.

<!-- -->

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**AWS Setup:** Ensure you have proper AWS access and permissions before configuring S3 integration.

* AWS account with S3 access
* AWS CLI configured or AWS credentials available
* Kubernetes cluster with MLflow deployed
* IAM permissions for S3 operations

## S3 Bucket Setup[​](#s3-bucket-setup "Direct link to S3 Bucket Setup")

tip

**Bucket Configuration:** Proper bucket setup ensures data durability and cost optimization for your MLflow artifacts.

### 1. Create S3 Bucket[​](#1-create-s3-bucket "Direct link to 1. Create S3 Bucket")

```
aws s3 mb s3://your-mlflow-artifacts-bucket
```

### 2. Configure Bucket Versioning (Recommended)[​](#2-configure-bucket-versioning-recommended "Direct link to 2. Configure Bucket Versioning (Recommended)")

```
aws s3api put-bucket-versioning \

  --bucket your-mlflow-artifacts-bucket \

  --versioning-configuration Status=Enabled
```

tip

**Versioning:** Enable versioning to protect against accidental deletions and maintain artifact history.

### 3. Configure Bucket Lifecycle (Optional)[​](#3-configure-bucket-lifecycle-optional "Direct link to 3. Configure Bucket Lifecycle (Optional)")

```
aws s3api put-bucket-lifecycle-configuration \

  --bucket your-mlflow-artifacts-bucket \

  --lifecycle-configuration '{

    "Rules": [

      {

        "ID": "DeleteOldVersions",

        "Status": "Enabled",

        "Filter": {},

        "NoncurrentVersionExpiration": {

          "NoncurrentDays": 30

        }

      }

    ]

  }'
```

info

**Lifecycle Management:** Configure lifecycle policies to automatically manage storage costs and clean up old artifacts.

## IAM Configuration[​](#iam-configuration "Direct link to IAM Configuration")

warning

**Security Best Practice:** Use IAM roles instead of access keys for production deployments to improve security and eliminate credential management.

### Option 1: IAM User (Development)[​](#option-1-iam-user-development "Direct link to Option 1: IAM User (Development)")

Create an IAM user with S3 permissions:

```
{

  "Version": "2012-10-17",

  "Statement": [

    {

      "Effect": "Allow",

      "Action": [

        "s3:GetObject",

        "s3:PutObject",

        "s3:DeleteObject",

        "s3:ListBucket"

      ],

      "Resource": [

        "arn:aws:s3:::your-mlflow-artifacts-bucket",

        "arn:aws:s3:::your-mlflow-artifacts-bucket/*"

      ]

    }

  ]

}
```

### Option 2: IAM Role (Production)[​](#option-2-iam-role-production "Direct link to Option 2: IAM Role (Production)")

Create an IAM role for Kubernetes service accounts:

```
{

  "Version": "2012-10-17",

  "Statement": [

    {

      "Effect": "Allow",

      "Principal": {

        "Federated": "arn:aws:iam::YOUR_ACCOUNT_ID:oidc-provider/oidc.eks.YOUR_REGION.amazonaws.com/id/YOUR_OIDC_ID"

      },

      "Action": "sts:AssumeRoleWithWebIdentity",

      "Condition": {

        "StringEquals": {

          "oidc.eks.YOUR_REGION.amazonaws.com/id/YOUR_OIDC_ID:sub": "system:serviceaccount:mlflow:mlflow"

        }

      }

    }

  ]

}
```

## Kubernetes Secret for AWS Credentials[​](#kubernetes-secret-for-aws-credentials "Direct link to Kubernetes Secret for AWS Credentials")

warning

**Credential Security:** Store AWS credentials in Kubernetes secrets rather than hardcoding them in configuration files.

### Create Secret with AWS Credentials[​](#create-secret-with-aws-credentials "Direct link to Create Secret with AWS Credentials")

```
kubectl create secret generic aws-credentials \

  --namespace mlflow \

  --from-literal=aws-access-key-id=YOUR_ACCESS_KEY \

  --from-literal=aws-secret-access-key=YOUR_SECRET_KEY \

  --from-literal=aws-region=us-west-2
```

## MLflow Configuration[​](#mlflow-configuration "Direct link to MLflow Configuration")

<!-- -->

info

**Complete Setup:** This configuration demonstrates a production-ready MLflow setup with PostgreSQL backend and S3 artifact storage.

### Option 1: Using Helm Values[​](#option-1-using-helm-values "Direct link to Option 1: Using Helm Values")

Create `values.yaml`:

```
backendStore:

  databaseMigration: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  s3:

    enabled: true

    bucket: your-mlflow-artifacts-bucket

    path: ""  # Optional: S3 bucket folder

    awsAccessKeyId: ""  # Will use IAM role or secret

    awsSecretAccessKey: ""  # Will use IAM role or secret



extraEnvVars:

  AWS_DEFAULT_REGION: us-west-2

  MLFLOW_S3_ENDPOINT_URL: ""  # For MinIO compatibility

  MLFLOW_S3_IGNORE_TLS: "false"
```

### Option 2: Using Helm Set Commands[​](#option-2-using-helm-set-commands "Direct link to Option 2: Using Helm Set Commands")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.databaseMigration=true \

  --set backendStore.postgres.enabled=true \

  --set backendStore.postgres.host=postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com \

  --set backendStore.postgres.database=mlflow \

  --set backendStore.postgres.user=mlflowuser \

  --set backendStore.postgres.password=Pa33w0rd! \

  --set artifactRoot.s3.enabled=true \

  --set artifactRoot.s3.bucket=your-mlflow-artifacts-bucket \

  --set artifactRoot.s3.awsAccessKeyId=YOUR_ACCESS_KEY \

  --set artifactRoot.s3.awsSecretAccessKey=YOUR_SECRET_KEY
```

warning

**Command Line Security:** Avoid passing sensitive credentials via command line arguments. Use values files or secrets instead.

## EKS Integration with IAM Roles[​](#eks-integration-with-iam-roles "Direct link to EKS Integration with IAM Roles")

If using EKS, configure IAM roles for service accounts:

tip

**EKS Best Practice:** IAM roles for service accounts provide the most secure and manageable way to grant AWS permissions to Kubernetes pods.

### 1. Create Service Account[​](#1-create-service-account "Direct link to 1. Create Service Account")

```
serviceAccount:

  create: true

  annotations:

    eks.amazonaws.com/role-arn: arn:aws:iam::YOUR_ACCOUNT_ID:role/mlflow-s3-role

  name: mlflow
```

### 2. Update MLflow Deployment[​](#2-update-mlflow-deployment "Direct link to 2. Update MLflow Deployment")

```
artifactRoot:

  s3:

    enabled: true

    bucket: your-mlflow-artifacts-bucket

    path: ""

    # No need for access keys when using IAM roles



serviceAccount:

  create: false

  name: mlflow
```

## MinIO Integration[​](#minio-integration "Direct link to MinIO Integration")

### S3-Compatible Storage with MinIO[​](#s3-compatible-storage-with-minio "Direct link to S3-Compatible Storage with MinIO")

<!-- -->

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgres-service

    port: 5432

    database: postgres

    user: postgres

    password: postgres



artifactRoot:

  s3:

    enabled: true

    bucket: mlflow

    awsAccessKeyId: minioadmin

    awsSecretAccessKey: minioadmin



extraEnvVars:

  MLFLOW_S3_ENDPOINT_URL: http://minio-service:9000

  MLFLOW_S3_IGNORE_TLS: "true"



ingress:

  enabled: true

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: ImplementationSpecific
```

### MinIO with MySQL Backend[​](#minio-with-mysql-backend "Direct link to MinIO with MySQL Backend")

<!-- -->

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  mysql:

    enabled: true

    host: mysql-service

    port: 3306

    database: mlflow

    user: mlflow

    password: mlflow



artifactRoot:

  s3:

    enabled: true

    bucket: mlflow

    awsAccessKeyId: minioadmin

    awsSecretAccessKey: minioadmin



extraEnvVars:

  MLFLOW_S3_ENDPOINT_URL: http://minio-service:9000

  MLFLOW_S3_IGNORE_TLS: "true"
```

## Verification[​](#verification "Direct link to Verification")

### Test S3 Access[​](#test-s3-access "Direct link to Test S3 Access")

```
# Test from within the MLflow pod

kubectl exec -it deployment/mlflow -n mlflow -- \

  aws s3 ls s3://your-mlflow-artifacts-bucket
```

### Check MLflow Logs[​](#check-mlflow-logs "Direct link to Check MLflow Logs")

```
kubectl logs deployment/mlflow -n mlflow | grep -i "s3\|artifact"
```

### Test Artifact Upload[​](#test-artifact-upload "Direct link to Test Artifact Upload")

Access MLflow UI and create an experiment with artifacts to verify S3 integration.

## Advanced Configuration[​](#advanced-configuration "Direct link to Advanced Configuration")

### Custom S3 Endpoint[​](#custom-s3-endpoint "Direct link to Custom S3 Endpoint")

For S3-compatible storage (MinIO, etc.):

```
artifactRoot:

  s3:

    enabled: true

    bucket: your-bucket

    awsAccessKeyId: minio-access-key

    awsSecretAccessKey: minio-secret-key



extraEnvVars:

  MLFLOW_S3_ENDPOINT_URL: "http://minio-service:9000"  # Custom S3 endpoint URL

  MLFLOW_S3_IGNORE_TLS: "true"  # Skip TLS certificate verification for S3
```

### S3 Encryption[​](#s3-encryption "Direct link to S3 Encryption")

Enable server-side encryption:

```
extraEnvVars:

  MLFLOW_S3_UPLOAD_EXTRA_ARGS: '{"ServerSideEncryption": "aws:kms", "SSEKMSKeyId": "1234"}'  # Extra S3 upload arguments
```

### S3 Presigned URLs[​](#s3-presigned-urls "Direct link to S3 Presigned URLs")

For better performance with large artifacts:

```
extraEnvVars:

  MLFLOW_ENABLE_MULTIPART_UPLOAD: "true"  # Enable multipart upload for large files

  MLFLOW_ENABLE_MULTIPART_DOWNLOAD: "true"  # Enable multipart download for large files

  MLFLOW_MULTIPART_UPLOAD_MINIMUM_FILE_SIZE: "524288000"  # Minimum file size for multipart upload (500MB)

  MLFLOW_MULTIPART_DOWNLOAD_MINIMUM_FILE_SIZE: "524288000"  # Minimum file size for multipart download (500MB)
```

### Custom S3 Path[​](#custom-s3-path "Direct link to Custom S3 Path")

Store artifacts in a specific S3 folder:

```
artifactRoot:

  s3:

    enabled: true

    bucket: your-mlflow-artifacts-bucket

    path: mlflow/artifacts  # Optional folder path

    awsAccessKeyId: your-access-key

    awsSecretAccessKey: your-secret-key
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Access Denied**: Check IAM permissions and bucket policies
2. **Region Mismatch**: Ensure S3 bucket and MLflow region match
3. **Credential Issues**: Verify AWS credentials are properly configured
4. **Network Issues**: Check VPC endpoints for private subnets
5. **MinIO Connection**: Verify MinIO service endpoint and credentials

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check AWS credentials in pod

kubectl exec -it deployment/mlflow -n mlflow -- env | grep AWS



# Test S3 connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  aws s3api list-buckets



# Check MLflow S3 configuration

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import mlflow; print(mlflow.get_artifact_uri())"



# Test MinIO connection

kubectl exec -it deployment/mlflow -n mlflow -- \

  aws s3 ls s3://mlflow --endpoint-url http://minio-service:9000
```

## Cost Optimization[​](#cost-optimization "Direct link to Cost Optimization")

* Use S3 Intelligent Tiering for cost-effective storage
* Configure lifecycle policies to move old artifacts to cheaper storage
* Monitor S3 usage with CloudWatch
* Consider using S3 Transfer Acceleration for faster uploads

## Security Best Practices[​](#security-best-practices "Direct link to Security Best Practices")

* Use IAM roles instead of access keys when possible
* Enable S3 bucket encryption
* Configure bucket policies to restrict access
* Use VPC endpoints for private subnets
* Regularly rotate access keys

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Set up [authentication](/docs/charts/mlflow/authentication-configuration.md) for MLflow UI
* Configure [autoscaling](/docs/charts/mlflow/autoscaling-setup.md) for high availability
* Set up monitoring and alerting for S3 usage
* Configure [Google Cloud Storage](/docs/charts/mlflow/google-cloud-storage-integration.md) or [Azure Blob Storage](/docs/charts/mlflow/azure-blob-storage-integration.md) as alternatives


---

# Azure Blob Storage Integration

This guide covers configuring MLflow to use Azure Blob Storage for artifact storage. Azure Blob Storage provides scalable, durable storage for MLflow artifacts with enterprise-grade security and compliance features.

info

**Azure Integration:** Azure Blob Storage is ideal for organizations using Microsoft Azure, providing seamless integration with Azure services and enterprise security features.

<!-- -->

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**Azure Setup:** Ensure you have proper Azure access and permissions before configuring Blob Storage integration.

* Azure subscription with Storage Account access
* Azure CLI configured or Azure credentials available
* Kubernetes cluster with MLflow deployed
* Storage Account with Blob service enabled

## Azure Storage Account Setup[​](#azure-storage-account-setup "Direct link to Azure Storage Account Setup")

tip

**Storage Configuration:** Proper storage account setup ensures optimal performance and cost management for your MLflow artifacts.

### 1. Create Storage Account[​](#1-create-storage-account "Direct link to 1. Create Storage Account")

```
az storage account create \

  --name yourmlflowstorage \

  --resource-group your-resource-group \

  --location eastus \

  --sku Standard_LRS \

  --kind StorageV2
```

### 2. Create Blob Container[​](#2-create-blob-container "Direct link to 2. Create Blob Container")

```
az storage container create \

  --account-name yourmlflowstorage \

  --name mlflow-artifacts
```

### 3. Get Storage Account Key[​](#3-get-storage-account-key "Direct link to 3. Get Storage Account Key")

```
STORAGE_KEY=$(az storage account keys list \

  --account-name yourmlflowstorage \

  --resource-group your-resource-group \

  --query '[0].value' -o tsv)
```

## Authentication Options[​](#authentication-options "Direct link to Authentication Options")

warning

**Security Best Practice:** Use managed identities or service principals instead of storage account keys for production deployments.

### Option 1: Storage Account Key (Development)[​](#option-1-storage-account-key-development "Direct link to Option 1: Storage Account Key (Development)")

```
kubectl create secret generic azure-storage-credentials \

  --namespace mlflow \

  --from-literal=azure-storage-account-name=yourmlflowstorage \

  --from-literal=azure-storage-account-key=$STORAGE_KEY
```

tip

**Development Use:** Storage account keys are suitable for development and testing but not recommended for production.

### Option 2: Service Principal (Production)[​](#option-2-service-principal-production "Direct link to Option 2: Service Principal (Production)")

Create a service principal with Storage Blob Data Contributor role:

```
# Create service principal

az ad sp create-for-rbac \

  --name mlflow-storage-sp \

  --role "Storage Blob Data Contributor" \

  --scopes /subscriptions/YOUR_SUBSCRIPTION_ID/resourceGroups/YOUR_RESOURCE_GROUP/providers/Microsoft.Storage/storageAccounts/yourmlflowstorage



# Create secret with service principal credentials

kubectl create secret generic azure-service-principal \

  --namespace mlflow \

  --from-literal=azure-client-id=YOUR_CLIENT_ID \

  --from-literal=azure-client-secret=YOUR_CLIENT_SECRET \

  --from-literal=azure-tenant-id=YOUR_TENANT_ID \

  --from-literal=azure-subscription-id=YOUR_SUBSCRIPTION_ID
```

### Option 3: Managed Identity (AKS)[​](#option-3-managed-identity-aks "Direct link to Option 3: Managed Identity (AKS)")

If using AKS with managed identity:

```
# Enable managed identity on AKS cluster

az aks update \

  --resource-group your-resource-group \

  --name your-aks-cluster \

  --enable-managed-identity



# Assign Storage Blob Data Contributor role to managed identity

az role assignment create \

  --assignee-object-id $(az aks show -g your-resource-group -n your-aks-cluster --query identityProfile.kubeletidentity.objectId -o tsv) \

  --role "Storage Blob Data Contributor" \

  --scope /subscriptions/YOUR_SUBSCRIPTION_ID/resourceGroups/YOUR_RESOURCE_GROUP/providers/Microsoft.Storage/storageAccounts/yourmlflowstorage
```

info

**AKS Best Practice:** Managed identities provide the most secure and manageable way to grant Azure permissions to AKS pods.

## MLflow Configuration[​](#mlflow-configuration "Direct link to MLflow Configuration")

info

**Complete Setup:** This configuration demonstrates a production-ready MLflow setup with PostgreSQL backend and Azure Blob Storage.

### Option 1: Using Storage Account Key[​](#option-1-using-storage-account-key "Direct link to Option 1: Using Storage Account Key")

<!-- -->

Create `values.yaml`:

```
backendStore:

  databaseMigration: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  azureBlob:

    enabled: true

    container: mlflow-artifacts

    storageAccount: yourmlflowstorage

    path: ""  # Optional: Azure blob container folder

    accessKey: ""  # Will use secret

    connectionString: ""  # Alternative to accessKey



extraEnvVars:

  AZURE_STORAGE_ACCOUNT: yourmlflowstorage

  AZURE_STORAGE_KEY: ""  # Will use secret

  MLFLOW_ARTIFACT_ROOT: "wasbs://mlflow-artifacts@yourmlflowstorage.blob.core.windows.net"
```

### Option 2: Using Service Principal[​](#option-2-using-service-principal "Direct link to Option 2: Using Service Principal")

```
artifactRoot:

  azureBlob:

    enabled: true

    container: mlflow-artifacts

    storageAccount: yourmlflowstorage

    path: ""



extraEnvVars:

  AZURE_CLIENT_ID: ""  # Will use secret

  AZURE_CLIENT_SECRET: ""  # Will use secret

  AZURE_TENANT_ID: ""  # Will use secret

  AZURE_SUBSCRIPTION_ID: ""  # Will use secret

  MLFLOW_ARTIFACT_ROOT: "wasbs://mlflow-artifacts@yourmlflowstorage.blob.core.windows.net"
```

### Option 3: Using Helm Set Commands[​](#option-3-using-helm-set-commands "Direct link to Option 3: Using Helm Set Commands")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.databaseMigration=true \

  --set backendStore.postgres.enabled=true \

  --set backendStore.postgres.host=postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com \

  --set backendStore.postgres.database=mlflow \

  --set backendStore.postgres.user=mlflowuser \

  --set backendStore.postgres.password=Pa33w0rd! \

  --set artifactRoot.azureBlob.enabled=true \

  --set artifactRoot.azureBlob.container=mlflow-artifacts \

  --set artifactRoot.azureBlob.storageAccount=yourmlflowstorage \

  --set artifactRoot.azureBlob.accessKey=your-access-key
```

warning

**Command Line Security:** Avoid passing sensitive credentials via command line arguments. Use values files or secrets instead.

## AKS Integration with Managed Identity[​](#aks-integration-with-managed-identity "Direct link to AKS Integration with Managed Identity")

If using AKS with managed identity, configure the service account:

tip

**AKS Integration:** Managed identities eliminate the need to manage service principal credentials and provide automatic credential rotation.

```
serviceAccount:

  create: true

  name: mlflow

  annotations:

    azure.workload.identity/client-id: $(az aks show -g your-resource-group -n your-aks-cluster --query identityProfile.kubeletidentity.clientId -o tsv)



artifactRoot:

  azureBlob:

    enabled: true

    container: mlflow-artifacts

    storageAccount: yourmlflowstorage

    path: ""

    # No credentials needed with managed identity



extraEnvVars:

  MLFLOW_ARTIFACT_ROOT: "wasbs://mlflow-artifacts@yourmlflowstorage.blob.core.windows.net"
```

## Verification[​](#verification "Direct link to Verification")

### Test Azure Storage Access[​](#test-azure-storage-access "Direct link to Test Azure Storage Access")

```
# Test from within the MLflow pod

kubectl exec -it deployment/mlflow -n mlflow -- \

  az storage blob list --container-name mlflow-artifacts --account-name yourmlflowstorage
```

### Check MLflow Logs[​](#check-mlflow-logs "Direct link to Check MLflow Logs")

```
kubectl logs deployment/mlflow -n mlflow | grep -i "azure\|wasbs\|artifact"
```

### Test Artifact Upload[​](#test-artifact-upload "Direct link to Test Artifact Upload")

Access MLflow UI and create an experiment with artifacts to verify Azure Blob Storage integration.

## Advanced Configuration[​](#advanced-configuration "Direct link to Advanced Configuration")

### Custom Endpoint[​](#custom-endpoint "Direct link to Custom Endpoint")

For Azure Stack or custom endpoints:

```
extraEnvVars:

  AZURE_STORAGE_ENDPOINT: "https://your-custom-endpoint.com"
```

### Azure Data Lake Storage Gen2[​](#azure-data-lake-storage-gen2 "Direct link to Azure Data Lake Storage Gen2")

For ADLS Gen2 with hierarchical namespace:

```
artifactRoot:

  azureBlob:

    enabled: true

    container: mlflow-artifacts

    storageAccount: yourmlflowstorage

    path: ""



extraEnvVars:

  MLFLOW_ARTIFACT_ROOT: "abfss://mlflow-artifacts@yourmlflowstorage.dfs.core.windows.net"
```

### Azure Storage Encryption[​](#azure-storage-encryption "Direct link to Azure Storage Encryption")

Enable customer-managed keys:

```
# Create key vault and key

az keyvault create --name your-keyvault --resource-group your-resource-group

az keyvault key create --vault-name your-keyvault --name storage-key --kty RSA --size 2048



# Configure storage account encryption

az storage account update \

  --name yourmlflowstorage \

  --resource-group your-resource-group \

  --encryption-key-source Microsoft.Keyvault \

  --encryption-key-vault https://your-keyvault.vault.azure.net/keys/storage-key
```

### Custom Azure Blob Path[​](#custom-azure-blob-path "Direct link to Custom Azure Blob Path")

Store artifacts in a specific Azure Blob folder:

```
artifactRoot:

  azureBlob:

    enabled: true

    container: mlflow-artifacts

    storageAccount: yourmlflowstorage

    path: mlflow/artifacts  # Optional folder path

    accessKey: your-access-key
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Authentication Failed**: Check storage account key or service principal credentials
2. **Container Not Found**: Ensure blob container exists and is accessible
3. **Network Issues**: Check firewall rules and virtual network access
4. **Permission Denied**: Verify role assignments for service principal or managed identity
5. **Connection String Issues**: Verify connection string format and credentials

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check Azure credentials in pod

kubectl exec -it deployment/mlflow -n mlflow -- env | grep AZURE



# Test Azure CLI connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  az storage account show --name yourmlflowstorage



# Check MLflow Azure configuration

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import mlflow; print(mlflow.get_artifact_uri())"



# Test Azure Blob access

kubectl exec -it deployment/mlflow -n mlflow -- \

  az storage blob list --container-name mlflow-artifacts --account-name yourmlflowstorage
```

## Cost Optimization[​](#cost-optimization "Direct link to Cost Optimization")

* Use Azure Storage lifecycle management for cost-effective storage
* Configure blob tiering (Hot, Cool, Archive)
* Monitor storage usage with Azure Monitor
* Use Azure Storage Analytics for usage insights

## Security Best Practices[​](#security-best-practices "Direct link to Security Best Practices")

* Use managed identity instead of storage account keys when possible
* Enable Azure Storage encryption
* Configure network security with private endpoints
* Use Azure Key Vault for key management
* Regularly rotate storage account keys
* Enable soft delete for blob containers

## Monitoring and Alerting[​](#monitoring-and-alerting "Direct link to Monitoring and Alerting")

### Storage Metrics[​](#storage-metrics "Direct link to Storage Metrics")

Enable storage analytics for monitoring:

```
az storage metrics update \

  --account-name yourmlflowstorage \

  --services blob \

  --hour true \

  --minute true
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Set up [authentication](/docs/charts/mlflow/authentication-configuration.md) for MLflow UI
* Configure [autoscaling](/docs/charts/mlflow/autoscaling-setup.md) for high availability
* Set up Azure Monitor for comprehensive monitoring
* Configure backup and disaster recovery strategies
* Consider [AWS S3](/docs/charts/mlflow/aws-s3-integration.md) or [Google Cloud Storage](/docs/charts/mlflow/google-cloud-storage-integration.md) as alternatives


---

# Basic Installation with SQLite

This guide walks you through installing MLflow on Kubernetes using SQLite as the backend database. This setup is perfect for development, testing, or small-scale deployments.

info

**Use Case:** SQLite installation is ideal for development, testing, single-user scenarios, and learning MLflow concepts.

warning

**Production Limitation:** SQLite is not suitable for production environments with multiple users or high data volumes. Use PostgreSQL or MySQL for production deployments.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**Requirements:** Ensure you have all prerequisites installed and configured before proceeding with the installation.

* Kubernetes cluster (v1.16+)
* Helm 3.x installed
* kubectl configured
* Storage class available for PVC

danger

**Cluster Compatibility:** Verify your Kubernetes cluster version meets the minimum requirements to avoid deployment issues.

## Installation Steps[​](#installation-steps "Direct link to Installation Steps")

note

**Getting Started:** Follow these steps in order to get MLflow running quickly with minimal configuration.

### 1. Add the Helm Repository[​](#1-add-the-helm-repository "Direct link to 1. Add the Helm Repository")

```
helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update
```

tip

**Repository Management:** Always update the repository before installing to get the latest chart versions and bug fixes.

### 2. Create Namespace[​](#2-create-namespace "Direct link to 2. Create Namespace")

```
kubectl create namespace mlflow
```

info

**Namespace Organization:** Using dedicated namespaces helps organize your Kubernetes resources and simplifies management.

### 3. Install MLflow with Default Settings[​](#3-install-mlflow-with-default-settings "Direct link to 3. Install MLflow with Default Settings")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.defaultSqlitePath=/mlflow/data/mlflow.db
```

tip

**Quick Start:** This command installs MLflow with SQLite backend and basic configuration suitable for development.

warning

**Data Persistence:** The default installation stores SQLite data in the pod. Data will be lost if the pod is deleted.

### 4. Verify Installation[​](#4-verify-installation "Direct link to 4. Verify Installation")

Check the deployment status:

```
kubectl get pods -n mlflow
```

You should see the MLflow server pod running. Wait for it to be in `Running` state.

tip

**Status Monitoring:** Use `kubectl describe pod` to troubleshoot if the pod doesn't reach Running state.

### 5. Access MLflow UI[​](#5-access-mlflow-ui "Direct link to 5. Access MLflow UI")

Port-forward to access the web interface:

```
kubectl port-forward svc/mlflow -n mlflow 5000:5000
```

Open your browser and navigate to `http://localhost:5000`

info

**Access Method:** Port-forwarding is suitable for development. For production, use ingress or load balancer.

warning

**Security Note:** Port-forwarding bypasses ingress security. Use proper ingress configuration for production access.

## Configuration Options[​](#configuration-options "Direct link to Configuration Options")

tip

**Customization:** Use values files to customize your MLflow installation according to your specific needs.

tip

**Logging Level:** Use the `log.level` value to control the verbosity of MLflow logs. For development or troubleshooting, set `log.level: debug`.

### Basic Values Override[​](#basic-values-override "Direct link to Basic Values Override")

Create a `values.yaml` file for custom configuration:

```
backendStore:

  defaultSqlitePath: /mlflow/data/mlflow.db

  databaseMigration: false  # Enable for schema updates

  databaseConnectionCheck: false  # Enable for health checks



artifactRoot:

  defaultArtifactRoot: ./mlruns

  defaultArtifactsDestination: ./mlartifacts

  proxiedArtifactStorage: false



service:

  type: ClusterIP

  port: 5000



ingress:

  enabled: false



persistence:

  enabled: true

  size: 10Gi

  storageClass: ""
```

Install with custom values:

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  -f values.yaml
```

info

**Values File:** Using a values file makes it easier to manage and version your configuration.

### PVC Mount with SQLite and File-Based Artifacts[​](#pvc-mount-with-sqlite-and-file-based-artifacts "Direct link to PVC Mount with SQLite and File-Based Artifacts")

<!-- -->

info

**Persistent Storage:** Using PVC ensures your MLflow data persists across pod restarts and deployments.

For persistent storage with SQLite and local artifacts:

#### 1. Create PVC[​](#1-create-pvc "Direct link to 1. Create PVC")

```
apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: mlflow-pvc

  namespace: mlflow

spec:

  accessModes:

    - ReadWriteOnce

  resources:

    requests:

      storage: 5Gi

  storageClassName: standard
```

Apply the PVC:

```
kubectl apply -f mlflow-pvc.yaml
```

tip

**Storage Planning:** Choose an appropriate storage size based on your expected data volume and retention requirements.

#### 2. Configure MLflow with PVC[​](#2-configure-mlflow-with-pvc "Direct link to 2. Configure MLflow with PVC")

```
strategy:

  type: Recreate



extraVolumes:

  - name: mlflow-volume

    persistentVolumeClaim:

      claimName: mlflow-pvc



extraVolumeMounts:

  - name: mlflow-volume

    mountPath: /mlflow/data



backendStore:

  defaultSqlitePath: /mlflow/data/mlflow.db



artifactRoot:

  proxiedArtifactStorage: true

  defaultArtifactsDestination: /mlflow/data/mlartifacts



ingress:

  enabled: true

  hosts:

    - host: my-mlflow-server-domain-name.com

      paths:

        - path: /

          pathType: ImplementationSpecific
```

warning

**Data Persistence:** Without PVC, your MLflow data will be lost when the pod is restarted or redeployed. **SQLite Limitations:** While this setup works, consider PostgreSQL for production environments with multiple users or high data volumes.

danger

**Data Backup:** Always implement regular backups for your MLflow data, especially when using SQLite in any environment.

## Advanced Configuration[​](#advanced-configuration "Direct link to Advanced Configuration")

info

**Advanced Features:** These configurations provide additional functionality for more complex deployment scenarios.

### Database Migrations[​](#database-migrations "Direct link to Database Migrations")

Enable automatic database schema migrations:

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true
```

warning

**Migration Safety:** Database migrations are disabled by default. Enable them only when you're ready to update your database schema.

tip

**Migration Testing:** Test migrations in a staging environment before applying to production.

### Authentication Setup[​](#authentication-setup "Direct link to Authentication Setup")

Enable basic authentication:

```
auth:

  enabled: true

  adminUsername: admin

  adminPassword: your-secure-password
```

danger

**Security Requirement:** Always enable authentication in production environments to secure your MLflow instance.

warning

**Password Security:** Use strong, unique passwords and consider using Kubernetes secrets for credential management.

### Resource Management[​](#resource-management "Direct link to Resource Management")

Configure resource limits and requests:

```
resources:

  requests:

    cpu: 100m

    memory: 128Mi

  limits:

    cpu: 500m

    memory: 512Mi
```

tip

**Resource Planning:** Start with conservative limits and adjust based on actual usage patterns.

### Health Checks[​](#health-checks "Direct link to Health Checks")

Configure liveness and readiness probes:

```
livenessProbe:

  httpGet:

    path: /health

    port: 5000

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 3



readinessProbe:

  httpGet:

    path: /health

    port: 5000

  initialDelaySeconds: 5

  periodSeconds: 5

  timeoutSeconds: 3

  failureThreshold: 3
```

info

**Health Monitoring:** Health checks help Kubernetes detect and recover from application failures automatically.

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

info

**Common Issues:** This section covers the most frequently encountered problems and their solutions.

### Pod Not Starting[​](#pod-not-starting "Direct link to Pod Not Starting")

Check pod status and logs:

```
kubectl get pods -n mlflow

kubectl describe pod <pod-name> -n mlflow

kubectl logs <pod-name> -n mlflow
```

tip

**Debug Commands:** Use these commands to diagnose pod startup issues.

### Database Connection Issues[​](#database-connection-issues "Direct link to Database Connection Issues")

For SQLite-specific issues:

```
# Check if SQLite file exists

kubectl exec -it <pod-name> -n mlflow -- ls -la /mlflow/data/



# Check SQLite file permissions

kubectl exec -it <pod-name> -n mlflow -- ls -la /mlflow/data/mlflow.db
```

warning

**Permission Issues:** Ensure the MLflow container has proper permissions to read/write the SQLite database file.

### Storage Issues[​](#storage-issues "Direct link to Storage Issues")

Check PVC status:

```
kubectl get pvc -n mlflow

kubectl describe pvc mlflow-pvc -n mlflow
```

tip

**Storage Troubleshooting:** Verify PVC is bound and has sufficient storage capacity.

### Access Issues[​](#access-issues "Direct link to Access Issues")

Check service and port-forward:

```
kubectl get svc -n mlflow

kubectl port-forward svc/mlflow -n mlflow 5000:5000
```

info

**Network Debugging:** Verify the service is properly configured and port-forwarding is working.

## Performance Considerations[​](#performance-considerations "Direct link to Performance Considerations")

tip

**Performance Tips:** These recommendations help optimize MLflow performance for your specific use case.

### SQLite Performance[​](#sqlite-performance "Direct link to SQLite Performance")

* **File System**: Use SSD storage for better I/O performance
* **Concurrent Access**: SQLite has limitations with concurrent writes
* **File Size**: Monitor database file size and implement cleanup strategies

warning

**Concurrency Limits:** SQLite is not suitable for high-concurrency environments. Consider PostgreSQL for multi-user scenarios.

### Resource Optimization[​](#resource-optimization "Direct link to Resource Optimization")

* **Memory**: Allocate sufficient memory for MLflow operations
* **CPU**: Monitor CPU usage and adjust limits accordingly
* **Storage**: Use fast storage for better database performance

info

**Resource Monitoring:** Use Kubernetes metrics to monitor resource usage and optimize allocation.

## Security Considerations[​](#security-considerations "Direct link to Security Considerations")

warning

**Security Best Practices:** Implement these security measures to protect your MLflow deployment.

### Network Security[​](#network-security "Direct link to Network Security")

* Use ingress with TLS for external access
* Configure network policies to restrict pod-to-pod communication
* Use service mesh for advanced traffic management

### Data Security[​](#data-security "Direct link to Data Security")

* Enable authentication for all production deployments
* Use Kubernetes secrets for sensitive configuration
* Implement regular backups for data protection

danger

**Production Security:** Never deploy MLflow without authentication in production environments.

## Next Steps[​](#next-steps "Direct link to Next Steps")

tip

**Getting Started:** Follow these guides to enhance your MLflow deployment.

* For production use, consider [PostgreSQL backend](/docs/charts/mlflow/postgresql-backend-installation.md)
* Set up [authentication](/docs/charts/mlflow/authentication-configuration.md)
* Configure [AWS S3](/docs/charts/mlflow/aws-s3-integration.md) or [Azure Blob Storage](/docs/charts/mlflow/azure-blob-storage-integration.md) for artifacts
* Enable [autoscaling](/docs/charts/mlflow/autoscaling-setup.md) for high availability

info

**Production Migration:** Consider migrating to PostgreSQL when you need production-grade features or multi-user support.


---

# Google Cloud Storage Integration

This guide covers configuring MLflow to use Google Cloud Storage (GCS) for artifact storage. GCS provides scalable, durable storage for MLflow artifacts with enterprise-grade security and global availability.

info

**GCS Integration:** Google Cloud Storage is ideal for organizations using Google Cloud Platform, providing seamless integration with GCP services and global availability.

<!-- -->

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**GCP Setup:** Ensure you have proper GCP access and permissions before configuring GCS integration.

* Google Cloud Platform account with GCS access
* Google Cloud CLI configured or service account credentials available
* Kubernetes cluster with MLflow deployed
* GCS bucket created and accessible

## GCS Bucket Setup[​](#gcs-bucket-setup "Direct link to GCS Bucket Setup")

tip

**Bucket Configuration:** Proper bucket setup ensures data durability and cost optimization for your MLflow artifacts.

### 1. Create GCS Bucket[​](#1-create-gcs-bucket "Direct link to 1. Create GCS Bucket")

```
gsutil mb gs://your-mlflow-artifacts-bucket
```

### 2. Configure Bucket Versioning (Recommended)[​](#2-configure-bucket-versioning-recommended "Direct link to 2. Configure Bucket Versioning (Recommended)")

```
gsutil versioning set on gs://your-mlflow-artifacts-bucket
```

tip

**Versioning:** Enable versioning to protect against accidental deletions and maintain artifact history.

### 3. Configure Bucket Lifecycle (Optional)[​](#3-configure-bucket-lifecycle-optional "Direct link to 3. Configure Bucket Lifecycle (Optional)")

```
gsutil lifecycle set lifecycle.json gs://your-mlflow-artifacts-bucket
```

Create `lifecycle.json`:

```
{

  "rule": [

    {

      "action": {"type": "Delete"},

      "condition": {

        "age": 365,

        "isLive": true

      }

    }

  ]

}
```

info

**Lifecycle Management:** Configure lifecycle policies to automatically manage storage costs and clean up old artifacts.

## Authentication Options[​](#authentication-options "Direct link to Authentication Options")

warning

**Security Best Practice:** Use Workload Identity instead of service account keys for production deployments to improve security and eliminate credential management.

### Option 1: Service Account Key (Development)[​](#option-1-service-account-key-development "Direct link to Option 1: Service Account Key (Development)")

Create a service account with Storage Object Admin role:

```
# Create service account

gcloud iam service-accounts create mlflow-gcs-sa \

  --display-name="MLflow GCS Service Account"



# Grant Storage Object Admin role

gcloud projects add-iam-policy-binding YOUR_PROJECT_ID \

  --member="serviceAccount:mlflow-gcs-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com" \

  --role="roles/storage.objectAdmin"



# Create and download key

gcloud iam service-accounts keys create mlflow-gcs-key.json \

  --iam-account=mlflow-gcs-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com
```

tip

**Development Use:** Service account keys are suitable for development and testing but not recommended for production.

### Option 2: Workload Identity (GKE Production)[​](#option-2-workload-identity-gke-production "Direct link to Option 2: Workload Identity (GKE Production)")

If using GKE with Workload Identity:

```
# Enable Workload Identity

gcloud container clusters update your-cluster \

  --workload-pool=YOUR_PROJECT_ID.svc.id.goog \

  --zone=your-zone



# Create service account

gcloud iam service-accounts create mlflow-gcs-sa \

  --display-name="MLflow GCS Service Account"



# Grant Storage Object Admin role

gcloud projects add-iam-policy-binding YOUR_PROJECT_ID \

  --member="serviceAccount:mlflow-gcs-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com" \

  --role="roles/storage.objectAdmin"



# Bind service account to Kubernetes service account

gcloud iam service-accounts add-iam-policy-binding \

  mlflow-gcs-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com \

  --role="roles/iam.workloadIdentityUser" \

  --member="serviceAccount:YOUR_PROJECT_ID.svc.id.goog[mlflow/mlflow]"
```

info

**GKE Best Practice:** Workload Identity provides the most secure and manageable way to grant GCP permissions to GKE pods.

## Kubernetes Secret for GCS Credentials[​](#kubernetes-secret-for-gcs-credentials "Direct link to Kubernetes Secret for GCS Credentials")

warning

**Credential Security:** Store GCS credentials in Kubernetes secrets rather than hardcoding them in configuration files.

### Create Secret with Service Account Key[​](#create-secret-with-service-account-key "Direct link to Create Secret with Service Account Key")

```
kubectl create secret generic gcs-credentials \

  --namespace mlflow \

  --from-file=key.json=mlflow-gcs-key.json
```

## MLflow Configuration[​](#mlflow-configuration "Direct link to MLflow Configuration")

<!-- -->

info

**Complete Setup:** This configuration demonstrates a production-ready MLflow setup with PostgreSQL backend and GCS artifact storage.

### Option 1: Using Service Account Key[​](#option-1-using-service-account-key "Direct link to Option 1: Using Service Account Key")

Create `values.yaml`:

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  gcs:

    enabled: true

    bucket: your-mlflow-artifacts-bucket

    path: ""  # Optional: GCS bucket folder



extraEnvVars:

  GOOGLE_APPLICATION_CREDENTIALS: /etc/gcs/key.json

  MLFLOW_GCS_DEFAULT_TIMEOUT: "60"

  MLFLOW_GCS_UPLOAD_CHUNK_SIZE: "104857600"

  MLFLOW_GCS_DOWNLOAD_CHUNK_SIZE: "104857600"



extraVolumes:

  - name: gcs-credentials

    secret:

      secretName: gcs-credentials



extraVolumeMounts:

  - name: gcs-credentials

    mountPath: /etc/gcs

    readOnly: true
```

### Option 2: Using Workload Identity[​](#option-2-using-workload-identity "Direct link to Option 2: Using Workload Identity")

```
serviceAccount:

  create: true

  annotations:

    iam.gke.io/gcp-service-account: mlflow-gcs-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com

  name: mlflow



backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  gcs:

    enabled: true

    bucket: your-mlflow-artifacts-bucket

    path: ""

    # No credentials needed with Workload Identity
```

### Option 3: Using Helm Set Commands[​](#option-3-using-helm-set-commands "Direct link to Option 3: Using Helm Set Commands")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.databaseMigration=true \

  --set backendStore.postgres.enabled=true \

  --set backendStore.postgres.host=postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com \

  --set backendStore.postgres.database=mlflow \

  --set backendStore.postgres.user=mlflowuser \

  --set backendStore.postgres.password=Pa33w0rd! \

  --set artifactRoot.gcs.enabled=true \

  --set artifactRoot.gcs.bucket=your-mlflow-artifacts-bucket
```

## Verification[​](#verification "Direct link to Verification")

### Test GCS Access[​](#test-gcs-access "Direct link to Test GCS Access")

```
# Test from within the MLflow pod

kubectl exec -it deployment/mlflow -n mlflow -- \

  gsutil ls gs://your-mlflow-artifacts-bucket
```

### Check MLflow Logs[​](#check-mlflow-logs "Direct link to Check MLflow Logs")

```
kubectl logs deployment/mlflow -n mlflow | grep -i "gcs\|artifact"
```

### Test Artifact Upload[​](#test-artifact-upload "Direct link to Test Artifact Upload")

Access MLflow UI and create an experiment with artifacts to verify GCS integration.

## Advanced Configuration[​](#advanced-configuration "Direct link to Advanced Configuration")

### Custom GCS Endpoint[​](#custom-gcs-endpoint "Direct link to Custom GCS Endpoint")

For GCS-compatible storage or custom endpoints:

```
extraEnvVars:

  STORAGE_EMULATOR_HOST: http://your-custom-gcs-endpoint:4443
```

### GCS Performance Optimization[​](#gcs-performance-optimization "Direct link to GCS Performance Optimization")

Configure chunk sizes and timeouts for better performance:

```
extraEnvVars:

  MLFLOW_GCS_DEFAULT_TIMEOUT: "120"  # 2 minutes

  MLFLOW_GCS_UPLOAD_CHUNK_SIZE: "209715200"  # 200MB

  MLFLOW_GCS_DOWNLOAD_CHUNK_SIZE: "209715200"  # 200MB
```

### Custom GCS Path[​](#custom-gcs-path "Direct link to Custom GCS Path")

Store artifacts in a specific GCS folder:

```
artifactRoot:

  gcs:

    enabled: true

    bucket: your-mlflow-artifacts-bucket

    path: mlflow/artifacts  # Optional folder path
```

### GCS Encryption[​](#gcs-encryption "Direct link to GCS Encryption")

Enable customer-managed encryption keys:

```
# Create encryption key

gcloud kms keys create mlflow-key \

  --keyring mlflow-keyring \

  --location global \

  --purpose encryption



# Configure bucket encryption

gsutil kms encryption -k projects/YOUR_PROJECT_ID/locations/global/keyRings/mlflow-keyring/cryptoKeys/mlflow-key gs://your-mlflow-artifacts-bucket
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Authentication Failed**: Check service account permissions and credentials
2. **Bucket Not Found**: Ensure bucket exists and is accessible
3. **Network Issues**: Check firewall rules and VPC access
4. **Permission Denied**: Verify IAM roles and service account configuration
5. **Timeout Issues**: Adjust timeout values for large artifacts

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check GCS credentials in pod

kubectl exec -it deployment/mlflow -n mlflow -- env | grep GOOGLE



# Test GCS connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  gsutil ls gs://your-mlflow-artifacts-bucket



# Check MLflow GCS configuration

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import mlflow; print(mlflow.get_artifact_uri())"



# Test service account authentication

kubectl exec -it deployment/mlflow -n mlflow -- \

  gcloud auth list
```

## Cost Optimization[​](#cost-optimization "Direct link to Cost Optimization")

* Use GCS lifecycle management for cost-effective storage
* Configure object lifecycle policies to move old artifacts to cheaper storage classes
* Monitor GCS usage with Cloud Monitoring
* Use GCS Transfer Service for large data migrations

## Security Best Practices[​](#security-best-practices "Direct link to Security Best Practices")

* Use Workload Identity instead of service account keys when possible
* Enable GCS bucket encryption
* Configure IAM policies with least privilege access
* Use VPC Service Controls for network security
* Regularly rotate service account keys
* Enable audit logging for GCS operations

## Monitoring and Alerting[​](#monitoring-and-alerting "Direct link to Monitoring and Alerting")

### Cloud Monitoring Integration[​](#cloud-monitoring-integration "Direct link to Cloud Monitoring Integration")

```
extraEnvVars:

  GOOGLE_CLOUD_PROJECT: your-project-id

  GOOGLE_APPLICATION_CREDENTIALS: /etc/gcs/key.json
```

### GCS Metrics[​](#gcs-metrics "Direct link to GCS Metrics")

Enable monitoring for GCS operations:

```
# Enable GCS monitoring

gcloud services enable storage-component.googleapis.com



# Create monitoring dashboard

gcloud monitoring dashboards create --config-from-file=dashboard.json
```

## Production Configuration Example[​](#production-configuration-example "Direct link to Production Configuration Example")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  gcs:

    enabled: true

    bucket: your-mlflow-artifacts-bucket

    path: ""



serviceAccount:

  create: true

  annotations:

    iam.gke.io/gcp-service-account: mlflow-gcs-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com

  name: mlflow



serviceMonitor:

  enabled: true

  namespace: monitoring

  interval: 30s

  telemetryPath: /metrics

  labels:

    release: prometheus

  timeout: 10s

  targetLabels: []



resources:

  requests:

    cpu: 500m

    memory: 1Gi

  limits:

    cpu: 2

    memory: 4Gi



ingress:

  enabled: true

  className: nginx

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: mlflow-tls

      hosts:

        - mlflow.your-domain.com
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Set up [authentication](/docs/charts/mlflow/authentication-configuration.md) for MLflow UI
* Configure [autoscaling](/docs/charts/mlflow/autoscaling-setup.md) for high availability
* Set up monitoring and alerting for GCS usage
* Configure backup and disaster recovery strategies
* Consider [AWS S3](/docs/charts/mlflow/aws-s3-integration.md) or [Azure Blob Storage](/docs/charts/mlflow/azure-blob-storage-integration.md) as alternatives

### Custom Environment Variables[​](#custom-environment-variables "Direct link to Custom Environment Variables")

```
extraEnvVars:

  # GCS Configuration

  MLFLOW_GCS_DEFAULT_TIMEOUT: "60"  # GCS transfer timeout in seconds

  MLFLOW_GCS_UPLOAD_CHUNK_SIZE: "104857600"  # GCS upload chunk size (100MB)

  MLFLOW_GCS_DOWNLOAD_CHUNK_SIZE: "104857600"  # GCS download chunk size (100MB)
```


---

# MySQL Backend Installation

This guide covers setting up MLflow with MySQL as the backend database. MySQL is a popular alternative to PostgreSQL and provides good performance for MLflow deployments.

info

**Alternative Database:** MySQL is a viable alternative to PostgreSQL for MLflow deployments, offering good performance and wide compatibility with existing infrastructure.

<!-- -->

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**Requirements:** Ensure you have all prerequisites installed and configured before proceeding with MySQL setup.

* Kubernetes cluster (v1.16+)
* Helm 3.x installed
* kubectl configured
* MySQL database (can be deployed in-cluster or external)
* Storage class for PVC (if using in-cluster MySQL)

## Option 1: Using External MySQL[​](#option-1-using-external-mysql "Direct link to Option 1: Using External MySQL")

tip

**External Database:** Using external MySQL (like RDS, Cloud SQL, or Azure Database) is recommended for production as it provides managed backups, high availability, and easier maintenance.

### 1. Prepare MySQL Database[​](#1-prepare-mysql-database "Direct link to 1. Prepare MySQL Database")

Create a database and user for MLflow:

```
CREATE DATABASE mlflow;

CREATE USER 'mlflow_user'@'%' IDENTIFIED BY 'your_secure_password';

GRANT ALL PRIVILEGES ON mlflow.* TO 'mlflow_user'@'%';

FLUSH PRIVILEGES;
```

### 2. Install MLflow with External MySQL[​](#2-install-mlflow-with-external-mysql "Direct link to 2. Install MLflow with External MySQL")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.databaseMigration=true \

  --set backendStore.mysql.enabled=true \

  --set backendStore.mysql.host=your-mysql-host \

  --set backendStore.mysql.port=3306 \

  --set backendStore.mysql.database=mlflow \

  --set backendStore.mysql.user=mlflow_user \

  --set backendStore.mysql.password=your_secure_password
```

warning

**Security:** Never hardcode database passwords in command line arguments. Use Kubernetes secrets or environment variables for sensitive data.

## Option 2: Deploy MySQL in Kubernetes[​](#option-2-deploy-mysql-in-kubernetes "Direct link to Option 2: Deploy MySQL in Kubernetes")

info

**In-Cluster Database:** Deploying MySQL in Kubernetes is suitable for development and testing environments, but external managed databases are recommended for production.

### 1. Install MySQL using Bitnami Chart[​](#1-install-mysql-using-bitnami-chart "Direct link to 1. Install MySQL using Bitnami Chart")

```
helm repo add bitnami https://charts.bitnami.com/bitnami

helm repo update



helm install mysql bitnami/mysql \

  --namespace mlflow \

  --set auth.rootPassword=root_password \

  --set auth.database=mlflow \

  --set primary.persistence.size=10Gi
```

### 2. Get MySQL Connection Details[​](#2-get-mysql-connection-details "Direct link to 2. Get MySQL Connection Details")

```
export MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace mlflow mysql -o jsonpath="{.data.mysql-root-password}" | base64 -d)

export MYSQL_HOST=$(kubectl get svc --namespace mlflow mysql -o jsonpath="{.spec.clusterIP}")
```

### 3. Create MLflow User[​](#3-create-mlflow-user "Direct link to 3. Create MLflow User")

```
kubectl run mysql-client --rm -it --restart=Never --image=mysql:8.0 --namespace mlflow -- \

  mysql -h $MYSQL_HOST -u root -p$MYSQL_ROOT_PASSWORD -e "

CREATE USER 'mlflow_user'@'%' IDENTIFIED BY 'mlflow_password';

GRANT ALL PRIVILEGES ON mlflow.* TO 'mlflow_user'@'%';

FLUSH PRIVILEGES;

"
```

### 4. Install MLflow with In-Cluster MySQL[​](#4-install-mlflow-with-in-cluster-mysql "Direct link to 4. Install MLflow with In-Cluster MySQL")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.databaseMigration=true \

  --set backendStore.mysql.enabled=true \

  --set backendStore.mysql.host=$MYSQL_HOST \

  --set backendStore.mysql.port=3306 \

  --set backendStore.mysql.database=mlflow \

  --set backendStore.mysql.user=mlflow_user \

  --set backendStore.mysql.password=mlflow_password
```

## Option 3: Using Existing Database Secret[​](#option-3-using-existing-database-secret "Direct link to Option 3: Using Existing Database Secret")

tip

**Secret Management:** Using Kubernetes secrets for database credentials is a security best practice that keeps sensitive data out of configuration files.

### 1. Create Database Secret[​](#1-create-database-secret "Direct link to 1. Create Database Secret")

```
kubectl create secret generic mysql-database-secret \

  --namespace mlflow \

  --from-literal=username=mlflow_user \

  --from-literal=password=your_secure_password
```

### 2. Configure MLflow with Existing Secret[​](#2-configure-mlflow-with-existing-secret "Direct link to 2. Configure MLflow with Existing Secret")

```
backendStore:

  databaseMigration: true

  mysql:

    enabled: true

    host: mysql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 3306

    database: mlflow



  existingDatabaseSecret:

    name: mysql-database-secret

    usernameKey: username

    passwordKey: password
```

## Configuration with Values File[​](#configuration-with-values-file "Direct link to Configuration with Values File")

<!-- -->

info

**Complete Setup:** This configuration demonstrates a production-ready MLflow setup with MySQL backend and proper resource management.

Create a `values.yaml` file:

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  mysql:

    enabled: true

    host: mysql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 3306

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!

    driver: pymysql



artifactRoot:

  defaultArtifactRoot: ./mlruns

  defaultArtifactsDestination: ./mlartifacts



service:

  type: ClusterIP

  port: 5000



ingress:

  enabled: false



persistence:

  enabled: true

  size: 10Gi



# Optional: Configure MySQL connection pooling and SSL

extraEnvVars:

  MLFLOW_SQLALCHEMYSTORE_POOL_SIZE: "10"  # SQLAlchemy connection pool size

  MLFLOW_SQLALCHEMYSTORE_MAX_OVERFLOW: "20"  # SQLAlchemy max overflow connections

  MLFLOW_SQLALCHEMYSTORE_POOL_RECYCLE: "3600"  # SQLAlchemy pool recycle time

  MLFLOW_SQLALCHEMYSTORE_ECHO: "false"  # Enable SQLAlchemy query logging

  MLFLOW_MYSQL_SSL_CA: "/path/to/ca-cert.pem"  # MySQL SSL CA certificate path

  MLFLOW_MYSQL_SSL_CERT: "/path/to/client-cert.pem"  # MySQL SSL client certificate path

  MLFLOW_MYSQL_SSL_KEY: "/path/to/client-key.pem"  # MySQL SSL client key path
```

Install with the configuration:

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  -f values.yaml
```

## Database Migration Features[​](#database-migration-features "Direct link to Database Migration Features")

### Automatic Schema Migrations[​](#automatic-schema-migrations "Direct link to Automatic Schema Migrations")

The chart supports automatic database schema migrations using init containers:

```
backendStore:

  databaseMigration: true  # Enable automatic migrations

  mysql:

    enabled: true

    host: your-mysql-host

    database: mlflow

    user: mlflowuser

    password: your-password

    driver: pymysql
```

### Database Connection Health Checks[​](#database-connection-health-checks "Direct link to Database Connection Health Checks")

Add database availability checks before starting MLflow:

```
backendStore:

  databaseConnectionCheck: true  # Enable connection checks

  mysql:

    enabled: true

    host: your-mysql-host

    database: mlflow

    user: mlflowuser

    password: your-password

    driver: pymysql
```

### Migration from SQLite[​](#migration-from-sqlite "Direct link to Migration from SQLite")

When migrating from SQLite to MySQL:

```
backendStore:

  databaseMigration: true

  mysql:

    enabled: true

    host: mysql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 3306

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!

    driver: pymysql
```

## Bitnami MySQL Integration[​](#bitnami-mysql-integration "Direct link to Bitnami MySQL Integration")

### Complete Bitnami MySQL Setup[​](#complete-bitnami-mysql-setup "Direct link to Complete Bitnami MySQL Setup")

<!-- -->

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true



mysql:

  enabled: true

  architecture: standalone



  primary:

    service:

      ports:

        mysql: 3306



    persistence:

      enabled: true

      existingClaim: ""



  auth:

    username: mlflowuser

    password: Pa33w0rd!

    database: mlflow
```

## MySQL-Specific Considerations[​](#mysql-specific-considerations "Direct link to MySQL-Specific Considerations")

### Character Set and Collation[​](#character-set-and-collation "Direct link to Character Set and Collation")

Ensure your MySQL database uses UTF-8 encoding:

```
ALTER DATABASE mlflow CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
```

### Connection String Format[​](#connection-string-format "Direct link to Connection String Format")

The MySQL connection string format for MLflow is:

```
mysql+pymysql://username:password@host:port/database
```

### Required Python Dependencies[​](#required-python-dependencies "Direct link to Required Python Dependencies")

The MLflow container includes `pymysql` for MySQL connectivity. If you're using a custom image, ensure it includes:

```
RUN pip install pymysql
```

## Database Migration[​](#database-migration "Direct link to Database Migration")

MLflow will automatically create the required tables on first startup when `databaseMigration: true` is enabled. The init container will handle schema migrations.

### Manual Migration (if needed)[​](#manual-migration-if-needed "Direct link to Manual Migration (if needed)")

If you need to run migrations manually:

```
# Export data from SQLite (if migrating from SQLite)

mlflow db export-sqlite mlflow.db > mlflow_export.sql



# Run migrations on MySQL

mlflow db upgrade mysql+pymysql://mlflow_user:password@host:3306/mlflow
```

## Verification[​](#verification "Direct link to Verification")

### Check MLflow Pod Status[​](#check-mlflow-pod-status "Direct link to Check MLflow Pod Status")

```
kubectl get pods -n mlflow
```

### Verify Database Connection[​](#verify-database-connection "Direct link to Verify Database Connection")

```
kubectl logs deployment/mlflow -n mlflow | grep -i "mysql\|database"
```

### Check Migration Status[​](#check-migration-status "Direct link to Check Migration Status")

```
kubectl logs deployment/mlflow -c init-mlflow -n mlflow
```

### Test MySQL Connection[​](#test-mysql-connection "Direct link to Test MySQL Connection")

```
kubectl run mysql-test --rm -it --image=mysql:8.0 --restart=Never --namespace mlflow -- \

  mysql -h $MYSQL_HOST -u mlflow_user -pmlflow_password mlflow -e "SHOW TABLES;"
```

### Access MLflow UI[​](#access-mlflow-ui "Direct link to Access MLflow UI")

```
kubectl port-forward svc/mlflow -n mlflow 5000:5000
```

Visit `http://localhost:5000` in your browser.

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

tip

**Log Level:** Set `log.level: debug` in your values to get more detailed logs for troubleshooting MySQL connection or migration issues.

### Common MySQL Issues[​](#common-mysql-issues "Direct link to Common MySQL Issues")

1. **Connection refused**: Check MySQL service and network policies
2. **Authentication failed**: Verify username/password and host permissions
3. **Character set issues**: Ensure UTF-8 encoding is configured
4. **SSL connection errors**: Add `?ssl_mode=DISABLED` to connection string if needed
5. **Migration failures**: Check init container logs for migration errors

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check MySQL logs

kubectl logs -f deployment/mysql -n mlflow



# Test connection from MLflow pod

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import pymysql; pymysql.connect(host='$MYSQL_HOST', user='mlflow_user', password='mlflow_password', database='mlflow')"



# Check MLflow logs

kubectl logs -f deployment/mlflow -n mlflow



# Check init container logs

kubectl logs deployment/mlflow -c init-mlflow -n mlflow
```

### Connection Issues[​](#connection-issues "Direct link to Connection Issues")

```
# Test network connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  nc -zv $MYSQL_HOST 3306



# Check MySQL service

kubectl get svc mysql -n mlflow



# Verify database credentials

kubectl get secret mysql-database-secret -n mlflow -o yaml
```

## Production Considerations[​](#production-considerations "Direct link to Production Considerations")

* Use managed MySQL services (AWS RDS, Google Cloud SQL, Azure Database)
* Configure automated backups and point-in-time recovery
* Set up monitoring and alerting
* Use connection pooling for high-traffic deployments
* Consider read replicas for scaling
* Enable SSL/TLS for database connections

### High Availability Setup[​](#high-availability-setup "Direct link to High Availability Setup")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  mysql:

    enabled: true

    host: your-mysql-cluster-endpoint

    port: 3306

    database: mlflow

    user: mlflowuser

    password: your-password

    driver: pymysql



# Configure connection pooling for HA

extraEnvVars:

  MLFLOW_SQLALCHEMY_POOL_SIZE: "20"

  MLFLOW_SQLALCHEMY_MAX_OVERFLOW: "30"

  MLFLOW_SQLALCHEMY_POOL_TIMEOUT: "30"

  MLFLOW_SQLALCHEMY_POOL_RECYCLE: "3600"
```

## Migration from Other Databases[​](#migration-from-other-databases "Direct link to Migration from Other Databases")

### From SQLite[​](#from-sqlite "Direct link to From SQLite")

1. Export data from SQLite:

```
mlflow db export-sqlite mlflow.db > mlflow_export.sql
```

2. Convert and import to MySQL (requires manual conversion of SQLite-specific syntax)

### From PostgreSQL[​](#from-postgresql "Direct link to From PostgreSQL")

Use MLflow's built-in migration tools or export/import functionality.

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Configure [artifact storage](/docs/charts/mlflow/aws-s3-integration.md) for production
* Set up [authentication](/docs/charts/mlflow/authentication-configuration.md)
* Configure [autoscaling](/docs/charts/mlflow/autoscaling-setup.md) for high availability
* Set up monitoring with [ServiceMonitor](/docs/charts/mlflow/usage.md#monitoring)


---

# PostgreSQL Backend Installation

This guide covers setting up MLflow with PostgreSQL as the backend database. This configuration is recommended for production deployments as it provides better performance, scalability, and data integrity compared to SQLite.

info

**Production Database:** PostgreSQL is the recommended database backend for production MLflow deployments, offering better performance, scalability, and concurrent access capabilities.

<!-- -->

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**Requirements:** Ensure you have all prerequisites installed and configured before proceeding with PostgreSQL setup.

* Kubernetes cluster (v1.16+)
* Helm 3.x installed
* kubectl configured
* PostgreSQL database (can be deployed in-cluster or external)
* Storage class for PVC (if using in-cluster PostgreSQL)

## Option 1: Using External PostgreSQL[​](#option-1-using-external-postgresql "Direct link to Option 1: Using External PostgreSQL")

tip

**External Database:** Using external PostgreSQL (like RDS, Cloud SQL, or Azure Database) is recommended for production as it provides managed backups, high availability, and easier maintenance.

### 1. Prepare PostgreSQL Database[​](#1-prepare-postgresql-database "Direct link to 1. Prepare PostgreSQL Database")

Create a database and user for MLflow:

```
CREATE DATABASE mlflow;

CREATE USER mlflow_user WITH PASSWORD 'your_secure_password';

GRANT ALL PRIVILEGES ON DATABASE mlflow TO mlflow_user;

GRANT ALL PRIVILEGES ON SCHEMA public TO mlflow_user;
```

If you want user access with more limited privileges on the public schema:

```
CREATE DATABASE mlflow;

CREATE USER mlflow_user WITH PASSWORD 'your_secure_password';

GRANT ALL PRIVILEGES ON DATABASE mlflow TO mlflow_user;

\c mlflow

GRANT USAGE, CREATE ON SCHEMA public TO mlflow_user;
```

Or if you want to use mlflow specific schema, please use:

```
CREATE DATABASE mlflow;

CREATE USER mlflow_user WITH PASSWORD 'your_secure_password';

GRANT ALL PRIVILEGES ON DATABASE mlflow TO mlflow_user;

\c mlflow mlflow_user

CREATE SCHEMA mlflow;

ALTER ROLE mlflow_user IN DATABASE mlflow

SET search_path = mlflow;
```

### 2. Install MLflow with External PostgreSQL[​](#2-install-mlflow-with-external-postgresql "Direct link to 2. Install MLflow with External PostgreSQL")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.databaseMigration=true \

  --set backendStore.postgres.enabled=true \

  --set backendStore.postgres.host=your-postgres-host \

  --set backendStore.postgres.port=5432 \

  --set backendStore.postgres.database=mlflow \

  --set backendStore.postgres.user=mlflow_user \

  --set backendStore.postgres.password=your_secure_password
```

warning

**Security:** Never hardcode database passwords in command line arguments. Use Kubernetes secrets or environment variables for sensitive data.

## Option 2: Deploy PostgreSQL in Kubernetes[​](#option-2-deploy-postgresql-in-kubernetes "Direct link to Option 2: Deploy PostgreSQL in Kubernetes")

info

**In-Cluster Database:** Deploying PostgreSQL in Kubernetes is suitable for development and testing environments, but external managed databases are recommended for production.

### 1. Install PostgreSQL using Bitnami Chart[​](#1-install-postgresql-using-bitnami-chart "Direct link to 1. Install PostgreSQL using Bitnami Chart")

```
helm repo add bitnami https://charts.bitnami.com/bitnami

helm repo update



helm install postgres bitnami/postgresql \

  --namespace mlflow \

  --set auth.postgresPassword=mlflow_password \

  --set auth.database=mlflow \

  --set primary.persistence.size=10Gi
```

### 2. Get PostgreSQL Connection Details[​](#2-get-postgresql-connection-details "Direct link to 2. Get PostgreSQL Connection Details")

```
export POSTGRES_PASSWORD=$(kubectl get secret --namespace mlflow postgres -o jsonpath="{.data.postgres-password}" | base64 -d)

export POSTGRES_HOST=$(kubectl get svc --namespace mlflow postgres -o jsonpath="{.spec.clusterIP}")
```

### 3. Install MLflow with In-Cluster PostgreSQL[​](#3-install-mlflow-with-in-cluster-postgresql "Direct link to 3. Install MLflow with In-Cluster PostgreSQL")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --set backendStore.databaseMigration=true \

  --set backendStore.postgres.enabled=true \

  --set backendStore.postgres.host=$POSTGRES_HOST \

  --set backendStore.postgres.port=5432 \

  --set backendStore.postgres.database=mlflow \

  --set backendStore.postgres.user=postgres \

  --set backendStore.postgres.password=$POSTGRES_PASSWORD
```

## Option 3: Using Existing Database Secret[​](#option-3-using-existing-database-secret "Direct link to Option 3: Using Existing Database Secret")

tip

**Secret Management:** Using Kubernetes secrets for database credentials is a security best practice that keeps sensitive data out of configuration files.

### 1. Create Database Secret[​](#1-create-database-secret "Direct link to 1. Create Database Secret")

```
kubectl create secret generic postgres-database-secret \

  --namespace mlflow \

  --from-literal=username=mlflow_user \

  --from-literal=password=your_secure_password
```

### 2. Configure MLflow with Existing Secret[​](#2-configure-mlflow-with-existing-secret "Direct link to 2. Configure MLflow with Existing Secret")

```
backendStore:

  databaseMigration: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow



  existingDatabaseSecret:

    name: postgres-database-secret

    usernameKey: username

    passwordKey: password
```

## Configuration with Values File[​](#configuration-with-values-file "Direct link to Configuration with Values File")

<!-- -->

info

**Complete Setup:** This configuration demonstrates a production-ready MLflow setup with PostgreSQL backend and proper resource management.

Create a `values.yaml` file:

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  defaultArtifactRoot: ./mlruns

  defaultArtifactsDestination: ./mlartifacts



service:

  type: ClusterIP

  port: 5000



ingress:

  enabled: false



persistence:

  enabled: true

  size: 10Gi



# Optional: Configure PostgreSQL connection pooling

extraEnvVars:

  MLFLOW_SQLALCHEMYSTORE_POOL_SIZE: "10"  # SQLAlchemy connection pool size

  MLFLOW_SQLALCHEMYSTORE_MAX_OVERFLOW: "20"  # SQLAlchemy max overflow connections

  MLFLOW_SQLALCHEMYSTORE_POOL_RECYCLE: "3600"  # SQLAlchemy pool recycle time

  MLFLOW_SQLALCHEMYSTORE_ECHO: "false"  # Enable SQLAlchemy query logging
```

Install with the configuration:

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  -f values.yaml
```

## Database Migration Features[​](#database-migration-features "Direct link to Database Migration Features")

tip

**Migration Safety:** Database migrations are disabled by default. Enable them only when you're ready to update your database schema.

### Automatic Schema Migrations[​](#automatic-schema-migrations "Direct link to Automatic Schema Migrations")

The chart supports automatic database schema migrations using init containers:

```
backendStore:

  databaseMigration: true  # Enable automatic migrations

  postgres:

    enabled: true

    host: your-postgres-host

    database: mlflow

    user: mlflowuser

    password: your-password
```

### Database Connection Health Checks[​](#database-connection-health-checks "Direct link to Database Connection Health Checks")

Add database availability checks before starting MLflow:

```
backendStore:

  databaseConnectionCheck: true  # Enable connection checks

  postgres:

    enabled: true

    host: your-postgres-host

    database: mlflow

    user: mlflowuser

    password: your-password
```

### Migration from SQLite[​](#migration-from-sqlite "Direct link to Migration from SQLite")

When migrating from SQLite to PostgreSQL:

```
backendStore:

  databaseMigration: true

  postgres:

    enabled: true

    host: postgresql-instance1.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!
```

## Bitnami PostgreSQL Integration[​](#bitnami-postgresql-integration "Direct link to Bitnami PostgreSQL Integration")

### Complete Bitnami PostgreSQL Setup[​](#complete-bitnami-postgresql-setup "Direct link to Complete Bitnami PostgreSQL Setup")

<!-- -->

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true



postgresql:

  enabled: true

  architecture: standalone



  primary:

    service:

      ports:

        postgresql: 5432



    persistence:

      enabled: true

      existingClaim: ""



  auth:

    username: mlflowuser

    password: Pa33w0rd!

    database: mlflow
```

## Database Migration[​](#database-migration "Direct link to Database Migration")

MLflow will automatically create the required tables on first startup when `databaseMigration: true` is enabled. The init container will handle schema migrations.

### Manual Migration (if needed)[​](#manual-migration-if-needed "Direct link to Manual Migration (if needed)")

If you need to run migrations manually:

```
# Export data from SQLite (if migrating from SQLite)

mlflow db export-sqlite mlflow.db > mlflow_export.sql



# Run migrations on PostgreSQL

mlflow db upgrade postgresql://mlflow_user:password@host:5432/mlflow
```

## Verification[​](#verification "Direct link to Verification")

### Check MLflow Pod Status[​](#check-mlflow-pod-status "Direct link to Check MLflow Pod Status")

```
kubectl get pods -n mlflow
```

### Verify Database Connection[​](#verify-database-connection "Direct link to Verify Database Connection")

```
kubectl logs deployment/mlflow -n mlflow | grep -i "database\|postgres"
```

### Check Migration Status[​](#check-migration-status "Direct link to Check Migration Status")

```
kubectl logs deployment/mlflow -c init-mlflow -n mlflow
```

### Test PostgreSQL Connection[​](#test-postgresql-connection "Direct link to Test PostgreSQL Connection")

```
# Test from within the cluster

kubectl run postgres-test --rm -it --image=postgres:13 --restart=Never -- \

  psql -h $POSTGRES_HOST -U postgres -d mlflow
```

### Access MLflow UI[​](#access-mlflow-ui "Direct link to Access MLflow UI")

```
kubectl port-forward svc/mlflow -n mlflow 5000:5000
```

Visit `http://localhost:5000` in your browser.

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

tip

**Log Level:** Set `log.level: debug` in your values to get more detailed logs for troubleshooting PostgreSQL connection or migration issues.

### Common PostgreSQL Issues[​](#common-postgresql-issues "Direct link to Common PostgreSQL Issues")

1. **Connection refused**: Check PostgreSQL service and network policies
2. **Authentication failed**: Verify username/password and database permissions
3. **Database not found**: Ensure database exists and user has access
4. **Migration failures**: Check init container logs for migration errors

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check PostgreSQL logs

kubectl logs -f deployment/postgres -n mlflow



# Test PostgreSQL connection from MLflow pod

kubectl exec -it deployment/mlflow -n mlflow -- \

  psql -h $POSTGRES_HOST -U postgres -d mlflow -c "SELECT version();"



# Check MLflow logs

kubectl logs -f deployment/mlflow -n mlflow



# Check init container logs

kubectl logs deployment/mlflow -c init-mlflow -n mlflow
```

### Connection Issues[​](#connection-issues "Direct link to Connection Issues")

```
# Test network connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  nc -zv $POSTGRES_HOST 5432



# Check PostgreSQL service

kubectl get svc postgres -n mlflow



# Verify database credentials

kubectl get secret postgres-database-secret -n mlflow -o yaml
```

## Production Considerations[​](#production-considerations "Direct link to Production Considerations")

* Use managed PostgreSQL services (AWS RDS, Google Cloud SQL, Azure Database)
* Configure automated backups
* Set up monitoring and alerting
* Use connection pooling for high-traffic deployments
* Consider read replicas for scaling
* Enable SSL/TLS for database connections

### High Availability Setup[​](#high-availability-setup "Direct link to High Availability Setup")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: your-postgres-cluster-endpoint

    port: 5432

    database: mlflow

    user: mlflowuser

    password: your-password



# Configure connection pooling for HA

extraEnvVars:

  MLFLOW_SQLALCHEMYSTORE_POOL_SIZE: "20"  # SQLAlchemy connection pool size

  MLFLOW_SQLALCHEMYSTORE_MAX_OVERFLOW: "30"  # SQLAlchemy max overflow connections

  MLFLOW_SQLALCHEMYSTORE_POOL_RECYCLE: "3600"  # SQLAlchemy pool recycle time

  MLFLOW_HTTP_REQUEST_TIMEOUT: "120"  # HTTP request timeout in seconds

  MLFLOW_HTTP_REQUEST_MAX_RETRIES: "7"  # Maximum HTTP retries
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Configure [artifact storage](/docs/charts/mlflow/aws-s3-integration.md) for production
* Set up [authentication](/docs/charts/mlflow/authentication-configuration.md)
* Configure [autoscaling](/docs/charts/mlflow/autoscaling-setup.md) for high availability
* Set up monitoring with [ServiceMonitor](/docs/charts/mlflow/usage.md#monitoring)


---

# Troubleshooting and Monitoring

This guide provides comprehensive troubleshooting steps and monitoring setup for MLflow deployments on Kubernetes. Learn how to diagnose common issues, set up monitoring, and maintain production deployments.

info

**Production Support:** This guide covers the most common issues you'll encounter with MLflow deployments and provides systematic approaches to diagnose and resolve them.

## Common Issues and Solutions[​](#common-issues-and-solutions "Direct link to Common Issues and Solutions")

warning

**Critical Issues:** Database and authentication issues are the most common causes of MLflow deployment failures. Start troubleshooting here if your deployment isn't working.

### Database Connection Issues[​](#database-connection-issues "Direct link to Database Connection Issues")

#### PostgreSQL Connection Problems[​](#postgresql-connection-problems "Direct link to PostgreSQL Connection Problems")

**Symptoms:**

* Pod stuck in `CrashLoopBackOff`
* Error messages: "connection refused", "authentication failed"
* Init container failures

**Diagnosis:**

```
# Check PostgreSQL service

kubectl get svc postgres -n mlflow



# Test network connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  nc -zv postgres-service 5432



# Check PostgreSQL logs

kubectl logs -f deployment/postgres -n mlflow



# Verify database credentials

kubectl get secret postgres-database-secret -n mlflow -o yaml
```

**Solutions:**

1. **Connection Refused**: Check if PostgreSQL is running and accessible
2. **Authentication Failed**: Verify username/password and database permissions
3. **Database Not Found**: Ensure database exists and user has access
4. **SSL Issues**: Add `?sslmode=disable` to connection string if needed

tip

**Quick Check:** Always verify network connectivity first, then check credentials and permissions.

#### MySQL Connection Problems[​](#mysql-connection-problems "Direct link to MySQL Connection Problems")

**Symptoms:**

* Similar to PostgreSQL issues
* PyMySQL driver errors
* Character set issues

**Diagnosis:**

```
# Test MySQL connection

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import pymysql; pymysql.connect(host='mysql-host', user='user', password='pass', database='mlflow')"



# Check MySQL logs

kubectl logs -f deployment/mysql -n mlflow
```

**Solutions:**

1. **Character Set**: Ensure UTF-8 encoding is configured
2. **Driver Issues**: Verify PyMySQL is installed
3. **SSL Connection**: Add `?ssl_mode=DISABLED` if needed

### Artifact Storage Issues[​](#artifact-storage-issues "Direct link to Artifact Storage Issues")

warning

**Storage Problems:** Artifact storage issues can prevent model tracking and deployment. These are often related to cloud provider permissions or network connectivity.

#### S3/MinIO Problems[​](#s3minio-problems "Direct link to S3/MinIO Problems")

**Symptoms:**

* Artifact upload/download failures
* Access denied errors
* Endpoint connection issues

**Diagnosis:**

```
# Test S3 access

kubectl exec -it deployment/mlflow -n mlflow -- \

  aws s3 ls s3://your-bucket



# Check S3 credentials

kubectl exec -it deployment/mlflow -n mlflow -- env | grep AWS



# Test MinIO endpoint

kubectl exec -it deployment/mlflow -n mlflow -- \

  aws s3 ls s3://mlflow --endpoint-url http://minio-service:9000
```

**Solutions:**

1. **Access Denied**: Check IAM permissions or access keys
2. **Endpoint Issues**: Verify MinIO service endpoint
3. **Region Mismatch**: Ensure S3 bucket and MLflow region match

#### Azure Blob Storage Problems[​](#azure-blob-storage-problems "Direct link to Azure Blob Storage Problems")

**Symptoms:**

* WASBS connection failures
* Authentication errors
* Container access issues

**Diagnosis:**

```
# Test Azure CLI connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  az storage account show --name your-storage-account



# Check Azure credentials

kubectl exec -it deployment/mlflow -n mlflow -- env | grep AZURE
```

**Solutions:**

1. **Authentication Failed**: Verify storage account key or service principal
2. **Container Not Found**: Ensure blob container exists
3. **Network Issues**: Check firewall rules and VPC access

### Authentication Issues[​](#authentication-issues "Direct link to Authentication Issues")

warning

**Security Issues:** Authentication problems can prevent access to MLflow entirely. These issues often relate to configuration or credential management.

#### Basic Authentication Problems[​](#basic-authentication-problems "Direct link to Basic Authentication Problems")

**Symptoms:**

* Login failures
* Session timeout issues
* Permission denied errors

**Diagnosis:**

```
# Check authentication configuration

kubectl exec -it deployment/mlflow -n mlflow -- env | grep MLFLOW



# View authentication logs

kubectl logs deployment/mlflow -n mlflow | grep -i "auth\|login"



# Test authentication endpoint

kubectl port-forward svc/mlflow -n mlflow 5000:5000

curl -u admin:password http://localhost:5000/health
```

**Solutions:**

1. **Login Failed**: Verify admin credentials
2. **Session Issues**: Check session timeout settings
3. **Permission Issues**: Verify user permissions and roles

#### LDAP Authentication Problems[​](#ldap-authentication-problems "Direct link to LDAP Authentication Problems")

**Symptoms:**

* LDAP connection failures
* User lookup errors
* Group membership issues

**Diagnosis:**

```
# Test LDAP connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  ldapsearch -H ldap://your-ldap-server:389 -D "uid=test,ou=people,dc=example,dc=com" -w password -b "dc=example,dc=com"



# Check LDAP configuration

kubectl get configmap mlflow -n mlflow -o yaml
```

**Solutions:**

1. **Connection Issues**: Verify LDAP server connectivity
2. **Certificate Issues**: Check TLS certificate configuration
3. **Search Issues**: Verify LDAP search base and filters

### Migration Issues[​](#migration-issues "Direct link to Migration Issues")

tip

**Migration Safety:** Database migrations are critical for schema updates. Always backup your database before enabling migrations in production.

#### Database Migration Failures[​](#database-migration-failures "Direct link to Database Migration Failures")

**Symptoms:**

* Init container failures
* Schema migration errors
* Data corruption issues

**Diagnosis:**

```
# Check migration logs

kubectl logs deployment/mlflow -c init-mlflow -n mlflow



# Check database schema

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import mlflow; mlflow.db.get_sqlalchemy_engine().execute('SELECT version_num FROM alembic_version')"
```

**Solutions:**

1. **Migration Errors**: Enable `databaseMigration: true`
2. **Permission Issues**: Ensure database user has migration permissions
3. **Schema Conflicts**: Check for existing schema conflicts

## Monitoring Setup[​](#monitoring-setup "Direct link to Monitoring Setup")

info

**Production Monitoring:** Comprehensive monitoring is essential for production MLflow deployments to ensure reliability and performance.

### Prometheus ServiceMonitor Configuration[​](#prometheus-servicemonitor-configuration "Direct link to Prometheus ServiceMonitor Configuration")

Enable comprehensive monitoring with Prometheus:

```
serviceMonitor:

  enabled: true

  namespace: monitoring

  interval: 30s

  telemetryPath: /metrics

  labels:

    release: prometheus

  timeout: 10s

  targetLabels: []

  metricRelabelings:

    - sourceLabels: [__name__]

      regex: 'mlflow_(.+)'

      targetLabel: mlflow_metric

      replacement: '${1}'
```

### Grafana Dashboard[​](#grafana-dashboard "Direct link to Grafana Dashboard")

Create a Grafana dashboard for MLflow monitoring:

```
{

  "annotations": {

    "list": [

      {

        "builtIn": 1,

        "datasource": "-- Grafana --",

        "enable": true,

        "hide": true,

        "iconColor": "rgba(0, 211, 255, 1)",

        "name": "Annotations & Alerts",

        "target": {

          "limit": 100,

          "matchAny": false,

          "tags": [],

          "type": "dashboard"

        },

        "type": "dashboard"

      }

    ]

  },

  "editable": true,

  "fiscalYearStartMonth": 0,

  "gnetId": null,

  "graphTooltip": 0,

  "id": 32,

  "links": [],

  "liveNow": false,

  "panels": [

    {

      "datasource": "prometheus",

      "fieldConfig": {

        "defaults": {

          "color": {

            "mode": "palette-classic"

          },

          "custom": {

            "axisLabel": "",

            "axisPlacement": "auto",

            "barAlignment": 0,

            "drawStyle": "line",

            "fillOpacity": 10,

            "gradientMode": "none",

            "hideFrom": {

              "legend": false,

              "tooltip": false,

              "viz": false

            },

            "lineInterpolation": "linear",

            "lineWidth": 1,

            "pointSize": 5,

            "scaleDistribution": {

              "type": "linear"

            },

            "showPoints": "never",

            "spanNulls": true,

            "stacking": {

              "group": "A",

              "mode": "none"

            },

            "thresholdsStyle": {

              "mode": "off"

            }

          },

          "mappings": [],

          "thresholds": {

            "mode": "absolute",

            "steps": [

              {

                "color": "green",

                "value": null

              },

              {

                "color": "red",

                "value": 80

              }

            ]

          },

          "unit": "short"

        },

        "overrides": []

      },

      "gridPos": {

        "h": 8,

        "w": 9,

        "x": 0,

        "y": 0

      },

      "id": 2,

      "links": [],

      "options": {

        "legend": {

          "calcs": [

            "mean",

            "lastNotNull"

          ],

          "displayMode": "table",

          "placement": "right"

        },

        "tooltip": {

          "mode": "single"

        }

      },

      "pluginVersion": "8.2.7",

      "targets": [

        {

          "$$hashKey": "object:214",

          "exemplar": true,

          "expr": "rate(mlflow_http_request_duration_seconds_count{status=\"200\"}[2m])",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{ method }}",

          "refId": "A"

        }

      ],

      "timeFrom": null,

      "timeShift": null,

      "title": "Requests per second",

      "type": "timeseries"

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 8,

        "w": 6,

        "x": 9,

        "y": 0

      },

      "hiddenSeries": false,

      "id": 4,

      "legend": {

        "avg": true,

        "current": true,

        "max": true,

        "min": false,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 5,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [

        {

          "$$hashKey": "object:1922",

          "alias": "errors",

          "color": "#c15c17"

        }

      ],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "$$hashKey": "object:766",

          "exemplar": true,

          "expr": "sum(rate(mlflow_http_request_duration_seconds_count{status!=\"200\"}[2m]))",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "errors",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Errors per second",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "$$hashKey": "object:890",

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "$$hashKey": "object:891",

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": true,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 8,

        "w": 9,

        "x": 15,

        "y": 0

      },

      "hiddenSeries": false,

      "id": 13,

      "legend": {

        "avg": true,

        "current": false,

        "max": true,

        "min": false,

        "rightSide": true,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": false,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 5,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [

        {

          "$$hashKey": "object:255",

          "alias": "HTTP 500",

          "color": "#bf1b00"

        }

      ],

      "spaceLength": 10,

      "stack": true,

      "steppedLine": false,

      "targets": [

        {

          "$$hashKey": "object:140",

          "exemplar": true,

          "expr": "increase(mlflow_http_request_total[2m])",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "HTTP {{ status }} - {{ method }}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Total requests each 2 minutes",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "$$hashKey": "object:211",

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": "0",

          "show": true

        },

        {

          "$$hashKey": "object:212",

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "decimals": null,

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 6,

        "w": 13,

        "x": 0,

        "y": 8

      },

      "hiddenSeries": false,

      "id": 6,

      "legend": {

        "alignAsTable": true,

        "avg": false,

        "current": true,

        "max": false,

        "min": false,

        "rightSide": true,

        "show": true,

        "sort": "avg",

        "sortDesc": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null as zero",

      "options": {

        "alertThreshold": true

      },

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 5,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "$$hashKey": "object:146",

          "exemplar": true,

          "expr": "rate(mlflow_http_request_duration_seconds_sum{status=\"200\"}[2m])\n/\nrate(mlflow_http_request_duration_seconds_count{status=\"200\"}[2m])",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{ method }}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Average response time [2m]",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "$$hashKey": "object:1004",

          "decimals": null,

          "format": "s",

          "label": "",

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "$$hashKey": "object:1005",

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "description": "",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 6,

        "w": 11,

        "x": 13,

        "y": 8

      },

      "hiddenSeries": false,

      "id": 15,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "rightSide": true,

        "show": true,

        "sort": "avg",

        "sortDesc": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null as zero",

      "options": {

        "alertThreshold": true

      },

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 5,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "$$hashKey": "object:426",

          "exemplar": true,

          "expr": "histogram_quantile(0.5, rate(mlflow_http_request_duration_seconds_bucket{status=\"200\"}[2m]))",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{ method }}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Request duration [s] - p50",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "$$hashKey": "object:1280",

          "format": "none",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "$$hashKey": "object:1281",

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 6,

        "w": 13,

        "x": 0,

        "y": 14

      },

      "hiddenSeries": false,

      "id": 11,

      "legend": {

        "alignAsTable": true,

        "avg": false,

        "current": true,

        "max": false,

        "min": false,

        "rightSide": true,

        "show": true,

        "sort": "current",

        "sortDesc": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null as zero",

      "options": {

        "alertThreshold": true

      },

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 5,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "$$hashKey": "object:1079",

          "exemplar": true,

          "expr": "increase(mlflow_http_request_duration_seconds_bucket{status=\"200\",le=\"0.25\"}[2m]) \n/ ignoring (le) increase(mlflow_http_request_duration_seconds_count{status=\"200\"}[2m])",

          "format": "time_series",

          "instant": false,

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{ method }}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Requests under 250ms",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "$$hashKey": "object:1137",

          "decimals": null,

          "format": "percentunit",

          "label": null,

          "logBase": 1,

          "max": "1",

          "min": "0",

          "show": true

        },

        {

          "$$hashKey": "object:1138",

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 6,

        "w": 11,

        "x": 13,

        "y": 14

      },

      "hiddenSeries": false,

      "id": 16,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "rightSide": true,

        "show": true,

        "sort": "avg",

        "sortDesc": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null as zero",

      "options": {

        "alertThreshold": true

      },

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 5,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "$$hashKey": "object:426",

          "exemplar": true,

          "expr": "histogram_quantile(0.9, rate(mlflow_http_request_duration_seconds_bucket{status=\"200\"}[2m]))",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{ method }}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Request duration [s] - p90",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    }

  ],

  "refresh": "1m",

  "schemaVersion": 32,

  "style": "dark",

  "tags": [

    "mlflow"

  ],

  "templating": {

    "list": []

  },

  "time": {

    "from": "now-1h",

    "to": "now"

  },

  "timepicker": {

    "refresh_intervals": [

      "5s",

      "10s",

      "30s",

      "1m",

      "5m",

      "15m",

      "30m",

      "1h",

      "2h",

      "1d"

    ],

    "time_options": [

      "5m",

      "15m",

      "1h",

      "6h",

      "12h",

      "24h",

      "2d",

      "7d",

      "30d"

    ]

  },

  "timezone": "browser",

  "title": "Mlflow Dashboard",

  "uid": "_eX4mpl4",

  "version": 1

}
```

### Health Checks and Alerts[​](#health-checks-and-alerts "Direct link to Health Checks and Alerts")

Configure health checks and alerting:

```
livenessProbe:

  initialDelaySeconds: 30

  periodSeconds: 20

  timeoutSeconds: 6

  failureThreshold: 3

  httpGet:

    path: /health

    port: 5000



readinessProbe:

  initialDelaySeconds: 30

  periodSeconds: 20

  timeoutSeconds: 6

  failureThreshold: 3

  httpGet:

    path: /health

    port: 5000
```

### Prometheus Alert Rules[​](#prometheus-alert-rules "Direct link to Prometheus Alert Rules")

Create alert rules for MLflow:

```
apiVersion: monitoring.coreos.com/v1

kind: PrometheusRule

metadata:

  name: mlflow-alerts

  namespace: monitoring

spec:

  groups:

  - name: mlflow

    rules:

    - alert: MLflowDown

      expr: up{job="mlflow"} == 0

      for: 1m

      labels:

        severity: critical

      annotations:

        summary: "MLflow is down"

        description: "MLflow instance has been down for more than 1 minute"



    - alert: MLflowHighErrorRate

      expr: rate(http_requests_total{job="mlflow",status=~"5.."}[5m]) > 0.1

      for: 5m

      labels:

        severity: warning

      annotations:

        summary: "High error rate in MLflow"

        description: "MLflow is returning 5xx errors at a high rate"



    - alert: MLflowHighResponseTime

      expr: histogram_quantile(0.95, rate(http_request_duration_seconds_bucket{job="mlflow"}[5m])) > 2

      for: 5m

      labels:

        severity: warning

      annotations:

        summary: "High response time in MLflow"

        description: "MLflow 95th percentile response time is above 2 seconds"
```

## Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

### Resource Management[​](#resource-management "Direct link to Resource Management")

Configure appropriate resource limits:

```
resources:

  requests:

    cpu: 500m

    memory: 1Gi

  limits:

    cpu: 2

    memory: 4Gi
```

### Database Connection Pooling[​](#database-connection-pooling "Direct link to Database Connection Pooling")

Optimize database connections:

```
extraEnvVars:

  MLFLOW_SQLALCHEMY_POOL_SIZE: "20"

  MLFLOW_SQLALCHEMY_MAX_OVERFLOW: "30"

  MLFLOW_SQLALCHEMY_POOL_TIMEOUT: "30"

  MLFLOW_SQLALCHEMY_POOL_RECYCLE: "3600"
```

### Artifact Storage Optimization[​](#artifact-storage-optimization "Direct link to Artifact Storage Optimization")

Optimize artifact storage performance:

```
# For S3

extraEnvVars:

  MLFLOW_S3_PRESIGNED_URLS: "true"

  MLFLOW_S3_UPLOAD_EXTRA_ARGS: '{"ServerSideEncryption": "aws:kms"}'



# For GCS

extraEnvVars:

  MLFLOW_GCS_DEFAULT_TIMEOUT: "120"

  MLFLOW_GCS_UPLOAD_CHUNK_SIZE: "209715200"
```

## Logging and Debugging[​](#logging-and-debugging "Direct link to Logging and Debugging")

tip

**Log Level:** Use the `log.level` value in your Helm values to control MLflow's logging verbosity. Set to `debug` for troubleshooting, or `info` for normal operation.

### Log Level Configuration[​](#log-level-configuration "Direct link to Log Level Configuration")

Configure appropriate log levels:

```
log:

  enabled: true

  level: debug  # debug, info, warning, error, critical
```

### Centralized Logging[​](#centralized-logging "Direct link to Centralized Logging")

Set up centralized logging with Fluentd or similar:

```
extraEnvVars:

  MLFLOW_LOG_FORMAT: "json"

  MLFLOW_LOG_FILE: "/var/log/mlflow/mlflow.log"
```

### Debug Mode[​](#debug-mode "Direct link to Debug Mode")

Enable debug mode for troubleshooting:

```
extraEnvVars:

  MLFLOW_LOG_LEVEL: "DEBUG"

  MLFLOW_TRACKING_URI: "http://localhost:5000"

  MLFLOW_SERVE_ARTIFACTS: "true"
```

## Backup and Recovery[​](#backup-and-recovery "Direct link to Backup and Recovery")

### Database Backup[​](#database-backup "Direct link to Database Backup")

Set up automated database backups:

```
# PostgreSQL backup script

#!/bin/bash

pg_dump -h $POSTGRES_HOST -U $POSTGRES_USER -d mlflow > /backup/mlflow_$(date +%Y%m%d_%H%M%S).sql



# MySQL backup script

#!/bin/bash

mysqldump -h $MYSQL_HOST -u $MYSQL_USER -p$MYSQL_PASSWORD mlflow > /backup/mlflow_$(date +%Y%m%d_%H%M%S).sql
```

### Artifact Storage Backup[​](#artifact-storage-backup "Direct link to Artifact Storage Backup")

Configure artifact storage backup:

```
# S3 backup configuration

extraEnvVars:

  MLFLOW_S3_BACKUP_BUCKET: "mlflow-backup-bucket"

  MLFLOW_S3_BACKUP_SCHEDULE: "0 2 * * *"  # Daily at 2 AM
```

## Security Monitoring[​](#security-monitoring "Direct link to Security Monitoring")

### Access Monitoring[​](#access-monitoring "Direct link to Access Monitoring")

Monitor access patterns and security events:

```
extraEnvVars:

  MLFLOW_AUDIT_ENABLED: "true"

  MLFLOW_AUDIT_LOG_PATH: "/var/log/mlflow/audit.log"

  MLFLOW_SESSION_TIMEOUT: "3600"

  MLFLOW_MAX_SESSIONS_PER_USER: "5"
```

### Network Security[​](#network-security "Direct link to Network Security")

Monitor network access and security:

```
# Network policy for MLflow

apiVersion: networking.k8s.io/v1

kind: NetworkPolicy

metadata:

  name: mlflow-network-policy

  namespace: mlflow

spec:

  podSelector:

    matchLabels:

      app: mlflow

  policyTypes:

  - Ingress

  - Egress

  ingress:

  - from:

    - namespaceSelector:

        matchLabels:

          name: ingress-nginx

    ports:

    - protocol: TCP

      port: 5000

  egress:

  - to:

    - namespaceSelector:

        matchLabels:

          name: database

    ports:

    - protocol: TCP

      port: 5432
```

## Maintenance Tasks[​](#maintenance-tasks "Direct link to Maintenance Tasks")

### Regular Maintenance[​](#regular-maintenance "Direct link to Regular Maintenance")

Set up regular maintenance tasks:

```
# Clean up old experiments (older than 90 days)

mlflow gc --older-than 90d



# Clean up old artifacts

mlflow artifacts cleanup --older-than 90d



# Database maintenance

mlflow db gc --older-than 90d
```

### Health Check Script[​](#health-check-script "Direct link to Health Check Script")

Create a comprehensive health check script:

```
#!/bin/bash

# MLflow Health Check Script



# Check pod status

kubectl get pods -n mlflow



# Check service status

kubectl get svc -n mlflow



# Check database connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import mlflow; print('Database OK')"



# Check artifact storage

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import mlflow; print('Artifact storage OK')"



# Check metrics endpoint

kubectl exec -it deployment/mlflow -n mlflow -- \

  curl -s http://localhost:5000/metrics | head -5
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Set up monitoring with [ServiceMonitor](/docs/charts/mlflow/usage.md#monitoring)
* Configure [autoscaling](/docs/charts/mlflow/autoscaling-setup.md) for high availability
* Implement backup and disaster recovery strategies
* Set up [security monitoring](/docs/charts/mlflow/authentication-configuration.md) and alerting


---

# MLflow Chart Usage

[MLflow](https://mlflow.org) is an open-source platform for managing the end-to-end machine learning lifecycle, including experiment tracking, model management, and deployment. This Helm chart helps you deploy MLflow on Kubernetes with enterprise-grade features.

info

**Quick Links:**

* **Official Website:** <https://mlflow.org>
* **GitHub Repository:** <https://github.com/mlflow/mlflow>
* **Documentation:** <https://mlflow.org/docs/latest/index.html>
* **ArtifactHub:** [MLflow Helm Chart](https://artifacthub.io/packages/helm/community-charts/mlflow)

## Why use this chart?[​](#why-use-this-chart "Direct link to Why use this chart?")

tip

**Enterprise Ready:** This chart provides production-grade features that make MLflow suitable for enterprise environments and team collaboration.

* **Production Ready**: Deploy MLflow with PostgreSQL, MySQL, or SQLite backends
* **Cloud Storage Integration**: Support for AWS S3, Google Cloud Storage, and Azure Blob Storage
* **Enterprise Features**: Built-in authentication, LDAP integration, and autoscaling
* **Database Migrations**: Automatic database schema migrations with init containers
* **Monitoring Ready**: Prometheus ServiceMonitor integration
* **Community Maintained**: Regularly updated and tested

## Supported Databases[​](#supported-databases "Direct link to Supported Databases")

tip

**Database Selection:** Choose your database based on your deployment requirements. PostgreSQL is recommended for production environments.

The chart supports multiple database backends for MLflow:

* **PostgreSQL**: Production-ready with connection pooling and migrations
* **MySQL**: Alternative database with PyMySQL driver support
* **SQLite**: Development and testing (in-memory or file-based)

warning

**Production Database:** SQLite is not suitable for production deployments. Use PostgreSQL or MySQL for production environments.

danger

**Data Loss Risk:** SQLite stores data in files that can be lost if the pod is deleted. Always use persistent volumes for SQLite in any environment.

## Supported Cloud Providers[​](#supported-cloud-providers "Direct link to Supported Cloud Providers")

info

**Enterprise Storage:** Cloud storage integration is essential for production MLflow deployments to handle large model artifacts and datasets.

Enterprise artifact storage integration:

* **AWS S3**: IAM roles, access keys, and MinIO compatibility
* **Google Cloud Storage**: GCS bucket integration with service accounts
* **Azure Blob Storage**: Azure Storage Account with managed identities

tip

**Storage Strategy:** Use cloud storage for artifacts to enable team collaboration and ensure data persistence across deployments.

## Quick Start[​](#quick-start "Direct link to Quick Start")

note

**Getting Started:** Follow these steps to get MLflow running quickly. For production deployments, see the detailed configuration examples below.

### 1. Add the Helm Repository[​](#1-add-the-helm-repository "Direct link to 1. Add the Helm Repository")

```
helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update
```

### 2. Basic Installation with SQLite[​](#2-basic-installation-with-sqlite "Direct link to 2. Basic Installation with SQLite")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --create-namespace
```

tip

**Development Use:** SQLite installation is perfect for development, testing, and single-user scenarios.

### 3. Production Installation with PostgreSQL and S3[​](#3-production-installation-with-postgresql-and-s3 "Direct link to 3. Production Installation with PostgreSQL and S3")

```
helm install mlflow community-charts/mlflow \

  --namespace mlflow \

  --create-namespace \

  --set backendStore.databaseMigration=true \

  --set backendStore.postgres.enabled=true \

  --set backendStore.postgres.host=your-postgres-host \

  --set backendStore.postgres.database=mlflow \

  --set backendStore.postgres.user=mlflow \

  --set backendStore.postgres.password=your-password \

  --set artifactRoot.s3.enabled=true \

  --set artifactRoot.s3.bucket=your-mlflow-bucket \

  --set artifactRoot.s3.awsAccessKeyId=your-access-key \

  --set artifactRoot.s3.awsSecretAccessKey=your-secret-key
```

warning

**Security:** Never hardcode credentials in command line arguments. Use Kubernetes secrets or environment variables for sensitive data.

danger

**Production Security:** Always use strong passwords, enable authentication, and configure TLS for production deployments.

## Key Features[​](#key-features "Direct link to Key Features")

info

**Enterprise Features:** These features make MLflow production-ready and suitable for enterprise environments.

### Logging Level Control[​](#logging-level-control "Direct link to Logging Level Control")

Configure the verbosity of MLflow logs using the `log.level` value:

```
log:

  enabled: true

  level: info  # Set to debug, info, warning, error, or critical
```

tip

**Debugging:** Set `log.level: debug` to get more detailed logs for troubleshooting. Use `info` or higher for production.

### Database Migrations[​](#database-migrations "Direct link to Database Migrations")

Enable automatic database schema migrations:

```
backendStore:

  databaseMigration: true
```

tip

**Migration Safety:** Database migrations are disabled by default. Enable them only when you're ready to update your database schema.

warning

**Migration Backup:** Always backup your database before enabling migrations in production environments.

### Connection Health Checks[​](#connection-health-checks "Direct link to Connection Health Checks")

Add database availability checks:

```
backendStore:

  databaseConnectionCheck: true
```

tip

**Health Monitoring:** Enable connection checks to ensure your MLflow instance can detect database connectivity issues early.

### Authentication[​](#authentication "Direct link to Authentication")

Basic authentication with admin credentials:

```
auth:

  enabled: true

  adminUsername: admin

  adminPassword: your-secure-password
```

warning

**Authentication:** Always enable authentication in production environments to secure your MLflow instance.

danger

**Default Credentials:** Change default admin credentials immediately after installation. Never use default passwords in production.

### LDAP Integration[​](#ldap-integration "Direct link to LDAP Integration")

Enterprise LDAP authentication:

```
ldapAuth:

  enabled: true

  uri: ldap://your-ldap-server:389

  lookupBind: uid=%s,ou=people,dc=example,dc=com

  searchBaseDistinguishedName: ou=groups,dc=example,dc=com

  adminGroupDistinguishedName: cn=admins,ou=groups,dc=example,dc=com
```

info

**Enterprise Integration:** LDAP authentication enables centralized user management and integration with existing enterprise identity systems.

### Autoscaling[​](#autoscaling "Direct link to Autoscaling")

Horizontal Pod Autoscaler for production workloads:

```
autoscaling:

  enabled: true

  minReplicas: 2

  maxReplicas: 10

  metrics:

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70
```

tip

**Scaling Strategy:** Use autoscaling for dynamic workloads and manual scaling for predictable, steady-state workloads.

warning

**Resource Limits:** Set appropriate resource limits when using autoscaling to prevent resource exhaustion.

### Monitoring[​](#monitoring "Direct link to Monitoring")

Prometheus ServiceMonitor integration:

```
serviceMonitor:

  enabled: true

  interval: 30s

  labels:

    release: prometheus
```

tip

**Observability:** Enable monitoring to track MLflow performance, usage patterns, and identify potential issues.

## Configuration Examples[​](#configuration-examples "Direct link to Configuration Examples")

info

**Production Examples:** These examples demonstrate common production deployment patterns for different cloud providers and databases.

### PostgreSQL with S3 Artifacts[​](#postgresql-with-s3-artifacts "Direct link to PostgreSQL with S3 Artifacts")

```
backendStore:

  databaseMigration: true

  postgres:

    enabled: true

    host: postgresql-instance.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  s3:

    enabled: true

    bucket: my-mlflow-artifact-root-backend

    awsAccessKeyId: a1b2c3d4

    awsSecretAccessKey: a1b2c3d4
```

### MySQL with Azure Blob Storage[​](#mysql-with-azure-blob-storage "Direct link to MySQL with Azure Blob Storage")

```
backendStore:

  databaseMigration: true

  mysql:

    enabled: true

    host: mysql-instance.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 3306

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  azureBlob:

    enabled: true

    container: mlflow

    storageAccount: mystorageaccount

    accessKey: your-access-key
```

tip

**Production Setup:** This configuration provides a robust production environment with external database and cloud storage.

### EKS with IAM Roles[​](#eks-with-iam-roles "Direct link to EKS with IAM Roles")

info

**IAM Best Practice:** Using IAM roles is the recommended approach for AWS EKS deployments as it eliminates the need to manage access keys.

```
serviceAccount:

  create: true

  annotations:

    eks.amazonaws.com/role-arn: arn:aws:iam::account-id:role/iam-role-name



backendStore:

  databaseMigration: true

  postgres:

    enabled: true

    host: postgresql-instance.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  s3:

    enabled: true

    bucket: my-mlflow-artifact-root-backend

    # No access keys needed with IAM roles
```

### MinIO Integration (S3-Compatible Storage)[​](#minio-integration-s3-compatible-storage "Direct link to MinIO Integration (S3-Compatible Storage)")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgres-service

    port: 5432

    database: postgres

    user: postgres

    password: postgres



artifactRoot:

  s3:

    enabled: true

    bucket: mlflow

    awsAccessKeyId: minioadmin

    awsSecretAccessKey: minioadmin



extraEnvVars:

  MLFLOW_S3_ENDPOINT_URL: http://minio-service:9000

  MLFLOW_S3_IGNORE_TLS: "true"



ingress:

  enabled: true

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: ImplementationSpecific
```

tip

**Self-Hosted Storage:** MinIO provides S3-compatible storage for environments where you need to keep data on-premises.

### Production Monitoring Setup[​](#production-monitoring-setup "Direct link to Production Monitoring Setup")

```
backendStore:

  databaseMigration: true

  databaseConnectionCheck: true

  postgres:

    enabled: true

    host: postgresql-instance.cg034hpkmmjt.eu-central-1.rds.amazonaws.com

    port: 5432

    database: mlflow

    user: mlflowuser

    password: Pa33w0rd!



artifactRoot:

  s3:

    enabled: true

    bucket: my-mlflow-artifact-root-backend

    awsAccessKeyId: a1b2c3d4

    awsSecretAccessKey: a1b2c3d4



serviceMonitor:

  enabled: true

  namespace: monitoring

  interval: 30s

  telemetryPath: /metrics

  labels:

    release: prometheus

  timeout: 10s

  targetLabels: []



livenessProbe:

  initialDelaySeconds: 30

  periodSeconds: 20

  timeoutSeconds: 6

  failureThreshold: 3



readinessProbe:

  initialDelaySeconds: 30

  periodSeconds: 20

  timeoutSeconds: 6

  failureThreshold: 3
```

info

**Production Monitoring:** This configuration includes comprehensive monitoring and health checks for production environments.

### Proxied Artifact Storage Access[​](#proxied-artifact-storage-access "Direct link to Proxied Artifact Storage Access")

```
backendStore:

  postgres:

    enabled: true

    host: postgres-service

    port: 5432

    database: postgres

    user: postgres

    password: postgres



artifactRoot:

  proxiedArtifactStorage: true

  s3:

    enabled: true

    bucket: mlflow

    awsAccessKeyId: minioadmin

    awsSecretAccessKey: minioadmin



extraEnvVars:

  MLFLOW_S3_ENDPOINT_URL: http://minio-service:9000



extraFlags:

  - serveArtifacts
```

tip

**Proxied Storage:** Enable proxied artifact storage when you want MLflow to serve artifacts directly instead of redirecting to storage URLs.

### Static Prefix Configuration[​](#static-prefix-configuration "Direct link to Static Prefix Configuration")

```
extraArgs:

  staticPrefix: /mlflow



ingress:

  enabled: true

  hosts:

    - host: your-domain.com

      paths:

        - path: /mlflow

          pathType: ImplementationSpecific
```

info

**URL Customization:** Use static prefix to customize the base URL path for your MLflow instance.

### PVC Usage with SQLite[​](#pvc-usage-with-sqlite "Direct link to PVC Usage with SQLite")

```
strategy:

  type: Recreate



extraVolumes:

  - name: mlflow-volume

    persistentVolumeClaim:

      claimName: mlflow-pvc



extraVolumeMounts:

  - name: mlflow-volume

    mountPath: /mlflow/data



backendStore:

  defaultSqlitePath: /mlflow/data/mlflow.db



artifactRoot:

  proxiedArtifactStorage: true

  defaultArtifactsDestination: /mlflow/data/mlartifacts



ingress:

  enabled: true

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: ImplementationSpecific
```

warning

**SQLite Limitations:** While this setup works, consider PostgreSQL for production environments with multiple users or high data volumes.

## Advanced Configuration[​](#advanced-configuration "Direct link to Advanced Configuration")

info

**Advanced Features:** These configurations provide fine-grained control over MLflow behavior and performance.

### Logging Level[​](#logging-level "Direct link to Logging Level")

You can control the MLflow logging level via the `log.level` value:

```
log:

  enabled: true

  level: info  # debug, info, warning, error, critical
```

This sets the logging verbosity for the MLflow server. Use `debug` for troubleshooting and `info` or higher for normal operation.

### Custom Environment Variables[​](#custom-environment-variables "Direct link to Custom Environment Variables")

```
extraEnvVars:

  # S3 Configuration

  MLFLOW_S3_IGNORE_TLS: "true"  # Skip TLS certificate verification for S3

  MLFLOW_S3_UPLOAD_EXTRA_ARGS: '{"ServerSideEncryption": "aws:kms", "SSEKMSKeyId": "1234"}'  # Extra S3 upload arguments

  MLFLOW_S3_ENDPOINT_URL: "http://minio-service:9000"  # Custom S3 endpoint URL



  # AWS Configuration

  AWS_DEFAULT_REGION: "us-east-1"  # AWS default region

  AWS_CA_BUNDLE: "/some/ca/bundle.pem"  # Custom CA bundle for AWS



  # Google Cloud Storage Configuration

  MLFLOW_GCS_DEFAULT_TIMEOUT: "60"  # GCS transfer timeout in seconds

  MLFLOW_GCS_UPLOAD_CHUNK_SIZE: "104857600"  # GCS upload chunk size (100MB)

  MLFLOW_GCS_DOWNLOAD_CHUNK_SIZE: "104857600"  # GCS download chunk size (100MB)



  # Database Connection Pooling

  MLFLOW_SQLALCHEMYSTORE_POOL_SIZE: "10"  # SQLAlchemy connection pool size

  MLFLOW_SQLALCHEMYSTORE_MAX_OVERFLOW: "20"  # SQLAlchemy max overflow connections

  MLFLOW_SQLALCHEMYSTORE_POOL_RECYCLE: "3600"  # SQLAlchemy pool recycle time



  # Logging and Monitoring

  MLFLOW_LOGGING_LEVEL: "INFO"  # MLflow logging level

  MLFLOW_ENABLE_SYSTEM_METRICS_LOGGING: "true"  # Enable system metrics logging

  MLFLOW_SYSTEM_METRICS_SAMPLING_INTERVAL: "1.0"  # System metrics sampling interval
```

tip

**Environment Variables:** Use environment variables to customize MLflow behavior without modifying the container image.

### Resource Management[​](#resource-management "Direct link to Resource Management")

```
resources:

  requests:

    cpu: 500m

    memory: 1Gi

  limits:

    cpu: 2

    memory: 4Gi
```

warning

**Resource Planning:** Set appropriate resource limits to prevent resource exhaustion and ensure stable performance.

### Ingress Configuration[​](#ingress-configuration "Direct link to Ingress Configuration")

```
ingress:

  enabled: true

  className: nginx

  hosts:

    - host: mlflow.your-domain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: mlflow-tls

      hosts:

        - mlflow.your-domain.com
```

danger

**TLS Security:** Always use TLS certificates in production to encrypt traffic between clients and MLflow.

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

info

**Common Issues:** This section covers the most frequently encountered problems and their solutions.

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Database Connection**: Ensure database credentials and network connectivity
2. **S3 Access**: Verify IAM permissions or access keys
3. **Authentication**: Check admin credentials and LDAP configuration
4. **Migrations**: Enable `databaseMigration: true` for schema updates

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check pod status

kubectl get pods -n mlflow



# View logs

kubectl logs -f deployment/mlflow -n mlflow



# Check database connectivity

kubectl exec -it deployment/mlflow -n mlflow -- \

  python -c "import mlflow; print(mlflow.get_tracking_uri())"



# Test S3 access

kubectl exec -it deployment/mlflow -n mlflow -- \

  aws s3 ls s3://your-bucket
```

tip

**Debugging:** Use these commands to diagnose common issues with MLflow deployments.

## Next Steps[​](#next-steps "Direct link to Next Steps")

tip

**Getting Started:** Follow these guides in order for a complete MLflow setup experience.

* [Basic Installation with SQLite](/docs/charts/mlflow/basic-installation.md) - Get started quickly
* [PostgreSQL Backend Installation](/docs/charts/mlflow/postgresql-backend-installation.md) - Production database setup
* [MySQL Backend Installation](/docs/charts/mlflow/mysql-backend-installation.md) - Alternative database setup
* [AWS S3 Integration](/docs/charts/mlflow/aws-s3-integration.md) - Cloud artifact storage
* [Azure Blob Storage Integration](/docs/charts/mlflow/azure-blob-storage-integration.md) - Azure storage setup
* [Authentication Configuration](/docs/charts/mlflow/authentication-configuration.md) - Secure access
* [Autoscaling Setup](/docs/charts/mlflow/autoscaling-setup.md) - Handle high workloads


---

# Managed Redis Setup for n8n

n8n queue mode requires a Redis backend. This guide explains how to connect n8n to managed Redis services on Google Cloud (Memorystore), AWS (ElastiCache), and Azure (Cache for Redis).

## GCP Memorystore for Redis[​](#gcp-memorystore-for-redis "Direct link to GCP Memorystore for Redis")

info

Google Cloud Memorystore provides a fully managed Redis service. Use private IP for secure access from GKE.

### Example `values.yaml`[​](#example-valuesyaml "Direct link to example-valuesyaml")

```
externalRedis:

  host: "<memorystore-ip>"

  port: 6379

  # Memorystore does not use password by default
```

tip

Ensure your GKE nodes are in the same VPC and region as your Memorystore instance. Use private IP connectivity.

#### Networking & Security[​](#networking--security "Direct link to Networking & Security")

* Memorystore must be provisioned with private IP.
* GKE nodes must be in the same VPC/subnet or have VPC peering.
* No password by default; enable AUTH if needed.

#### Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

* **Timeouts:** Check VPC/subnet and firewall rules.
* **Auth errors:** If AUTH is enabled, set the password in `externalRedis.password`.

note

See [GCP Memorystore for Redis docs](https://cloud.google.com/memorystore/docs/redis) for more details.

### Next Steps[​](#next-steps "Direct link to Next Steps")

* [GCP Memorystore Docs](https://cloud.google.com/memorystore/docs/redis)
* [n8n Queue Mode Guide](/docs/charts/n8n/queue-mode.md)

***

## AWS ElastiCache for Redis[​](#aws-elasticache-for-redis "Direct link to AWS ElastiCache for Redis")

info

AWS ElastiCache for Redis is a fully managed Redis service. Use VPC/subnet groups for secure access from EKS.

### Example `values.yaml`[​](#example-valuesyaml-1 "Direct link to example-valuesyaml-1")

```
externalRedis:

  host: "<primary-endpoint>.cache.amazonaws.com"

  port: 6379

  # Set password if AUTH is enabled

  password: "<your-password>"
```

tip

Ensure your EKS nodes are in the same VPC/subnet as your ElastiCache cluster. Use security groups to control access.

#### Networking & Security[​](#networking--security-1 "Direct link to Networking & Security")

* ElastiCache must be in a VPC accessible to EKS nodes.
* Use security groups to allow inbound traffic from EKS nodes.
* Enable AUTH for password protection (optional).
* TLS/SSL is supported (see AWS docs).

#### Troubleshooting[​](#troubleshooting-1 "Direct link to Troubleshooting")

* **Timeouts:** Check VPC/subnet and security group rules.
* **Auth errors:** Set the correct password if AUTH is enabled.
* **TLS errors:** Ensure n8n supports Redis TLS if enabled.

note

See [AWS ElastiCache for Redis docs](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) for more details.

### Next Steps[​](#next-steps-1 "Direct link to Next Steps")

* [AWS ElastiCache Docs](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html)
* [n8n Queue Mode Guide](/docs/charts/n8n/queue-mode.md)

***

## Azure Cache for Redis[​](#azure-cache-for-redis "Direct link to Azure Cache for Redis")

info

Azure Cache for Redis is a fully managed Redis service. Use VNet integration for secure access from AKS.

### Example `values.yaml`[​](#example-valuesyaml-2 "Direct link to example-valuesyaml-2")

```
externalRedis:

  host: "<redis-name>.redis.cache.windows.net"

  port: 6380

  password: "<access-key>"

  # Azure requires SSL (port 6380)
```

tip

Use the access key from the Azure portal as the Redis password. Use SSL (port 6380) for connections.

#### Networking & Security[​](#networking--security-2 "Direct link to Networking & Security")

* Use VNet integration for private access from AKS.
* Add AKS subnet to the Redis firewall rules.
* Use SSL (port 6380) for all connections.

#### Troubleshooting[​](#troubleshooting-2 "Direct link to Troubleshooting")

* **Timeouts:** Check VNet/firewall rules.
* **Auth errors:** Use the correct access key as password.
* **SSL errors:** Ensure n8n is configured for SSL (port 6380).

note

See [Azure Cache for Redis docs](https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/) for more details.

### Next Steps[​](#next-steps-2 "Direct link to Next Steps")

* [Azure Cache for Redis Docs](https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/)
* [n8n Queue Mode Guide](/docs/charts/n8n/queue-mode.md)

***

## Pod Affinity and Anti-Affinity[​](#pod-affinity-and-anti-affinity "Direct link to Pod Affinity and Anti-Affinity")

tip

**Redis Affinity:** Proper affinity configuration can optimize Redis performance by ensuring pods are placed optimally relative to Redis resources.

warning

**Deprecation Notice:** The top-level `affinity` field is deprecated. Use the specific affinity configurations under `main`, `worker`, and `webhook` blocks instead.

### Affinity for Redis Optimization[​](#affinity-for-redis-optimization "Direct link to Affinity for Redis Optimization")

#### Co-locate with Redis Nodes[​](#co-locate-with-redis-nodes "Direct link to Co-locate with Redis Nodes")

```
# Place pods on nodes close to Redis

main:

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: redis-zone

            operator: In

            values:

            - "primary"



worker:

  mode: queue

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: redis-zone

            operator: In

            values:

            - "primary"
```

#### Spread Pods for Redis Load Distribution[​](#spread-pods-for-redis-load-distribution "Direct link to Spread Pods for Redis Load Distribution")

```
# Distribute Redis connections across nodes

main:

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: kubernetes.io/hostname



worker:

  mode: queue

  affinity:

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - n8n

          - key: app.kubernetes.io/component

            operator: In

            values:

            - worker

        topologyKey: kubernetes.io/hostname
```

#### Zone Distribution for Redis Resilience[​](#zone-distribution-for-redis-resilience "Direct link to Zone Distribution for Redis Resilience")

```
# Distribute pods across zones for Redis availability

main:

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: topology.kubernetes.io/zone



webhook:

  mode: queue

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

            - key: app.kubernetes.io/component

              operator: In

              values:

              - webhook

          topologyKey: topology.kubernetes.io/zone
```

#### Node Affinity for Redis Performance[​](#node-affinity-for-redis-performance "Direct link to Node Affinity for Redis Performance")

```
# Use nodes optimized for Redis workloads

main:

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: node-type

            operator: In

            values:

            - redis-optimized



worker:

  mode: queue

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: node-type

            operator: In

            values:

            - redis-optimized
```

info

**Redis Benefits:** Proper affinity configuration ensures optimal Redis performance by placing pods on nodes with good Redis connectivity and distributing Redis load effectively.

***

## Next Steps[​](#next-steps-3 "Direct link to Next Steps")

* [Database Setup](/docs/charts/n8n/database-setup.md)
* [n8n Queue Mode Guide](/docs/charts/n8n/queue-mode.md)
* [Troubleshooting](/docs/charts/n8n/troubleshooting.md)


---

# n8n Configuration Reference

This comprehensive guide provides detailed coverage of all configuration options available in the n8n Helm chart, systematically organized by functional category with practical examples and enterprise-grade best practices.

info

**Configuration Reference:** This guide serves as the definitive reference for all available configuration options. Utilize the table of contents for efficient navigation to specific sections.

tip

**Enterprise Best Practices:** Follow the recommendations outlined in this guide to ensure a secure, performant, and reliable n8n deployment suitable for production environments.

## Table of Contents[​](#table-of-contents "Direct link to Table of Contents")

* [Image Configuration](#image-configuration)
* [Service Configuration](#service-configuration)
* [Ingress Configuration](#ingress-configuration)
* [Resources and Scaling](#resources-and-scaling)
* [Pod Affinity and Anti-Affinity](#pod-affinity-and-anti-affinity)
* [Persistence Configuration](#persistence-configuration)
* [Database Configuration](#database-configuration)
* [Queue Mode Configuration](#queue-mode-configuration)
* [Storage Configuration](#storage-configuration)
* [Node Configuration](#node-configuration)
* [Monitoring Configuration](#monitoring-configuration)
* [Security Configuration](#security-configuration)
* [Task Runners](#task-runners)
* [Workflow History](#workflow-history)
* [API Configuration](#api-configuration)
* [Diagnostics and Telemetry](#diagnostics-and-telemetry)
* [DNS Configuration](#dns-configuration)

## Image Configuration[​](#image-configuration "Direct link to Image Configuration")

tip

**Image Selection Strategy:** Choose the appropriate image tag for your environment. Implement specific versions for production stability and security.

### Standard Image Configuration[​](#standard-image-configuration "Direct link to Standard Image Configuration")

```
image:

  repository: n8nio/n8n

  tag: "1.0.0"  # Specify version or leave empty for appVersion

  pullPolicy: IfNotPresent
```

warning

**Production Image Security:** Always utilize specific image tags in production environments to prevent unexpected updates and mitigate potential security vulnerabilities.

### Private Registry Integration[​](#private-registry-integration "Direct link to Private Registry Integration")

```
image:

  repository: your-registry.com/n8nio/n8n

  tag: "1.0.0"

  pullPolicy: Always



imagePullSecrets:

  - name: registry-secret
```

info

**Private Registry Benefits:** Implement private registries for enhanced security posture and centralized control over image distribution.

## Service Configuration[​](#service-configuration "Direct link to Service Configuration")

note

**Service Architecture:** Select the service type based on your networking requirements and infrastructure architecture.

### Service Disabling[​](#service-disabling "Direct link to Service Disabling")

```
service:

  enabled: false
```

info

**Service Disabling:** Disable service creation when using external load balancers, ingress-only access, or when services are managed externally.

warning

**Access Considerations:** When services are disabled, ensure alternative access methods (ingress, external load balancers) are properly configured.

### Standard Service Configuration[​](#standard-service-configuration "Direct link to Standard Service Configuration")

```
service:

  enabled: true

  type: ClusterIP

  port: 5678

  name: http

  annotations: {}
```

tip

**Service Selection:** ClusterIP is optimal for internal access scenarios. Implement LoadBalancer or NodePort for external access without ingress configuration.

### LoadBalancer Service Configuration[​](#loadbalancer-service-configuration "Direct link to LoadBalancer Service Configuration")

```
service:

  enabled: true

  type: LoadBalancer

  port: 5678

  annotations:

    service.beta.kubernetes.io/aws-load-balancer-type: nlb

    service.beta.kubernetes.io/aws-load-balancer-internal: "true"
```

warning

**Cost Considerations:** LoadBalancer services may incur additional costs in cloud environments. Consider ingress implementation for cost optimization.

## Ingress Configuration[​](#ingress-configuration "Direct link to Ingress Configuration")

warning

**Security Implementation:** Always implement HTTPS in production environments. Configure TLS certificates and security headers appropriately for enhanced protection.

### Standard Ingress Configuration[​](#standard-ingress-configuration "Direct link to Standard Ingress Configuration")

This configuration sets up a basic Ingress for n8n using the NGINX Ingress controller, with TLS enabled for secure communication.

```
ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

    cert-manager.io/cluster-issuer: letsencrypt-prod

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: n8n-tls

      hosts:

        - n8n.yourdomain.com
```

danger

**TLS Security Requirement:** Never expose n8n without TLS in production environments. Implement cert-manager or similar solutions for automated certificate management.

### Multi-Host Ingress Configuration[​](#multi-host-ingress-configuration "Direct link to Multi-Host Ingress Configuration")

For enhanced security and access control, you can configure separate hosts for the n8n UI and API. This approach allows for granular management of traffic.

```
ingress:

  enabled: true

  className: nginx

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

    - host: n8n-api.yourdomain.com

      paths:

        - path: /api

          pathType: Prefix
```

tip

**Host Separation Strategy:** Implement separate API and UI hosts for enhanced security posture and granular access control.

### Webhook Subdomain Ingress Configuration[​](#webhook-subdomain-ingress-configuration "Direct link to Webhook Subdomain Ingress Configuration")

You can configure webhook endpoints with or without SSL, depending on your needs. Below are examples for both scenarios.

tip

Ensure the correct certificate secret is defined in the `ingress.tls` section when using SSL for webhook endpoints.

#### Without SSL[​](#without-ssl "Direct link to Without SSL")

```
ingress:

  enabled: true

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix



webhook:

  ...

  url: "http://webhook.yourdomain.com"

  ...
```

#### With SSL[​](#with-ssl "Direct link to With SSL")

```
ingress:

  enabled: true

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: n8n-tls

      hosts:

        - n8n.yourdomain.com

        - webhook.yourdomain.com



webhook:

  ...

  url: "https://webhook.yourdomain.com"

  ...
```

### Different Webhook Domain Ingress Configuration[​](#different-webhook-domain-ingress-configuration "Direct link to Different Webhook Domain Ingress Configuration")

For setups using different domains for n8n and webhooks, you can configure Ingress accordingly. Below are examples with and without SSL.

tip

When using SSL, verify that the certificate secret in `ingress.tls` matches the correct hostnames.

#### Without SSL[​](#without-ssl-1 "Direct link to Without SSL")

```
ingress:

  enabled: true

  hosts:

    - host: n8n.firstdomain.local

      paths:

        - path: /

          pathType: Prefix



webhook:

  ...

  url: "http://webhook.seconddomain.com"

  ...
```

#### With SSL[​](#with-ssl-1 "Direct link to With SSL")

```
ingress:

  enabled: true

  hosts:

    - host: n8n.firstdomain.local

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: n8n-tls

      hosts:

        - n8n.firstdomain.local

        - webhook.seconddomain.com



webhook:

  ...

  url: "https://webhook.seconddomain.com"

  ...
```

### Queue Mode Advanced Endpoints[​](#queue-mode-advanced-endpoints "Direct link to Queue Mode Advanced Endpoints")

info

**Advanced Endpoint Capabilities:** Queue mode with PostgreSQL database enables sophisticated endpoints for MCP and Form functionality.

#### MCP (Model Context Protocol) Endpoints[​](#mcp-model-context-protocol-endpoints "Direct link to MCP (Model Context Protocol) Endpoints")

When implementing queue mode with PostgreSQL, the following MCP endpoints are automatically configured:

* `/mcp/` — Main MCP endpoint for AI assistants, LLMs, and tool clients
* `/mcp-test/` — Test endpoint for MCP
* **MCP Webhook Service** — Dedicated deployment for MCP traffic (enabled when `webhook.count` bigger than 1 or `webhook.autoscaling.enabled=true` or `webhook.allNodes=true`)

##### Example values.yaml for MCP[​](#example-valuesyaml-for-mcp "Direct link to Example values.yaml for MCP")

```
webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  count: 2

  mcp:

    enabled: true

    # Customize resources, affinity, env, etc. under webhook.mcp
```

##### MCP Client Integration (Claude Desktop, Cursor, etc.)[​](#mcp-client-integration-claude-desktop-cursor-etc "Direct link to MCP Client Integration (Claude Desktop, Cursor, etc.)")

Set the following in your client (Claude Desktop, Cursor, etc.):

```
{

  "mcpServers": {

    "command": "npx",

    "args": [

      "-y",

      "supergateway",

      "--sse",

      "https://webhook.myhost/mcp/ab123c45-d678-9d0e-fg1a-2345bcd6ef7g"

    ]

  }

}
```

With header authentication:

```
{

  "mcpServers": {

    "command": "npx",

    "args": [

      "-y",

      "supergateway",

      "--sse",

      "https://webhook.myhost/mcp/ab123c45-d678-9d0e-fg1a-2345bcd6ef7g",

      "--header",

      "mykey:myvalue"

    ]

  }

}
```

tip

**MCP Scaling:**

* Customize resources, affinity, and environment variables under `webhook.mcp`.

#### Form Endpoints[​](#form-endpoints "Direct link to Form Endpoints")

Queue mode also provides dedicated form endpoints for interactive web form generation:

```
webhook:

  mode: queue

  url: "https://n8n.yourdomain.com"



ingress:

  enabled: true

  className: nginx

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

        # Form endpoints are automatically added when webhook.mode=queue

        # - path: /form/

        # - path: /form-test/

        # - path: /form-waiting/
```

**Available Form Endpoints:**

* `/form/` - Main form submission endpoint
* `/form-test/` - Testing endpoint for forms
* `/form-waiting/` - Endpoint for form waiting workflows

warning

**Queue Mode Required:** MCP and Form endpoints are only available when `webhook.mode=queue` and `db.type=postgresdb` are configured.

#### Endpoint Routing[​](#endpoint-routing "Direct link to Endpoint Routing")

In queue mode, different endpoints are routed to appropriate node types:

* **Main Node**: Handles UI, API, and test endpoints (`/mcp-test/`, `/form-test/`)
* **Webhook Nodes**: Process webhook, form, and MCP endpoints (`/webhook/`, `/form/`, `/mcp/`)
* **Worker Nodes**: Execute workflows triggered by any endpoint

info

**Load Distribution:** This routing ensures optimal performance by directing traffic to the appropriate node types based on the request type.

## Resources and Scaling[​](#resources-and-scaling "Direct link to Resources and Scaling")

tip

**Resource Planning:** Monitor your n8n usage and adjust resources accordingly. Start with conservative limits and scale up as needed.

### Main Node Resources[​](#main-node-resources "Direct link to Main Node Resources")

```
main:

  resources:

    requests:

      cpu: 100m

      memory: 128Mi

    limits:

      cpu: 1000m

      memory: 1Gi
```

warning

**Resource Limits:** Set appropriate limits to prevent resource exhaustion and ensure stable performance.

### Worker Node Resources[​](#worker-node-resources "Direct link to Worker Node Resources")

```
worker:

  mode: queue

  count: 3

  concurrency: 10

  resources:

    requests:

      cpu: 500m

      memory: 512Mi

    limits:

      cpu: 2000m

      memory: 2Gi
```

info

**Worker Scaling:** Worker nodes handle workflow execution. Allocate more resources to workers for better performance.

### Autoscaling[​](#autoscaling "Direct link to Autoscaling")

```
worker:

  mode: queue

  autoscaling:

    enabled: true

    minReplicas: 2

    maxReplicas: 10

    metrics:

      - type: Resource

        resource:

          name: memory

          target:

            type: Utilization

            averageUtilization: 80

      - type: Resource

        resource:

          name: cpu

          target:

            type: Utilization

            averageUtilization: 80
```

tip

**Autoscaling Strategy:** Use autoscaling for dynamic workloads. Monitor scaling behavior and adjust thresholds as needed.

## Pod Affinity and Anti-Affinity[​](#pod-affinity-and-anti-affinity "Direct link to Pod Affinity and Anti-Affinity")

tip

**Advanced Scheduling:** Pod affinity and anti-affinity rules allow you to control where n8n pods are scheduled based on node labels, pod labels, and other criteria.

warning

**Deprecation Notice:** The top-level `affinity` field is deprecated. Use the specific affinity configurations under `main`, `worker`, and `webhook` blocks instead.

### Main Node Affinity[​](#main-node-affinity "Direct link to Main Node Affinity")

Configure affinity rules for the main n8n node to control its placement:

```
main:

  affinity:

    nodeAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

        nodeSelectorTerms:

        - matchExpressions:

          - key: kubernetes.io/os

            operator: In

            values:

            - linux

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: kubernetes.io/hostname
```

### Worker Node Affinity[​](#worker-node-affinity "Direct link to Worker Node Affinity")

Configure affinity rules for worker nodes to optimize their distribution:

```
worker:

  mode: queue

  affinity:

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchLabels:

            app.kubernetes.io/name: n8n

            app.kubernetes.io/component: worker

        topologyKey: kubernetes.io/hostname

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: node-role.kubernetes.io/worker

            operator: Exists
```

### Webhook Node Affinity[​](#webhook-node-affinity "Direct link to Webhook Node Affinity")

Configure affinity rules for webhook nodes to ensure proper distribution:

```
webhook:

  mode: queue

  affinity:

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchLabels:

            app.kubernetes.io/name: n8n

            app.kubernetes.io/component: webhook

        topologyKey: kubernetes.io/hostname
```

### Common Affinity Patterns[​](#common-affinity-patterns "Direct link to Common Affinity Patterns")

#### Spread Pods Across Nodes[​](#spread-pods-across-nodes "Direct link to Spread Pods Across Nodes")

```
# Spread worker pods across different nodes

worker:

  mode: queue

  affinity:

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchLabels:

            app.kubernetes.io/name: n8n

            app.kubernetes.io/component: worker

        topologyKey: kubernetes.io/hostname
```

#### Zone Distribution[​](#zone-distribution "Direct link to Zone Distribution")

```
# Distribute pods across availability zones

main:

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: topology.kubernetes.io/zone
```

## Persistence Configuration[​](#persistence-configuration "Direct link to Persistence Configuration")

info

**Persistence:** Configure persistent storage for each node type independently. Persistence is used to store workflows, configuration, and npm packages. Configure independently from hostAliases.

### Main Node Persistence Example[​](#main-node-persistence-example "Direct link to Main Node Persistence Example")

```
main:

  persistence:

    enabled: true

    volumeName: "n8n-main-data"

    mountPath: "/home/node/.n8n"

    size: 8Gi

    accessMode: ReadWriteOnce

    storageClass: "fast-ssd"

    annotations:

      helm.sh/resource-policy: keep
```

### Worker Node Persistence Example[​](#worker-node-persistence-example "Direct link to Worker Node Persistence Example")

```
worker:

  mode: queue

  persistence:

    enabled: true

    volumeName: "n8n-worker-data"

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteMany  # For autoscaling

    storageClass: "fast-ssd"
```

***

## Host Aliases Configuration[​](#host-aliases-configuration "Direct link to Host Aliases Configuration")

info

**Host Aliases:** Host aliases provide custom DNS mappings for all node types. Configure hostAliases independently from persistence settings.

### Main Node Host Aliases Example[​](#main-node-host-aliases-example "Direct link to Main Node Host Aliases Example")

```
main:

  hostAliases:

    - ip: "127.0.0.1"

      hostnames:

        - "foo.local"

        - "bar.local"

    - ip: "10.1.2.3"

      hostnames:

        - "internal-api.local"

        - "database.local"
```

### Worker Node Host Aliases Example[​](#worker-node-host-aliases-example "Direct link to Worker Node Host Aliases Example")

```
worker:

  mode: queue

  hostAliases:

    - ip: "192.168.1.100"

      hostnames:

        - "worker-api.local"

    - ip: "10.0.0.50"

      hostnames:

        - "redis.local"

        - "postgres.local"
```

### Webhook Node Host Aliases Example[​](#webhook-node-host-aliases-example "Direct link to Webhook Node Host Aliases Example")

```
webhook:

  mode: queue

  hostAliases:

    - ip: "10.0.0.50"

      hostnames:

        - "webhook-service.local"

    - ip: "172.16.0.10"

      hostnames:

        - "external-api.local"
```

tip

**Separation of Concerns:** Persistence and hostAliases are configured independently and can be used together or separately as needed.

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

info

**Environment Variables:** Configure environment variables for all node types to customize behavior and integrate with external systems.

## Database Configuration[​](#database-configuration "Direct link to Database Configuration")

warning

**Production Database:** Use PostgreSQL for production deployments. SQLite is suitable only for development and testing.

info

**Cloud Databases:** For AWS RDS/Aurora, Azure Database for PostgreSQL, or Google Cloud SQL, see [Database Setup](/docs/charts/n8n/database-setup.md) for cloud-specific instructions.

### SQLite (Default)[​](#sqlite-default "Direct link to SQLite (Default)")

```
db:

  type: sqlite

  sqlite:

    database: database.sqlite

    poolSize: 0

    vacuum: false
```

danger

**SQLite Limitations:** SQLite is not suitable for production. It lacks concurrent access support and can cause data corruption under load.

### Bitnami's PostgreSQL Chart Configuration[​](#bitnamis-postgresql-chart-configuration "Direct link to Bitnami's PostgreSQL Chart Configuration")

```
db:

  type: postgresdb



postgresql:

  enabled: true

  auth:

    database: n8n

    username: n8n

    password: your-secure-password

  primary:

    persistence:

      enabled: true

      size: 10Gi
```

tip

**PostgreSQL Benefits:** PostgreSQL provides better performance, concurrent access, and supports all n8n features including queue mode.

### External PostgreSQL Configuration[​](#external-postgresql-configuration "Direct link to External PostgreSQL Configuration")

```
db:

  type: postgresdb



externalPostgresql:

  host: your-postgres-host

  port: 5432

  database: n8n

  username: n8n

  password: your-secure-password

  existingSecret: postgres-secret  # Optional: use existing secret
```

info

**External Database:** Use external databases for better resource isolation and management flexibility.

## Queue Mode Configuration[​](#queue-mode-configuration "Direct link to Queue Mode Configuration")

info

**Queue Mode Benefits:** Queue mode enables distributed execution, better resource utilization, and improved reliability.

### Bitnami's Redis Chart Configuration[​](#bitnamis-redis-chart-configuration "Direct link to Bitnami's Redis Chart Configuration")

```
redis:

  enabled: true

  architecture: standalone

  auth:

    enabled: true

    password: your-redis-password
```

warning

**Redis Security:** Always enable Redis authentication in production environments.

### External Redis Configuration[​](#external-redis-configuration "Direct link to External Redis Configuration")

```
externalRedis:

  host: your-redis-host

  port: 6379

  username: default

  password: your-redis-password

  existingSecret: redis-secret  # Optional: use existing secret
```

tip

**Redis Planning:** Ensure Redis has sufficient memory and persistence configuration for your workload.

### Worker Configuration[​](#worker-configuration "Direct link to Worker Configuration")

```
worker:

  mode: queue

  count: 3

  concurrency: 10

  autoscaling:

    enabled: true

    minReplicas: 2

    maxReplicas: 10
```

info

**Worker Tuning:** Adjust worker count and concurrency based on your workflow complexity and resource availability.

### Webhook Configuration[​](#webhook-configuration "Direct link to Webhook Configuration")

```
webhook:

  mode: queue

  count: 2

  url: https://webhook.yourdomain.com

  autoscaling:

    enabled: true

    minReplicas: 2

    maxReplicas: 5
```

tip

**Webhook Scaling:** Dedicated webhook nodes improve performance for high-volume webhook processing.

## Storage Configuration[​](#storage-configuration "Direct link to Storage Configuration")

info

**Storage Strategy:** Choose storage options based on your data persistence and performance requirements.

### Binary Data Storage[​](#binary-data-storage "Direct link to Binary Data Storage")

```
binaryData:

  mode: default  # default, filesystem, s3

  localStoragePath: /n8n/data
```

warning

**Data Persistence:** Default mode stores data in memory and will be lost on pod restart. Use filesystem or S3 for persistence.

### S3 Storage[​](#s3-storage "Direct link to S3 Storage")

warning

**Enterprise License:** Enterprise n8n license required for s3 binary data storage capability.

```
binaryData:

  mode: s3

  s3:

    host: s3.amazonaws.com

    bucketName: n8n-binary-data

    bucketRegion: us-east-1

    accessKey: your-access-key

    accessSecret: your-secret-key

    existingSecret: s3-secret  # Optional: use existing secret
```

tip

**S3 Benefits:** S3 storage provides scalability, durability, and enables team collaboration.

### MinIO Integration[​](#minio-integration "Direct link to MinIO Integration")

```
minio:

  enabled: true

  rootUser: minioadmin

  rootPassword: minioadmin

  buckets:

    - name: n8n-bucket

      policy: none
```

info

**Self-Hosted Storage:** MinIO provides S3-compatible storage for on-premises deployments.

## Node Configuration[​](#node-configuration "Direct link to Node Configuration")

info

**Node Management:** Configure npm package installation and built-in module access for enhanced workflow capabilities.

### External npm Packages[​](#external-npm-packages "Direct link to External npm Packages")

```
nodes:

  external:

    allowAll: false

    packages:

      - "moment@2.29.4"

      - "lodash@4.17.21"

    reinstallMissingPackages: true
```

warning

**Package Security:** Only install trusted npm packages. Review packages for security vulnerabilities before installation.

### Built-in Modules[​](#built-in-modules "Direct link to Built-in Modules")

```
nodes:

  builtin:

    enabled: true

    modules:

      - crypto

      - fs

      - path
```

tip

**Module Access:** Enable built-in modules to enhance Code node capabilities while maintaining security.

### Private npm Registry[​](#private-npm-registry "Direct link to Private npm Registry")

```
npmRegistry:

  enabled: true

  url: https://your-registry.com

  secretName: npm-registry-secret

  secretKey: npmrc
```

info

**Private Registry:** Use private registries for internal packages and enhanced security.

## Monitoring Configuration[​](#monitoring-configuration "Direct link to Monitoring Configuration")

tip

**Observability:** Enable monitoring to track n8n performance, identify issues, and optimize resource usage.

### ServiceMonitor[​](#servicemonitor "Direct link to ServiceMonitor")

```
serviceMonitor:

  enabled: true

  interval: 30s

  labels:

    release: prometheus

  include:

    defaultMetrics: true

    apiEndpoints: true

    queueMetrics: true
```

info

**Prometheus Integration:** ServiceMonitor enables automatic metric collection by Prometheus Operator.

### Metrics Configuration[​](#metrics-configuration "Direct link to Metrics Configuration")

```
serviceMonitor:

  metricsPrefix: n8n_

  include:

    defaultMetrics: true

    apiEndpoints: true

    apiMethodLabel: true

    apiPathLabel: true

    apiStatusCodeLabel: true

    cacheMetrics: true

    credentialTypeLabel: true

    messageEventBusMetrics: true

    nodeTypeLabel: true

    queueMetrics: true

    workflowIdLabel: true
```

tip

**Metric Granularity:** Enable specific metrics based on your monitoring needs and resource constraints.

## Security Configuration[​](#security-configuration "Direct link to Security Configuration")

warning

**Security Best Practices:** Implement these security measures to protect your n8n deployment.

### Security Context[​](#security-context "Direct link to Security Context")

UID `1000` and GID `1000` default node user and group IDs.

```
securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

  readOnlyRootFilesystem: false

  runAsNonRoot: true

  runAsUser: 1000

  runAsGroup: 1000



podSecurityContext:

  fsGroup: 1000

  fsGroupChangePolicy: OnRootMismatch
```

danger

**Security Context:** Always run containers as non-root users and drop unnecessary capabilities.

### RBAC Configuration[​](#rbac-configuration "Direct link to RBAC Configuration")

```
serviceAccount:

  create: true

  automount: true

  annotations: {}

  name: ""
```

tip

**RBAC Best Practices:** Use dedicated service accounts and implement least-privilege access policies.

### Encryption Key[​](#encryption-key "Direct link to Encryption Key")

```
encryptionKey: your-32-character-encryption-key

existingEncryptionKeySecret: n8n-encryption-key
```

warning

**Encryption Security:** Use strong encryption keys and store them securely in Kubernetes secrets.

## Task Runners[​](#task-runners "Direct link to Task Runners")

info

**Task Runner Modes:** Choose between internal and external task runners based on your security and performance requirements.

### Internal Task Runners[​](#internal-task-runners "Direct link to Internal Task Runners")

```
taskRunners:

  mode: internal

  maxConcurrency: 5

  taskTimeout: 60

  taskHeartbeatInterval: 30
```

tip

**Internal Runners:** Internal task runners are simpler to configure and suitable for most use cases.

### External Task Runners[​](#external-task-runners "Direct link to External Task Runners")

```
taskRunners:

  mode: external

  broker:

    address: 127.0.0.1

    port: 5679

  external:

    port: 5680

    autoShutdownTimeout: 15

    resources:

      requests:

        cpu: 100m

        memory: 32Mi

      limits:

        cpu: 2000m

        memory: 512Mi
```

warning

**Enterprise Feature:** External task runners require n8n Enterprise license.

danger

**License Requirement:** Verify your n8n Enterprise license before enabling external task runners.

## Workflow History[​](#workflow-history "Direct link to Workflow History")

info

**History Management:** Configure workflow history to track changes and enable rollback capabilities.

### History Configuration[​](#history-configuration "Direct link to History Configuration")

```
workflowHistory:

  enabled: true

  pruneTime: 336  # in hours (14 days)
```

tip

**History Retention:** Set appropriate retention periods to balance storage usage with audit requirements.

## API Configuration[​](#api-configuration "Direct link to API Configuration")

info

**API Access:** Configure the public API for external integrations and automation.

### Public API[​](#public-api "Direct link to Public API")

```
api:

  enabled: true

  path: api

  swagger:

    enabled: true
```

warning

**API Security:** Secure API access with proper authentication and authorization mechanisms.

## Diagnostics and Telemetry[​](#diagnostics-and-telemetry "Direct link to Diagnostics and Telemetry")

note

**Telemetry Configuration:** Configure diagnostics and telemetry based on your privacy and monitoring requirements.

### Diagnostics[​](#diagnostics "Direct link to Diagnostics")

```
diagnostics:

  enabled: false

  frontendConfig: "1zPn9bgWPzlQc0p8Gj1uiK6DOTn;https://telemetry.n8n.io"

  backendConfig: "1zPn7YoGC3ZXE9zLeTKLuQCB4F6;https://telemetry.n8n.io"
```

tip

**Privacy Control:** Disable diagnostics if you prefer not to share usage data with n8n.

### Sentry Integration[​](#sentry-integration "Direct link to Sentry Integration")

```
sentry:

  enabled: true

  backendDsn: your-backend-dsn

  frontendDsn: your-frontend-dsn

  externalTaskRunnersDsn: your-external-runners-dsn
```

info

**Error Tracking:** Sentry integration helps track and resolve application errors in production environments.

## DNS Configuration[​](#dns-configuration "Direct link to DNS Configuration")

info

**DNS Settings:** Configure DNS policies and settings for advanced networking requirements.

### DNS Policy[​](#dns-policy "Direct link to DNS Policy")

```
dnsPolicy: ClusterFirst
```

### DNS Config[​](#dns-config "Direct link to DNS Config")

```
dnsConfig:

  nameservers:

    - 8.8.8.8

    - 8.8.4.4

  searches:

    - your-domain.com

  options:

    - name: ndots

      value: "2"
```

tip

**DNS Optimization:** Configure DNS settings for better network performance and reliability.

## Best Practices[​](#best-practices "Direct link to Best Practices")

tip

**Production Recommendations:** Follow these best practices for secure and reliable n8n deployments.

### Security Checklist[​](#security-checklist "Direct link to Security Checklist")

* <!-- -->
  Enable authentication
* <!-- -->
  Use TLS certificates
* <!-- -->
  Configure RBAC policies
* <!-- -->
  Set resource limits
* <!-- -->
  Use secrets for sensitive data
* <!-- -->
  Enable monitoring
* <!-- -->
  Regular backups

### Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

* <!-- -->
  Use PostgreSQL for production
* <!-- -->
  Enable queue mode for high workloads
* <!-- -->
  Configure appropriate resource limits
* <!-- -->
  Use S3 storage for binary data
* <!-- -->
  Monitor and tune autoscaling

warning

**Regular Maintenance:** Perform regular updates, security patches, and performance monitoring.

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

info

**Common Issues:** This section covers frequently encountered configuration problems and solutions.

### Configuration Validation[​](#configuration-validation "Direct link to Configuration Validation")

```
# Validate Helm values

helm template my-n8n community-charts/n8n -f values.yaml --dry-run



# Check for configuration errors

helm lint my-n8n community-charts/n8n -f values.yaml
```

### Common Configuration Issues[​](#common-configuration-issues "Direct link to Common Configuration Issues")

1. **Resource Limits Too Low**: Increase CPU/memory limits
2. **Database Connection Issues**: Verify database credentials and connectivity
3. **Storage Problems**: Check PVC status and permissions
4. **Ingress Issues**: Verify ingress controller and TLS configuration

tip

**Debug Commands:** Use these commands to validate and troubleshoot configuration issues.

## Next Steps[​](#next-steps "Direct link to Next Steps")

tip

**Configuration Guide:** Follow these guides to implement specific features and configurations.

* [Database Setup](/docs/charts/n8n/database-setup.md) - PostgreSQL and external database configuration
* [Queue Mode Setup](/docs/charts/n8n/queue-mode.md) - Distributed execution with Redis
* [Storage Configuration](/docs/charts/n8n/storage.md) - Binary data storage options
* [Monitoring Setup](/docs/charts/n8n/monitoring.md) - Metrics and observability
* [Troubleshooting](/docs/charts/n8n/troubleshooting.md) - Common issues and solutions

info

**Advanced Configuration:** Explore advanced features like external task runners, custom nodes, and enterprise integrations.

tip

**Cloud Redis:** For managed Redis on GCP, AWS, or Azure, see [Cloud Redis Setup](/docs/charts/n8n/cloud-redis.md).


---

# n8n Database Setup

n8n supports multiple database backends for storing workflows, executions, and metadata. This guide covers all database options and their configuration.

info

**Database Selection:** Choose your database based on your deployment requirements. PostgreSQL is recommended for production environments.

## Database Options[​](#database-options "Direct link to Database Options")

### SQLite (Default)[​](#sqlite-default "Direct link to SQLite (Default)")

* **Use Case:** Development, testing, single-node deployments
* **Pros:** Simple setup, no external dependencies
* **Cons:** Not suitable for production, limited concurrency
* **Storage:** File-based, stored in persistent volume

### PostgreSQL (Recommended for Production)[​](#postgresql-recommended-for-production "Direct link to PostgreSQL (Recommended for Production)")

* **Use Case:** Production deployments, high availability
* **Pros:** ACID compliance, high concurrency, backup support
* **Cons:** Requires external database setup
* **Storage:** External database server

warning

**Production Warning:** SQLite is not suitable for production deployments. Use PostgreSQL for any production environment.

## SQLite Configuration[​](#sqlite-configuration "Direct link to SQLite Configuration")

tip

**Development Use:** SQLite is perfect for development, testing, and single-user scenarios.

### Basic SQLite Setup[​](#basic-sqlite-setup "Direct link to Basic SQLite Setup")

```
db:

  type: sqlite

  sqlite:

    database: "database.sqlite"

    poolSize: 0  # Disable connection pooling

    vacuum: false  # Disable VACUUM on startup



# Enable persistence for data durability

main:

  persistence:

    enabled: true

    volumeName: "n8n-sqlite-data"

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteOnce
```

warning

**Data Persistence:** Without persistence enabled, SQLite data will be lost when the pod is terminated. Enable persistence for any deployment where data retention is important.

### SQLite with Persistence[​](#sqlite-with-persistence "Direct link to SQLite with Persistence")

tip

**SQLite Persistence:** Enable persistence to store SQLite database in a persistent volume, ensuring data survives pod restarts and deployments.

```
db:

  type: sqlite

  sqlite:

    database: "n8n-data.sqlite"

    poolSize: 0

    vacuum: true  # Enable VACUUM for better performance



# Enable persistence for SQLite storage

main:

  persistence:

    enabled: true

    volumeName: "n8n-sqlite-data"

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteOnce

    storageClass: "fast-ssd"

    annotations:

      helm.sh/resource-policy: keep
```

info

**Persistence Benefits:** With persistence enabled, your SQLite database will be stored in a persistent volume, providing data durability across pod restarts and deployments.

### SQLite with Custom Path and Existing PVC[​](#sqlite-with-custom-path-and-existing-pvc "Direct link to SQLite with Custom Path and Existing PVC")

```
db:

  type: sqlite

  sqlite:

    database: "n8n-data.sqlite"

    poolSize: 0

    vacuum: true  # Enable VACUUM for better performance



# Use existing PVC for SQLite storage

main:

  persistence:

    enabled: true

    existingClaim: "n8n-sqlite-pvc"

    mountPath: "/home/node/.n8n"
```

warning

**Data Persistence:** Without persistence, SQLite data is ephemeral and will be lost when the pod is terminated. Always enable persistence for production deployments.

### SQLite Performance Tuning[​](#sqlite-performance-tuning "Direct link to SQLite Performance Tuning")

```
db:

  type: sqlite

  sqlite:

    database: "database.sqlite"

    poolSize: 0

    vacuum: true  # Rebuild database on startup



# Enable database logging for troubleshooting

db:

  logging:

    enabled: true

    options: error

    maxQueryExecutionTime: 1000
```

## PostgreSQL Configuration[​](#postgresql-configuration "Direct link to PostgreSQL Configuration")

tip

**Production Recommendation:** PostgreSQL is the recommended database for production deployments due to its reliability, performance, and feature set.

### PostgreSQL with Bitnami Chart[​](#postgresql-with-bitnami-chart "Direct link to PostgreSQL with Bitnami Chart")

```
db:

  type: postgresdb

  logging:

    enabled: true

    options: error

    maxQueryExecutionTime: 1000



postgresql:

  enabled: true

  architecture: standalone



  auth:

    username: n8n

    password: your-secure-password

    database: n8n



  primary:

    service:

      ports:

        postgresql: 5432



    persistence:

      enabled: true

      existingClaim: ""

      storageClass: "fast-ssd"

      size: 20Gi



    resources:

      requests:

        cpu: 100m

        memory: 256Mi

      limits:

        cpu: 1000m

        memory: 1Gi
```

note

**Security:** Always use strong, unique passwords for database credentials. Consider using Kubernetes secrets for sensitive data.

### PostgreSQL High Availability[​](#postgresql-high-availability "Direct link to PostgreSQL High Availability")

```
db:

  type: postgresdb



postgresql:

  enabled: true

  architecture: replication  # Enable replication



  auth:

    username: n8n

    password: your-secure-password

    database: n8n



  primary:

    persistence:

      enabled: true

      size: 20Gi



    service:

      type: ClusterIP



  readReplicas:

    persistence:

      enabled: true

      size: 20Gi



    resources:

      requests:

        cpu: 100m

        memory: 256Mi

      limits:

        cpu: 500m

        memory: 512Mi
```

info

**High Availability:** Use replication architecture for production environments that require high availability and read scaling.

### External PostgreSQL[​](#external-postgresql "Direct link to External PostgreSQL")

```
db:

  type: postgresdb



externalPostgresql:

  host: your-postgres-host.com

  port: 5432

  username: n8n

  password: your-secure-password

  database: n8n

  existingSecret: postgres-secret  # Use Kubernetes secret
```

### Google Cloud SQL (GCP) with Cloud SQL Proxy[​](#google-cloud-sql-gcp-with-cloud-sql-proxy "Direct link to Google Cloud SQL (GCP) with Cloud SQL Proxy")

tip

**GKE + Cloud SQL:** If you are running n8n on Google Kubernetes Engine (GKE) and want to use Google Cloud SQL (PostgreSQL), you must use the Cloud SQL Auth Proxy as a sidecar container. This is required because Cloud SQL is not directly accessible from GKE nodes.

#### Example: Add Cloud SQL Proxy Sidecar to n8n Main Pod[​](#example-add-cloud-sql-proxy-sidecar-to-n8n-main-pod "Direct link to Example: Add Cloud SQL Proxy Sidecar to n8n Main Pod")

```
db:

  type: postgresdb



externalPostgresql:

  host: 127.0.0.1  # Cloud SQL Proxy listens on localhost

  port: 5432       # Default proxy port

  username: n8n

  password: your-secure-password

  database: n8n

  existingSecret: postgres-secret



main:

  extraContainers:

    - name: cloudsql-proxy

      image: gcr.io/cloudsql-docker/gce-proxy:1.36.2

      command:

        - "/cloud_sql_proxy"

        - "-instances=YOUR_PROJECT:YOUR_REGION:YOUR_INSTANCE=tcp:5432"

        # Use one of the following for authentication:

        # - "-credential_file=/secrets/cloudsql/credentials.json"  # Service Account Key

        # OR (for Workload Identity, omit -credential_file)

      securityContext:

        runAsNonRoot: true

        allowPrivilegeEscalation: false

      volumeMounts:

        - name: cloudsql-instance-credentials

          mountPath: /secrets/cloudsql

          readOnly: true

  volumes:

    - name: cloudsql-instance-credentials

      secret:

        secretName: cloudsql-instance-credentials
```

* Replace `YOUR_PROJECT:YOUR_REGION:YOUR_INSTANCE` with your Cloud SQL instance connection name.
* If using a service account key, create a Kubernetes secret named `cloudsql-instance-credentials` with the key as `credentials.json`.
* If using Workload Identity, you can omit the `-credential_file` flag and the volume mount.

info

**Workload Identity:** For production, prefer [Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) over service account keys for better security.

#### Troubleshooting Cloud SQL Proxy[​](#troubleshooting-cloud-sql-proxy "Direct link to Troubleshooting Cloud SQL Proxy")

* Check Cloud SQL Proxy logs in the n8n main pod: `kubectl logs <n8n-pod> -c cloudsql-proxy`
* Ensure the service account has the `Cloud SQL Client` role.
* Verify the instance connection name is correct.
* Make sure the proxy port matches `externalPostgresql.port`.
* Network policies/firewall must allow egress to Cloud SQL.

For more, see [Cloud SQL Auth Proxy docs](https://cloud.google.com/sql/docs/postgres/connect-run#kubernetes-engine).

## AWS RDS/Aurora PostgreSQL[​](#aws-rdsaurora-postgresql "Direct link to AWS RDS/Aurora PostgreSQL")

info

Amazon RDS and Aurora PostgreSQL are fully managed database services on AWS. They are recommended for production deployments due to their reliability, scalability, and security features.

### Connecting n8n to AWS RDS/Aurora[​](#connecting-n8n-to-aws-rdsaurora "Direct link to Connecting n8n to AWS RDS/Aurora")

* Ensure your EKS cluster can reach the RDS/Aurora instance (VPC, subnet, and security group settings).
* Enable SSL for secure connections (recommended).
* Use IAM authentication for advanced security (optional, see AWS docs).

#### Example `values.yaml` for External PostgreSQL[​](#example-valuesyaml-for-external-postgresql "Direct link to example-valuesyaml-for-external-postgresql")

```
db:

  type: postgresdb

externalPostgresql:

  host: "<rds-endpoint>.rds.amazonaws.com"

  port: 5432

  username: "n8nuser"

  password: "<your-password>"

  database: "n8n"
```

tip

You can use `externalPostgresql.existingSecret` to reference a Kubernetes secret for your password.

#### Security Group & Networking Tips[​](#security-group--networking-tips "Direct link to Security Group & Networking Tips")

* The RDS instance must allow inbound connections from your EKS nodes (check security group rules).
* Prefer private subnets and VPC peering for security.
* If using IAM authentication, see [IAM DB Auth for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.html).

#### Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

* **Timeouts:** Check VPC/subnet routing and security groups.
* **SSL errors:** Ensure `rds.force_ssl=1` and use the correct SSL mode in n8n.
* **Auth errors:** Double-check username/password and DB user privileges.

note

See the [AWS RDS PostgreSQL documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html) for more details.

## Azure Database for PostgreSQL[​](#azure-database-for-postgresql "Direct link to Azure Database for PostgreSQL")

info

Azure Database for PostgreSQL is a fully managed database service on Microsoft Azure. It supports both Single Server and Flexible Server deployments.

### Connecting n8n to Azure Database for PostgreSQL[​](#connecting-n8n-to-azure-database-for-postgresql "Direct link to Connecting n8n to Azure Database for PostgreSQL")

* Ensure your AKS cluster can reach the Azure Database (VNet, firewall, and subnet settings).
* Use the full username format: `<username>@<server-name>`.
* SSL is required by default.

#### Example `values.yaml` for External PostgreSQL[​](#example-valuesyaml-for-external-postgresql-1 "Direct link to example-valuesyaml-for-external-postgresql-1")

```
db:

  type: postgresdb

externalPostgresql:

  host: "<server-name>.postgres.database.azure.com"

  port: 5432

  username: "n8nuser@<server-name>"

  password: "<your-password>"

  database: "n8n"
```

tip

You can use `externalPostgresql.existingSecret` to reference a Kubernetes secret for your password.

#### Firewall & Networking Tips[​](#firewall--networking-tips "Direct link to Firewall & Networking Tips")

* Add your AKS node subnet to the Azure Database firewall rules.
* For private access, use VNet integration.
* Ensure SSL is enabled (default for Azure).

#### Troubleshooting[​](#troubleshooting-1 "Direct link to Troubleshooting")

* **FATAL: no pg\_hba.conf entry:** Check firewall and username format.
* **SSL required:** Ensure SSL mode is enabled in n8n.
* **Auth errors:** Double-check username/password and DB user privileges.

note

See the [Azure Database for PostgreSQL documentation](https://learn.microsoft.com/en-us/azure/postgresql/) for more details.

## Database Migration[​](#database-migration "Direct link to Database Migration")

danger

**Backup First:** Always create a complete backup of your existing database before attempting any migration.

### SQLite to PostgreSQL Migration[​](#sqlite-to-postgresql-migration "Direct link to SQLite to PostgreSQL Migration")

1. **Backup SQLite Database**

```
# Get the SQLite database from the pod

kubectl cp <namespace>/<n8n-pod>:/home/node/.n8n/database.sqlite ./n8n-backup.sqlite
```

2. **Export Data from SQLite**

```
# Install sqlite3 if not available

sqlite3 n8n-backup.sqlite ".dump" > n8n-dump.sql
```

3. **Import to PostgreSQL**

```
# Connect to PostgreSQL and import

psql -h your-postgres-host -U n8n -d n8n -f n8n-dump.sql
```

4. **Update Helm Configuration**

```
db:

  type: postgresdb



postgresql:

  enabled: true

  auth:

    username: n8n

    password: your-secure-password

    database: n8n
```

5. **Upgrade Helm Release**

```
helm upgrade my-n8n community-charts/n8n -f values.yaml -n <namespace>
```

### PostgreSQL to PostgreSQL Migration[​](#postgresql-to-postgresql-migration "Direct link to PostgreSQL to PostgreSQL Migration")

1. **Backup Source Database**

```
pg_dump -h source-host -U n8n -d n8n > n8n-backup.sql
```

2. **Restore to Target Database**

```
psql -h target-host -U n8n -d n8n -f n8n-backup.sql
```

3. **Update Configuration**

```
db:

  type: postgresdb



externalPostgresql:

  host: new-postgres-host.com

  port: 5432

  username: n8n

  password: your-secure-password

  database: n8n
```

## Persistence for Database Configuration[​](#persistence-for-database-configuration "Direct link to Persistence for Database Configuration")

info

**Persistence:** Use persistence to store database configuration and credentials securely for main and worker nodes. Configure independently from hostAliases.

### Main Node Persistence Example[​](#main-node-persistence-example "Direct link to Main Node Persistence Example")

```
main:

  count: 1

  persistence:

    enabled: true

    volumeName: "n8n-main-data"

    mountPath: "/home/node/.n8n"

    size: 8Gi

    accessMode: ReadWriteOnce

    storageClass: "fast-ssd"

    annotations:

      helm.sh/resource-policy: keep
```

### Worker Node Persistence Example[​](#worker-node-persistence-example "Direct link to Worker Node Persistence Example")

```
worker:

  mode: queue

  persistence:

    enabled: true

    volumeName: "n8n-worker-data"

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteMany  # For autoscaling

    storageClass: "fast-ssd"
```

## Troubleshooting[​](#troubleshooting-2 "Direct link to Troubleshooting")

### Common Database Issues[​](#common-database-issues "Direct link to Common Database Issues")

#### Performance Issues[​](#performance-issues "Direct link to Performance Issues")

```
# Enable query logging for analysis

db:

  logging:

    enabled: true

    options: all

    maxQueryExecutionTime: 100



# Increase connection pool

db:

  sqlite:

    poolSize: 20
```

### Database Health Checks[​](#database-health-checks "Direct link to Database Health Checks")

```
# Add database health check

main:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 5

    periodSeconds: 5

    timeoutSeconds: 3

    failureThreshold: 3
```

### Database Monitoring[​](#database-monitoring "Direct link to Database Monitoring")

```
# Enable database metrics

serviceMonitor:

  enabled: true

  include:

    defaultMetrics: true

    cacheMetrics: true
```

## Pod Affinity and Anti-Affinity[​](#pod-affinity-and-anti-affinity "Direct link to Pod Affinity and Anti-Affinity")

tip

**Database Affinity:** Proper affinity configuration can optimize database performance by ensuring pods are placed optimally relative to database resources.

warning

**Deprecation Notice:** The top-level `affinity` field is deprecated. Use the specific affinity configurations under `main`, `worker`, and `webhook` blocks instead.

### Affinity for Database Optimization[​](#affinity-for-database-optimization "Direct link to Affinity for Database Optimization")

#### Co-locate with Database Nodes[​](#co-locate-with-database-nodes "Direct link to Co-locate with Database Nodes")

```
# Place pods on nodes close to database

main:

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: database-zone

            operator: In

            values:

            - "primary"



worker:

  mode: queue

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: database-zone

            operator: In

            values:

            - "primary"
```

#### Spread Pods for Database Load Distribution[​](#spread-pods-for-database-load-distribution "Direct link to Spread Pods for Database Load Distribution")

```
# Distribute database connections across nodes

main:

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: kubernetes.io/hostname



worker:

  mode: queue

  affinity:

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - n8n

          - key: app.kubernetes.io/component

            operator: In

            values:

            - worker

        topologyKey: kubernetes.io/hostname
```

#### Zone Distribution for Database Resilience[​](#zone-distribution-for-database-resilience "Direct link to Zone Distribution for Database Resilience")

```
# Distribute pods across zones for database availability

main:

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: topology.kubernetes.io/zone



webhook:

  mode: queue

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

            - key: app.kubernetes.io/component

              operator: In

              values:

              - webhook

          topologyKey: topology.kubernetes.io/zone
```

#### Node Affinity for Database Performance[​](#node-affinity-for-database-performance "Direct link to Node Affinity for Database Performance")

```
# Use nodes optimized for database workloads

main:

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: node-type

            operator: In

            values:

            - database-optimized



worker:

  mode: queue

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: node-type

            operator: In

            values:

            - database-optimized
```

info

**Database Benefits:** Proper affinity configuration ensures optimal database performance by placing pods on nodes with good database connectivity and distributing database load effectively.

## Best Practices[​](#best-practices "Direct link to Best Practices")

### Security[​](#security "Direct link to Security")

* Use strong, unique passwords for database users
* Store credentials in Kubernetes secrets
* Enable SSL/TLS for database connections
* Use network policies to restrict access
* Regularly rotate database credentials

### Performance[​](#performance "Direct link to Performance")

* Use PostgreSQL for production workloads
* Configure appropriate connection pools
* Monitor database performance metrics
* Use SSD storage for database volumes
* Enable query logging for optimization

### Reliability[​](#reliability "Direct link to Reliability")

* Set up automated backups
* Test backup and recovery procedures
* Use high availability configurations
* Monitor database health
* Plan for disaster recovery

### Maintenance[​](#maintenance "Direct link to Maintenance")

* Regularly update database versions
* Monitor disk space usage
* Clean up old data and logs
* Optimize database queries
* Review and update security policies

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Usage Guide](/docs/charts/n8n/usage.md) - Quick start and basic deployment
* [Configuration Guide](/docs/charts/n8n/configuration.md) - Detailed configuration options
* [Queue Mode Setup](/docs/charts/n8n/queue-mode.md) - Distributed execution with Redis
* [Storage Configuration](/docs/charts/n8n/storage.md) - Binary data storage options
* [Monitoring Setup](/docs/charts/n8n/monitoring.md) - Metrics and observability
* [Troubleshooting](/docs/charts/n8n/troubleshooting.md) - Common issues and solutions


---

# n8n Monitoring Setup

Comprehensive monitoring and observability are essential for production n8n deployments. This guide covers all monitoring options including Prometheus metrics, logging, health checks, and alerting.

info

**Production Monitoring:** Proper monitoring is crucial for production deployments. It helps you identify issues early, track performance, and ensure system reliability.

## Monitoring Overview[​](#monitoring-overview "Direct link to Monitoring Overview")

tip

**Monitoring Strategy:** Implement monitoring at multiple levels: application metrics, infrastructure metrics, and business metrics for comprehensive observability.

### Available Metrics[​](#available-metrics "Direct link to Available Metrics")

* **Application Metrics**: Workflow executions, API calls, performance
* **Queue Metrics**: Job processing, queue depths, worker utilization
* **System Metrics**: CPU, memory, disk usage
* **Custom Metrics**: Business-specific KPIs

### Monitoring Components[​](#monitoring-components "Direct link to Monitoring Components")

* **Prometheus**: Metrics collection and storage
* **ServiceMonitor**: Kubernetes-native monitoring
* **Logging**: Structured logging with configurable levels
* **Health Checks**: Liveness and readiness probes
* **Alerting**: Prometheus alerting rules

## Prometheus Metrics Configuration[​](#prometheus-metrics-configuration "Direct link to Prometheus Metrics Configuration")

note

**Prometheus Operator:** This guide assumes you have Prometheus Operator installed. If not, you'll need to set up Prometheus separately.

### Basic ServiceMonitor Setup[​](#basic-servicemonitor-setup "Direct link to Basic ServiceMonitor Setup")

```
serviceMonitor:

  enabled: true

  interval: 30s

  timeout: 10s

  labels:

    release: prometheus

  include:

    defaultMetrics: true

    cacheMetrics: false

    messageEventBusMetrics: false

    workflowIdLabel: false

    nodeTypeLabel: false

    credentialTypeLabel: false

    apiEndpoints: false

    queueMetrics: false
```

### Advanced ServiceMonitor Configuration[​](#advanced-servicemonitor-configuration "Direct link to Advanced ServiceMonitor Configuration")

```
serviceMonitor:

  enabled: true

  namespace: monitoring

  interval: 15s

  timeout: 10s

  labels:

    release: prometheus

    team: platform

  targetLabels:

    - app.kubernetes.io/name

    - app.kubernetes.io/instance

  metricRelabelings:

    - sourceLabels: [prometheus_replica]

      regex: (.*)

      targetLabel: another_prometheus_replica

      action: replace

  include:

    defaultMetrics: true

    cacheMetrics: true

    messageEventBusMetrics: true

    workflowIdLabel: true

    nodeTypeLabel: true

    credentialTypeLabel: true

    apiEndpoints: true

    apiPathLabel: true

    apiMethodLabel: true

    apiStatusCodeLabel: true

    queueMetrics: true
```

warning

**Metric Volume:** Be cautious with enabling all metrics in high-traffic environments as it can increase Prometheus storage requirements and query latency.

### Available Metrics[​](#available-metrics-1 "Direct link to Available Metrics")

#### Default Metrics[​](#default-metrics "Direct link to Default Metrics")

* `n8n_execution_total` - Total workflow executions
* `n8n_execution_duration_seconds` - Execution duration histogram
* `n8n_execution_failed_total` - Failed executions
* `n8n_workflow_total` - Total workflows
* `n8n_credential_total` - Total credentials
* `n8n_node_total` - Total nodes

#### Queue Metrics (Queue Mode)[​](#queue-metrics-queue-mode "Direct link to Queue Metrics (Queue Mode)")

* `n8n_queue_bull_queue_waiting` - Jobs waiting in queue
* `n8n_queue_bull_queue_active` - Active jobs
* `n8n_queue_bull_queue_completed` - Completed jobs
* `n8n_queue_bull_queue_failed` - Failed jobs
* `n8n_queue_bull_queue_delayed` - Delayed jobs

#### API Metrics[​](#api-metrics "Direct link to API Metrics")

* `n8n_api_requests_total` - Total API requests
* `n8n_api_request_duration_seconds` - API request duration
* `n8n_api_requests_failed_total` - Failed API requests

#### Queue Mode Endpoint Metrics[​](#queue-mode-endpoint-metrics "Direct link to Queue Mode Endpoint Metrics")

* **MCP Endpoints**: Monitor `/mcp/` and `/mcp-test/` endpoint performance
* **Form Endpoints**: Monitor `/form/`, `/form-test/`, and `/form-waiting/` endpoint performance
* **Webhook Endpoints**: Monitor `/webhook/` and `/webhook-test/` endpoint performance

tip

**Endpoint Monitoring:** In queue mode, different endpoints are handled by different node types. Monitor webhook nodes for MCP and Form endpoint performance.

#### Cache Metrics[​](#cache-metrics "Direct link to Cache Metrics")

* `n8n_cache_hits_total` - Cache hits
* `n8n_cache_misses_total` - Cache misses
* `n8n_cache_size_bytes` - Cache size

### Prometheus Queries[​](#prometheus-queries "Direct link to Prometheus Queries")

tip

**Query Optimization:** Use appropriate time ranges and aggregation functions to optimize query performance in Prometheus.

#### Basic Queries[​](#basic-queries "Direct link to Basic Queries")

```
# Execution rate (executions per second)

rate(n8n_execution_total[5m])



# Average execution duration

histogram_quantile(0.95, rate(n8n_execution_duration_seconds_bucket[5m]))



# Error rate

rate(n8n_execution_failed_total[5m])



# Queue depth (queue mode)

n8n_queue_bull_queue_waiting



# API request rate

rate(n8n_api_requests_total[5m])
```

#### Advanced Queries[​](#advanced-queries "Direct link to Advanced Queries")

```
# Success rate

(

  rate(n8n_execution_total[5m]) - rate(n8n_execution_failed_total[5m])

) / rate(n8n_execution_total[5m]) * 100



# 95th percentile execution time

histogram_quantile(0.95, rate(n8n_execution_duration_seconds_bucket[5m]))



# Queue utilization (queue mode)

n8n_queue_bull_queue_active / (n8n_queue_bull_queue_waiting + n8n_queue_bull_queue_active) * 100



# Cache hit ratio

rate(n8n_cache_hits_total[5m]) / (rate(n8n_cache_hits_total[5m]) + rate(n8n_cache_misses_total[5m])) * 100
```

## Logging Configuration[​](#logging-configuration "Direct link to Logging Configuration")

info

**Log Management:** Configure appropriate log levels and outputs based on your environment. Use structured logging for better log analysis.

### Basic Logging[​](#basic-logging "Direct link to Basic Logging")

```
log:

  level: info

  output:

    - console

  scopes: []
```

### Advanced Logging[​](#advanced-logging "Direct link to Advanced Logging")

```
log:

  level: info

  output:

    - console

    - file

  scopes:

    - concurrency

    - external-secrets

    - license

    - multi-main-setup

    - pubsub

    - redis

    - scaling

    - waiting-executions

  file:

    location: "logs/n8n.log"

    maxsize: 16

    maxcount: "100"
```

### Structured Logging[​](#structured-logging "Direct link to Structured Logging")

```
log:

  level: info

  output:

    - console

  scopes:

    - concurrency

    - redis

    - scaling
```

### Log Aggregation[​](#log-aggregation "Direct link to Log Aggregation")

```
# Configure log forwarding to external systems

main:

  extraContainers:

    - name: fluentd

      image: fluent/fluentd-kubernetes-daemonset:v1-debian-elasticsearch

      volumeMounts:

        - name: varlog

          mountPath: /var/log

        - name: varlibdockercontainers

          mountPath: /var/lib/docker/containers

          readOnly: true

  volumes:

    - name: varlog

      hostPath:

        path: /var/log

    - name: varlibdockercontainers

      hostPath:

        path: /var/lib/docker/containers
```

## Health Checks[​](#health-checks "Direct link to Health Checks")

### Basic Health Checks[​](#basic-health-checks "Direct link to Basic Health Checks")

```
main:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 5

    periodSeconds: 5

    timeoutSeconds: 3

    failureThreshold: 3
```

### Advanced Health Checks[​](#advanced-health-checks "Direct link to Advanced Health Checks")

```
main:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

      httpHeaders:

        - name: X-Custom-Header

          value: health-check

    initialDelaySeconds: 60

    periodSeconds: 30

    timeoutSeconds: 10

    failureThreshold: 3

    successThreshold: 1



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 10

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3

    successThreshold: 1



  startupProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 30
```

### Queue Mode Health Checks[​](#queue-mode-health-checks "Direct link to Queue Mode Health Checks")

```
worker:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 5

    periodSeconds: 5

    timeoutSeconds: 3

    failureThreshold: 3



  startupProbe:

    exec:

      command: ["/bin/sh", "-c", "ps aux | grep '[n]8n'"]

    initialDelaySeconds: 10

    periodSeconds: 5

    failureThreshold: 30



webhook:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 5

    periodSeconds: 5

    timeoutSeconds: 3

    failureThreshold: 3
```

## Persistence Monitoring[​](#persistence-monitoring "Direct link to Persistence Monitoring")

info

**Persistence Monitoring:** Monitor persistent volumes, PVC status, and storage usage for each node type independently. Persistence monitoring is separate from hostAliases monitoring.

### Volume Health Checks[​](#volume-health-checks "Direct link to Volume Health Checks")

```
# Monitor PVC status and binding

apiVersion: monitoring.coreos.com/v1

kind: PrometheusRule

metadata:

  name: n8n-persistence-alerts

  namespace: monitoring

  labels:

    release: prometheus

spec:

  groups:

    - name: n8n-persistence

      rules:

        - alert: N8NPVCNotBound

          expr: kube_persistentvolumeclaim_status_phase{namespace="n8n"} != 1

          for: 5m

          labels:

            severity: critical

          annotations:

            summary: "n8n PVC not bound"

            description: "PersistentVolumeClaim {{ $labels.persistentvolumeclaim }} is not bound"



        - alert: N8NVolumeFull

          expr: kubelet_volume_stats_used_bytes / kubelet_volume_stats_capacity_bytes > 0.85

          for: 5m

          labels:

            severity: warning

          annotations:

            summary: "n8n volume nearly full"

            description: "Volume {{ $labels.persistentvolumeclaim }} is {{ $value | humanizePercentage }} full"
```

## StatefulSet vs Deployment Monitoring[​](#statefulset-vs-deployment-monitoring "Direct link to StatefulSet vs Deployment Monitoring")

#### Workload Type Monitoring[​](#workload-type-monitoring "Direct link to Workload Type Monitoring")

```
# Monitor workload type selection

apiVersion: monitoring.coreos.com/v1

kind: PrometheusRule

metadata:

  name: n8n-workload-alerts

  namespace: monitoring

  labels:

    release: prometheus

spec:

  groups:

    - name: n8n-workload

      rules:

        - alert: N8NUnexpectedWorkloadType

          expr: |

            (

              kube_statefulset_status_replicas_ready{namespace="n8n"} > 0

              and

              kube_deployment_status_replicas_ready{namespace="n8n"} > 0

            )

          for: 1m

          labels:

            severity: warning

          annotations:

            summary: "Unexpected workload type detected"

            description: "Both StatefulSet and Deployment are running for n8n"
```

### Persistence Configuration Monitoring[​](#persistence-configuration-monitoring "Direct link to Persistence Configuration Monitoring")

#### Access Mode Validation[​](#access-mode-validation "Direct link to Access Mode Validation")

```
# Monitor persistence access modes

apiVersion: monitoring.coreos.com/v1

kind: PrometheusRule

metadata:

  name: n8n-persistence-config-alerts

  namespace: monitoring

  labels:

    release: prometheus

spec:

  groups:

    - name: n8n-persistence-config

      rules:

        - alert: N8NInvalidAccessMode

          expr: |

            (

              kube_persistentvolumeclaim_access_mode{namespace="n8n", access_mode="ReadWriteOnce"}

              and

              kube_horizontalpodautoscaler_status_current_replicas{namespace="n8n"} > 1

            )

          for: 5m

          labels:

            severity: warning

          annotations:

            summary: "Invalid persistence access mode for autoscaling"

            description: "ReadWriteOnce persistence with autoscaling may cause issues"
```

### Storage Class Monitoring[​](#storage-class-monitoring "Direct link to Storage Class Monitoring")

#### Storage Class Availability[​](#storage-class-availability "Direct link to Storage Class Availability")

```
# Monitor storage class availability

apiVersion: monitoring.coreos.com/v1

kind: PrometheusRule

metadata:

  name: n8n-storage-class-alerts

  namespace: monitoring

  labels:

    release: prometheus

spec:

  groups:

    - name: n8n-storage-class

      rules:

        - alert: N8NStorageClassNotFound

          expr: |

            (

              kube_persistentvolumeclaim_info{namespace="n8n"}

              and

              kube_storageclass_info == 0

            )

          for: 5m

          labels:

            severity: critical

          annotations:

            summary: "Storage class not found"

            description: "Storage class for n8n PVC is not available"
```

### Volume Permission Monitoring[​](#volume-permission-monitoring "Direct link to Volume Permission Monitoring")

#### Permission Health Checks[​](#permission-health-checks "Direct link to Permission Health Checks")

```
# Monitor volume permissions

main:

  extraContainers:

    - name: permission-monitor

      image: busybox:1.35

      command:

        - /bin/sh

        - -c

        - |

          while true; do

            if [ ! -w /home/node/.n8n ]; then

              echo "Volume not writable"

              exit 1

            fi

            if [ "$(stat -c %u /home/node/.n8n)" != "1000" ]; then

              echo "Wrong ownership"

              exit 1

            fi

            sleep 60

          done

      volumeMounts:

        - name: n8n-data

          mountPath: /home/node/.n8n
```

### Monitoring Best Practices[​](#monitoring-best-practices "Direct link to Monitoring Best Practices")

#### Comprehensive Monitoring Setup[​](#comprehensive-monitoring-setup "Direct link to Comprehensive Monitoring Setup")

```
# Complete monitoring configuration

serviceMonitor:

  enabled: true

  include:

    defaultMetrics: true

    cacheMetrics: true

    queueMetrics: true

  interval: 15s

  timeout: 5s



# Persistence monitoring

main:

  extraContainers:

    - name: volume-monitor

      image: busybox:1.35

      command:

        - /bin/sh

        - -c

        - |

          while true; do

            # Check volume space

            df -h /home/node/.n8n

            # Check permissions

            ls -la /home/node/.n8n

            # Check host aliases

            cat /etc/hosts | grep -E "(internal-api|database|redis)"

            sleep 300

          done

      volumeMounts:

        - name: n8n-data

          mountPath: /home/node/.n8n
```

tip

**Monitoring Strategy:** Combine Kubernetes-native monitoring with custom health checks to ensure comprehensive coverage of persistence features.

warning

**Resource Overhead:** Custom monitoring containers add resource overhead. Monitor their impact and adjust resource limits accordingly.

## Alerting Rules[​](#alerting-rules "Direct link to Alerting Rules")

### Basic Alerting Rules[​](#basic-alerting-rules "Direct link to Basic Alerting Rules")

```
apiVersion: monitoring.coreos.com/v1

kind: PrometheusRule

metadata:

  name: n8n-alerts

  namespace: monitoring

  labels:

    release: prometheus

spec:

  groups:

    - name: n8n

      rules:

        - alert: N8NHighErrorRate

          expr: rate(n8n_execution_failed_total[5m]) > 0.1

          for: 2m

          labels:

            severity: warning

          annotations:

            summary: "High n8n execution error rate"

            description: "n8n is experiencing a high error rate of {{ $value }} errors per second"



        - alert: N8NHighExecutionTime

          expr: histogram_quantile(0.95, rate(n8n_execution_duration_seconds_bucket[5m])) > 300

          for: 5m

          labels:

            severity: warning

          annotations:

            summary: "High n8n execution time"

            description: "95th percentile execution time is {{ $value }} seconds"



        - alert: N8NQueueDepth

          expr: n8n_queue_bull_queue_waiting > 100

          for: 2m

          labels:

            severity: warning

          annotations:

            summary: "High n8n queue depth"

            description: "Queue depth is {{ $value }} jobs"
```

### Advanced Alerting Rules[​](#advanced-alerting-rules "Direct link to Advanced Alerting Rules")

```
apiVersion: monitoring.coreos.com/v1

kind: PrometheusRule

metadata:

  name: n8n-advanced-alerts

  namespace: monitoring

  labels:

    release: prometheus

spec:

  groups:

    - name: n8n.advanced

      rules:

        - alert: N8NLowSuccessRate

          expr: (

            rate(n8n_execution_total[5m]) - rate(n8n_execution_failed_total[5m])

          ) / rate(n8n_execution_total[5m]) < 0.95

          for: 5m

          labels:

            severity: critical

          annotations:

            summary: "Low n8n success rate"

            description: "Success rate is {{ $value | humanizePercentage }}"



        - alert: N8NHighMemoryUsage

          expr: (container_memory_usage_bytes{container="n8n"} / container_spec_memory_limit_bytes{container="n8n"}) > 0.8

          for: 5m

          labels:

            severity: warning

          annotations:

            summary: "High n8n memory usage"

            description: "Memory usage is {{ $value | humanizePercentage }}"



        - alert: N8NHighCPUUsage

          expr: rate(container_cpu_usage_seconds_total{container="n8n"}[5m]) > 0.8

          for: 5m

          labels:

            severity: warning

          annotations:

            summary: "High n8n CPU usage"

            description: "CPU usage is {{ $value | humanizePercentage }}"



        - alert: N8NQueueStuck

          expr: n8n_queue_bull_queue_active > 0 and rate(n8n_queue_bull_queue_completed[5m]) == 0

          for: 10m

          labels:

            severity: critical

          annotations:

            summary: "n8n queue appears stuck"

            description: "Active jobs: {{ $value }}, no completions in 5m"



        - alert: N8NHighAPILatency

          expr: histogram_quantile(0.95, rate(n8n_api_request_duration_seconds_bucket[5m])) > 5

          for: 5m

          labels:

            severity: warning

          annotations:

            summary: "High n8n API latency"

            description: "95th percentile API latency is {{ $value }} seconds"
```

## Grafana Dashboards[​](#grafana-dashboards "Direct link to Grafana Dashboards")

info

**Dashboard Templates:** These dashboard examples are based on actual n8n metrics and can be imported directly into Grafana. Customize them based on your specific monitoring needs.

### Comprehensive n8n Dashboard[​](#comprehensive-n8n-dashboard "Direct link to Comprehensive n8n Dashboard")

Grafana dashboard json file

```
{

  "annotations": {

    "list": [

      {

        "builtIn": 1,

        "datasource": "-- Grafana --",

        "enable": true,

        "hide": true,

        "iconColor": "rgba(0, 211, 255, 1)",

        "name": "Annotations & Alerts",

        "target": {

          "limit": 100,

          "matchAny": false,

          "tags": [],

          "type": "dashboard"

        },

        "type": "dashboard"

      }

    ]

  },

  "description": "n8n prometheus client basic metrics",

  "editable": true,

  "fiscalYearStartMonth": 0,

  "gnetId": 11159,

  "graphTooltip": 0,

  "iteration": 1750529070188,

  "links": [],

  "liveNow": false,

  "panels": [

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 7,

        "w": 9,

        "x": 0,

        "y": 0

      },

      "hiddenSeries": false,

      "id": 6,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "paceLength": 10,

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 2,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "exemplar": true,

          "expr": "irate(n8n_process_cpu_user_seconds_total{instance=~\"$instance\"}[2m]) * 100",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "User CPU - {{instance}}",

          "refId": "A"

        },

        {

          "exemplar": true,

          "expr": "irate(n8n_process_cpu_system_seconds_total{instance=~\"$instance\"}[2m]) * 100",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Sys CPU - {{instance}}",

          "refId": "B"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Process CPU Usage",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "percent",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 7,

        "w": 8,

        "x": 9,

        "y": 0

      },

      "hiddenSeries": false,

      "id": 8,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "paceLength": 10,

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 2,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "exemplar": true,

          "expr": "n8n_nodejs_eventloop_lag_seconds{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{role}}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Event Loop Lag",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "s",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "datasource": "prometheus",

      "fieldConfig": {

        "defaults": {

          "color": {

            "mode": "thresholds"

          },

          "decimals": 0,

          "mappings": [],

          "noValue": "0",

          "thresholds": {

            "mode": "absolute",

            "steps": [

              {

                "color": "green",

                "value": null

              },

              {

                "color": "red",

                "value": 80

              }

            ]

          },

          "unit": "none"

        },

        "overrides": []

      },

      "gridPos": {

        "h": 7,

        "w": 3,

        "x": 17,

        "y": 0

      },

      "id": 14,

      "options": {

        "colorMode": "value",

        "graphMode": "none",

        "justifyMode": "auto",

        "orientation": "auto",

        "reduceOptions": {

          "calcs": [

            "last"

          ],

          "fields": "",

          "values": false

        },

        "text": {},

        "textMode": "value"

      },

      "pluginVersion": "8.2.7",

      "targets": [

        {

          "exemplar": true,

          "expr": "sum(increase(n8n_scaling_mode_queue_jobs_completed[1w]))",

          "interval": "",

          "legendFormat": "",

          "refId": "A"

        }

      ],

      "title": "Last Week Completed Jobs",

      "type": "stat"

    },

    {

      "cacheTimeout": null,

      "datasource": "prometheus",

      "fieldConfig": {

        "defaults": {

          "color": {

            "mode": "thresholds"

          },

          "mappings": [

            {

              "options": {

                "match": "null",

                "result": {

                  "text": "N/A"

                }

              },

              "type": "special"

            }

          ],

          "thresholds": {

            "mode": "absolute",

            "steps": [

              {

                "color": "green",

                "value": null

              },

              {

                "color": "red",

                "value": 80

              }

            ]

          },

          "unit": "none"

        },

        "overrides": []

      },

      "gridPos": {

        "h": 3,

        "w": 4,

        "x": 20,

        "y": 0

      },

      "id": 2,

      "interval": "",

      "links": [],

      "maxDataPoints": 100,

      "options": {

        "colorMode": "none",

        "graphMode": "none",

        "justifyMode": "auto",

        "orientation": "horizontal",

        "reduceOptions": {

          "calcs": [

            "lastNotNull"

          ],

          "fields": "",

          "values": false

        },

        "text": {},

        "textMode": "name"

      },

      "pluginVersion": "8.2.7",

      "targets": [

        {

          "exemplar": true,

          "expr": "sum(n8n_nodejs_version_info{instance=~\"$instance\"}) by (version)",

          "format": "time_series",

          "instant": false,

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{version}}",

          "refId": "A"

        }

      ],

      "timeFrom": null,

      "timeShift": null,

      "title": "Node.js Version",

      "type": "stat"

    },

    {

      "cacheTimeout": null,

      "datasource": "prometheus",

      "fieldConfig": {

        "defaults": {

          "color": {

            "fixedColor": "#F2495C",

            "mode": "fixed"

          },

          "mappings": [

            {

              "options": {

                "match": "null",

                "result": {

                  "text": "N/A"

                }

              },

              "type": "special"

            }

          ],

          "thresholds": {

            "mode": "absolute",

            "steps": [

              {

                "color": "green",

                "value": null

              },

              {

                "color": "red",

                "value": 80

              }

            ]

          },

          "unit": "none"

        },

        "overrides": []

      },

      "gridPos": {

        "h": 4,

        "w": 4,

        "x": 20,

        "y": 3

      },

      "id": 4,

      "interval": null,

      "links": [],

      "maxDataPoints": 100,

      "options": {

        "colorMode": "none",

        "graphMode": "none",

        "justifyMode": "auto",

        "orientation": "horizontal",

        "reduceOptions": {

          "calcs": [

            "lastNotNull"

          ],

          "fields": "",

          "values": false

        },

        "text": {},

        "textMode": "name"

      },

      "pluginVersion": "8.2.7",

      "targets": [

        {

          "exemplar": true,

          "expr": "sum(n8n_version_info{instance=~\"$instance\"}) by (version)",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "{{version}}",

          "refId": "A"

        }

      ],

      "timeFrom": null,

      "timeShift": null,

      "title": "n8n version",

      "type": "stat"

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 7,

        "w": 16,

        "x": 0,

        "y": 7

      },

      "hiddenSeries": false,

      "id": 7,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "rightSide": true,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "paceLength": 10,

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 2,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "exemplar": true,

          "expr": "n8n_process_resident_memory_bytes{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Process Memory - {{role}}",

          "refId": "A"

        },

        {

          "exemplar": true,

          "expr": "n8n_nodejs_heap_size_total_bytes{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Heap Total - {{role}}",

          "refId": "B"

        },

        {

          "exemplar": true,

          "expr": "n8n_nodejs_heap_size_used_bytes{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Heap Used - {{role}}",

          "refId": "C"

        },

        {

          "exemplar": true,

          "expr": "n8n_nodejs_external_memory_bytes{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "External Memory - {{role}}",

          "refId": "D"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Process Memory Usage",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "bytes",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 7,

        "w": 8,

        "x": 16,

        "y": 7

      },

      "hiddenSeries": false,

      "id": 9,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "paceLength": 10,

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 2,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "exemplar": true,

          "expr": "n8n_nodejs_active_handles_total{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Active Handler - {{role}}",

          "refId": "A"

        },

        {

          "exemplar": true,

          "expr": "n8n_nodejs_active_requests_total{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Active Request - {{role}}",

          "refId": "B"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Active Handlers/Requests Total",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 8,

        "w": 8,

        "x": 0,

        "y": 14

      },

      "hiddenSeries": false,

      "id": 10,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "rightSide": false,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "paceLength": 10,

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 2,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "exemplar": true,

          "expr": "n8n_nodejs_heap_space_size_total_bytes{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Heap Total - {{role}} - {{space}}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Heap Total Detail",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "bytes",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 8,

        "w": 8,

        "x": 8,

        "y": 14

      },

      "hiddenSeries": false,

      "id": 11,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "rightSide": false,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "paceLength": 10,

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 2,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "exemplar": true,

          "expr": "n8n_nodejs_heap_space_size_used_bytes{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Heap Used - {{role}} - {{space}}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Heap Used Detail",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "bytes",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    },

    {

      "aliasColors": {},

      "bars": false,

      "dashLength": 10,

      "dashes": false,

      "datasource": "prometheus",

      "fill": 1,

      "fillGradient": 0,

      "gridPos": {

        "h": 8,

        "w": 8,

        "x": 16,

        "y": 14

      },

      "hiddenSeries": false,

      "id": 12,

      "legend": {

        "alignAsTable": true,

        "avg": true,

        "current": true,

        "max": true,

        "min": true,

        "rightSide": false,

        "show": true,

        "total": false,

        "values": true

      },

      "lines": true,

      "linewidth": 1,

      "links": [],

      "nullPointMode": "null",

      "options": {

        "alertThreshold": true

      },

      "paceLength": 10,

      "percentage": false,

      "pluginVersion": "8.2.7",

      "pointradius": 2,

      "points": false,

      "renderer": "flot",

      "seriesOverrides": [],

      "spaceLength": 10,

      "stack": false,

      "steppedLine": false,

      "targets": [

        {

          "exemplar": true,

          "expr": "n8n_nodejs_heap_space_size_available_bytes{instance=~\"$instance\"}",

          "format": "time_series",

          "interval": "",

          "intervalFactor": 1,

          "legendFormat": "Heap Used - {{role}} - {{space}}",

          "refId": "A"

        }

      ],

      "thresholds": [],

      "timeFrom": null,

      "timeRegions": [],

      "timeShift": null,

      "title": "Heap Available Detail",

      "tooltip": {

        "shared": true,

        "sort": 0,

        "value_type": "individual"

      },

      "type": "graph",

      "xaxis": {

        "buckets": null,

        "mode": "time",

        "name": null,

        "show": true,

        "values": []

      },

      "yaxes": [

        {

          "format": "bytes",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        },

        {

          "format": "short",

          "label": null,

          "logBase": 1,

          "max": null,

          "min": null,

          "show": true

        }

      ],

      "yaxis": {

        "align": false,

        "alignLevel": null

      }

    }

  ],

  "refresh": "30s",

  "schemaVersion": 32,

  "style": "dark",

  "tags": [

    "n8n"

  ],

  "templating": {

    "list": [

      {

        "allValue": null,

        "current": {

          "selected": true,

          "text": [

            "All"

          ],

          "value": [

            "$__all"

          ]

        },

        "datasource": "prometheus",

        "definition": "label_values(n8n_nodejs_version_info, instance)",

        "description": null,

        "error": null,

        "hide": 0,

        "includeAll": true,

        "label": "instance",

        "multi": true,

        "name": "instance",

        "options": [],

        "query": {

          "query": "label_values(n8n_nodejs_version_info, instance)",

          "refId": "StandardVariableQuery"

        },

        "refresh": 1,

        "regex": "",

        "skipUrlSync": false,

        "sort": 1,

        "tagValuesQuery": "",

        "tagsQuery": "",

        "type": "query",

        "useTags": false

      }

    ]

  },

  "time": {

    "from": "now-1h",

    "to": "now"

  },

  "timepicker": {

    "refresh_intervals": [

      "5s",

      "10s",

      "30s",

      "1m",

      "5m",

      "15m",

      "30m",

      "1h",

      "2h",

      "1d"

    ],

    "time_options": [

      "5m",

      "15m",

      "1h",

      "6h",

      "12h",

      "24h",

      "2d",

      "7d",

      "30d"

    ]

  },

  "timezone": "browser",

  "title": "N8N Application Dashboard",

  "uid": "PTSqcpJWk",

  "version": 1

}
```

### Enhanced Prometheus Queries[​](#enhanced-prometheus-queries "Direct link to Enhanced Prometheus Queries")

tip

**Query Optimization:** These queries are optimized for production use and include proper rate calculations and aggregations.

#### System Performance Queries[​](#system-performance-queries "Direct link to System Performance Queries")

```
# CPU Usage (per instance)

irate(n8n_process_cpu_user_seconds_total{instance=~"$instance"}[2m]) * 100



# Memory Usage (per instance)

n8n_process_resident_memory_bytes{instance=~"$instance"}



# Event Loop Lag (critical for performance)

n8n_nodejs_eventloop_lag_seconds{instance=~"$instance"}



# Active Handles and Requests

n8n_nodejs_active_handles_total{instance=~"$instance"}

n8n_nodejs_active_requests_total{instance=~"$instance"}
```

#### Workflow Execution Queries[​](#workflow-execution-queries "Direct link to Workflow Execution Queries")

```
# Execution Rate (per instance)

rate(n8n_execution_total{instance=~"$instance"}[5m])



# Success Rate (per instance)

(

  rate(n8n_execution_total{instance=~"$instance"}[5m]) -

  rate(n8n_execution_failed_total{instance=~"$instance"}[5m])

) / rate(n8n_execution_total{instance=~"$instance"}[5m]) * 100



# Execution Duration Percentiles

histogram_quantile(0.50, rate(n8n_execution_duration_seconds_bucket{instance=~"$instance"}[5m]))

histogram_quantile(0.95, rate(n8n_execution_duration_seconds_bucket{instance=~"$instance"}[5m]))

histogram_quantile(0.99, rate(n8n_execution_duration_seconds_bucket{instance=~"$instance"}[5m]))



# Error Rate

rate(n8n_execution_failed_total{instance=~"$instance"}[5m])
```

#### Queue Mode Queries[​](#queue-mode-queries "Direct link to Queue Mode Queries")

```
# Queue Depth by Status

n8n_queue_bull_queue_waiting{instance=~"$instance"}

n8n_queue_bull_queue_active{instance=~"$instance"}

n8n_queue_bull_queue_delayed{instance=~"$instance"}



# Queue Processing Rate

rate(n8n_queue_bull_queue_completed{instance=~"$instance"}[5m])

rate(n8n_queue_bull_queue_failed{instance=~"$instance"}[5m])



# Worker Utilization

n8n_queue_bull_queue_active{role="worker"} /

(n8n_queue_bull_queue_waiting{role="worker"} + n8n_queue_bull_queue_active{role="worker"}) * 100



# Queue Stuck Detection

n8n_queue_bull_queue_active{instance=~"$instance"} > 0 and

rate(n8n_queue_bull_queue_completed{instance=~"$instance"}[5m]) == 0
```

#### API Performance Queries[​](#api-performance-queries "Direct link to API Performance Queries")

```
# API Request Rate

rate(n8n_api_requests_total{instance=~"$instance"}[5m])



# API Response Time Percentiles

histogram_quantile(0.50, rate(n8n_api_request_duration_seconds_bucket{instance=~"$instance"}[5m]))

histogram_quantile(0.95, rate(n8n_api_request_duration_seconds_bucket{instance=~"$instance"}[5m]))



# API Error Rate

rate(n8n_api_requests_failed_total{instance=~"$instance"}[5m])
```

#### Memory and Heap Queries[​](#memory-and-heap-queries "Direct link to Memory and Heap Queries")

```
# Heap Memory Usage

n8n_nodejs_heap_size_used_bytes{instance=~"$instance"}

n8n_nodejs_heap_size_total_bytes{instance=~"$instance"}



# Heap Space Details

n8n_nodejs_heap_space_size_used_bytes{instance=~"$instance"}

n8n_nodejs_heap_space_size_available_bytes{instance=~"$instance"}



# External Memory

n8n_nodejs_external_memory_bytes{instance=~"$instance"}
```

#### Advanced Analytics Queries[​](#advanced-analytics-queries "Direct link to Advanced Analytics Queries")

```
# Execution Trends (hourly)

increase(n8n_execution_total{instance=~"$instance"}[1h])



# Success Rate Trends (hourly)

(

  increase(n8n_execution_total{instance=~"$instance"}[1h]) -

  increase(n8n_execution_failed_total{instance=~"$instance"}[1h])

) / increase(n8n_execution_total{instance=~"$instance"}[1h]) * 100



# Queue Processing Efficiency

rate(n8n_queue_bull_queue_completed{instance=~"$instance"}[5m]) /

(n8n_queue_bull_queue_waiting{instance=~"$instance"} + n8n_queue_bull_queue_active{instance=~"$instance"})



# Resource Utilization Score

(

  irate(n8n_process_cpu_user_seconds_total{instance=~"$instance"}[2m]) * 100 +

  (n8n_process_resident_memory_bytes{instance=~"$instance"} /

   n8n_nodejs_heap_size_total_bytes{instance=~"$instance"}) * 100

) / 2
```

warning

**Query Performance:** Use appropriate time ranges and consider using recording rules for complex queries that are frequently executed.

## Sentry Integration[​](#sentry-integration "Direct link to Sentry Integration")

### Basic Sentry Setup[​](#basic-sentry-setup "Direct link to Basic Sentry Setup")

```
sentry:

  enabled: true

  backendDsn: "https://your-sentry-dsn@sentry.io/project"

  frontendDsn: "https://your-sentry-dsn@sentry.io/project"
```

### Advanced Sentry Configuration[​](#advanced-sentry-configuration "Direct link to Advanced Sentry Configuration")

```
sentry:

  enabled: true

  backendDsn: "https://your-sentry-dsn@sentry.io/project"

  frontendDsn: "https://your-sentry-dsn@sentry.io/project"

  externalTaskRunnersDsn: "https://your-sentry-dsn@sentry.io/project"
```

## Database Monitoring[​](#database-monitoring "Direct link to Database Monitoring")

### PostgreSQL Monitoring[​](#postgresql-monitoring "Direct link to PostgreSQL Monitoring")

```
# Enable PostgreSQL metrics

postgresql:

  enabled: true

  metrics:

    enabled: true

    serviceMonitor:

      enabled: true

      interval: 30s

      labels:

        release: prometheus
```

### Redis Monitoring (Queue Mode)[​](#redis-monitoring-queue-mode "Direct link to Redis Monitoring (Queue Mode)")

```
# Enable Redis metrics

redis:

  enabled: true

  metrics:

    enabled: true

    serviceMonitor:

      enabled: true

      interval: 30s

      labels:

        release: prometheus
```

## Storage Monitoring[​](#storage-monitoring "Direct link to Storage Monitoring")

### Filesystem Storage Monitoring[​](#filesystem-storage-monitoring "Direct link to Filesystem Storage Monitoring")

```
# Monitor filesystem usage

main:

  extraContainers:

    - name: storage-monitor

      image: busybox

      command:

        - /bin/sh

        - -c

        - |

          while true; do

            df -h /data | tail -1 | awk '{print $5}' | sed 's/%//' > /tmp/disk-usage

            sleep 60

          done

      volumeMounts:

        - name: n8n-binary-data

          mountPath: /data
```

## Pod Affinity and Anti-Affinity[​](#pod-affinity-and-anti-affinity "Direct link to Pod Affinity and Anti-Affinity")

tip

**Monitoring Affinity:** Proper affinity configuration can improve monitoring performance and reliability by ensuring pods are distributed optimally across your cluster.

warning

**Deprecation Notice:** The top-level `affinity` field is deprecated. Use the specific affinity configurations under `main`, `worker`, and `webhook` blocks instead.

### Affinity for Monitoring Optimization[​](#affinity-for-monitoring-optimization "Direct link to Affinity for Monitoring Optimization")

#### Spread Monitoring Pods[​](#spread-monitoring-pods "Direct link to Spread Monitoring Pods")

```
# Spread pods to avoid monitoring bottlenecks

main:

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: kubernetes.io/hostname



worker:

  mode: queue

  affinity:

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - n8n

          - key: app.kubernetes.io/component

            operator: In

            values:

            - worker

        topologyKey: kubernetes.io/hostname
```

#### Zone Distribution for High Availability[​](#zone-distribution-for-high-availability "Direct link to Zone Distribution for High Availability")

```
# Distribute pods across availability zones for monitoring resilience

main:

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

          topologyKey: topology.kubernetes.io/zone



webhook:

  mode: queue

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

              - n8n

            - key: app.kubernetes.io/component

              operator: In

              values:

              - webhook

          topologyKey: topology.kubernetes.io/zone
```

#### Node Affinity for Monitoring Nodes[​](#node-affinity-for-monitoring-nodes "Direct link to Node Affinity for Monitoring Nodes")

```
# Place pods on nodes with monitoring capabilities

main:

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: monitoring-enabled

            operator: In

            values:

            - "true"



worker:

  mode: queue

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: monitoring-enabled

            operator: In

            values:

            - "true"
```

info

**Monitoring Benefits:** Proper affinity configuration ensures that monitoring data collection is distributed across your cluster, preventing bottlenecks and improving overall monitoring performance.

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Monitoring Issues[​](#common-monitoring-issues "Direct link to Common Monitoring Issues")

#### ServiceMonitor Not Scraping[​](#servicemonitor-not-scraping "Direct link to ServiceMonitor Not Scraping")

```
# Check ServiceMonitor status

kubectl get servicemonitor -n monitoring



# Check Prometheus targets

kubectl port-forward svc/prometheus-operated 9090:9090 -n monitoring



# Check n8n metrics endpoint

kubectl exec -it <n8n-pod> -- curl -s http://localhost:5678/metrics
```

#### High Memory Usage[​](#high-memory-usage "Direct link to High Memory Usage")

```
# Check memory usage

kubectl top pods -l app.kubernetes.io/name=n8n



# Check memory limits

kubectl describe pod <n8n-pod>



# Check for memory leaks

kubectl logs <n8n-pod> | grep -i memory
```

#### High CPU Usage[​](#high-cpu-usage "Direct link to High CPU Usage")

```
# Check CPU usage

kubectl top pods -l app.kubernetes.io/name=n8n



# Check for CPU-intensive operations

kubectl logs <n8n-pod> | grep -i cpu



# Check execution metrics

kubectl exec -it <n8n-pod> -- curl -s http://localhost:5678/metrics | grep execution
```

### Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

#### Metrics Collection Optimization[​](#metrics-collection-optimization "Direct link to Metrics Collection Optimization")

```
serviceMonitor:

  enabled: true

  interval: 60s  # Increase interval for high-volume deployments

  timeout: 30s

  include:

    defaultMetrics: true

    cacheMetrics: false  # Disable if not needed

    messageEventBusMetrics: false

    queueMetrics: true
```

#### Logging Optimization[​](#logging-optimization "Direct link to Logging Optimization")

```
log:

  level: warn  # Reduce log level in production

  output:

    - console

  scopes:

    - redis

    - scaling

  file:

    maxsize: 32  # Increase file size

    maxcount: "50"  # Reduce file count
```

## Best Practices[​](#best-practices "Direct link to Best Practices")

### Monitoring Strategy[​](#monitoring-strategy "Direct link to Monitoring Strategy")

* Start with basic metrics and expand gradually
* Use appropriate alert thresholds
* Monitor both application and infrastructure metrics
* Set up dashboards for different user roles
* Regular review and tuning of alerts

### Performance[​](#performance "Direct link to Performance")

* Use appropriate scrape intervals
* Filter metrics to reduce cardinality
* Optimize Prometheus queries
* Use recording rules for complex queries
* Monitor monitoring system performance

### Reliability[​](#reliability "Direct link to Reliability")

* Set up monitoring for the monitoring system
* Use multiple alerting channels
* Test alerting rules regularly
* Document alert procedures
* Set up escalation policies

### Security[​](#security "Direct link to Security")

* Secure Prometheus endpoints
* Use RBAC for monitoring access
* Encrypt sensitive metrics
* Audit monitoring access
* Regular security updates

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Usage Guide](/docs/charts/n8n/usage.md) - Quick start and basic deployment
* [Configuration Guide](/docs/charts/n8n/configuration.md) - Detailed configuration options
* [Database Setup](/docs/charts/n8n/database-setup.md) - PostgreSQL and external database configuration
* [Queue Mode Setup](/docs/charts/n8n/queue-mode.md) - Distributed execution with Redis
* [Storage Configuration](/docs/charts/n8n/storage.md) - Binary data storage options
* [Troubleshooting](/docs/charts/n8n/troubleshooting.md) - Common issues and solutions


---

# n8n Queue Mode Setup

Queue mode enables distributed execution in n8n by separating the main node (UI/API) from worker nodes (execution) and webhook nodes (webhook processing). This architecture provides better scalability, reliability, and performance for production workloads.

tip

**Production Architecture:** Queue mode is the recommended architecture for production deployments. It provides better scalability, reliability, and performance compared to single-node deployments.

## Architecture Overview[​](#architecture-overview "Direct link to Architecture Overview")

info

**Distributed Execution:** Queue mode separates concerns by dedicating specific nodes to different tasks, improving overall system performance and reliability.

### Queue Mode Components[​](#queue-mode-components "Direct link to Queue Mode Components")

<!-- -->

### Component Roles[​](#component-roles "Direct link to Component Roles")

* **Main Node**: Handles UI, API requests, workflow management
* **Worker Nodes**: Execute workflows and process tasks
* **Webhook Nodes**: Process incoming webhook requests
* **Redis**: Message broker for communication between nodes

## Queue Mode Endpoints[​](#queue-mode-endpoints "Direct link to Queue Mode Endpoints")

info

**Enhanced Endpoints:** Queue mode supports additional endpoints for advanced workflow automation and AI integration capabilities.

### MCP (Model Context Protocol) Endpoints[​](#mcp-model-context-protocol-endpoints "Direct link to MCP (Model Context Protocol) Endpoints")

Queue mode includes support for MCP (Model Context Protocol) endpoints, enabling n8n to act as an MCP server for AI model integration:

* **MCP Endpoint**: `https://yourdomain.com/mcp/` - Main MCP server endpoint
* **MCP Test Endpoint**: `https://yourdomain.com/mcp-test/` - Testing endpoint for MCP functionality

tip

**AI Integration:** MCP endpoints allow AI models and assistants to interact with n8n workflows through the Model Context Protocol, enabling advanced AI-powered automation scenarios.

#### MCP Server Trigger Node[​](#mcp-server-trigger-node "Direct link to MCP Server Trigger Node")

The MCP Server Trigger node allows n8n to expose workflows as tools to MCP clients:

* **Server-Sent Events (SSE)**: Supports long-lived connections for real-time communication
* **Streamable HTTP**: Alternative transport method for MCP communication
* **Authentication**: Bearer token and header-based authentication support
* **Tool Integration**: Connect workflows with AI assistants and language models

warning

**MCP Requirements:** MCP endpoints require PostgreSQL database and queue mode configuration. They are not available in single-node deployments with SQLite.

#### MCP Configuration Example[​](#mcp-configuration-example "Direct link to MCP Configuration Example")

```
# Enable MCP endpoints in queue mode

webhook:

  mode: queue

  url: "https://yourdomain.com"

  count: 2

  mcp:

    enabled: true

    # You can add extra env vars, affinity, resources, etc. under webhook.mcp



ingress:

  enabled: true

  hosts:

    - host: yourdomain.com

      paths:

        - path: /

          pathType: Prefix
```

### MCP Client Integration (Claude Desktop, Cursor, etc.)[​](#mcp-client-integration-claude-desktop-cursor-etc "Direct link to MCP Client Integration (Claude Desktop, Cursor, etc.)")

[Supergateway](https://github.com/supercorp-ai/supergateway) runs MCP stdio-based servers over SSE (Server-Sent Events) with one command. Please download your MCP client ([Claude Desktop](https://claude.ai/download), [Cursor](https://cursor.com/downloads), etc.) and apply the following configuration from client settings.

tip

`https://webhook.myhost/mcp/ab123c45-d678-9d0e-fg1a-2345bcd6ef7g` url must be replaced with your `MCP Server Trigger Production URL`.

#### Basic MCP Client Settings[​](#basic-mcp-client-settings "Direct link to Basic MCP Client Settings")

```
{

  "mcpServers": {

    "command": "npx",

    "args": [

      "-y",

      "supergateway",

      "--sse",

      "https://webhook.myhost/mcp/ab123c45-d678-9d0e-fg1a-2345bcd6ef7g"

    ]

  }

}
```

#### With Header Authentication[​](#with-header-authentication "Direct link to With Header Authentication")

```
{

  "mcpServers": {

    "command": "npx",

    "args": [

      "-y",

      "supergateway",

      "--sse",

      "https://webhook.myhost/mcp/ab123c45-d678-9d0e-fg1a-2345bcd6ef7g",

      "--header",

      "mykey:myvalue"

    ]

  }

}
```

* You can set these in Claude Desktop, Cursor, or any compatible MCP client.
* Header authentication is supported for secure access.

info

**Authentication:**

* Use `--header` to pass custom authentication headers (e.g., API keys, tokens).
* You can also use Bearer tokens if your n8n instance is configured for it.

info

**MCP Documentation:** For detailed MCP setup and usage, see the [official n8n MCP documentation](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/).

### Form Endpoints[​](#form-endpoints "Direct link to Form Endpoints")

Queue mode supports dedicated form endpoints for the n8n Form Trigger node:

* **Form Endpoint**: `https://yourdomain.com/form/` - Main form submission endpoint
* **Form Test Endpoint**: `https://yourdomain.com/form-test/` - Testing endpoint for forms
* **Form Waiting Endpoint**: `https://yourdomain.com/form-waiting/` - Endpoint for form waiting workflows

tip

**Form Automation:** Form endpoints enable the creation of interactive forms that can trigger n8n workflows, allowing users to submit data through web forms.

#### Form Trigger Node[​](#form-trigger-node "Direct link to Form Trigger Node")

The Form Trigger node creates web forms that can:

* **Collect User Input**: Gather data through customizable web forms
* **Trigger Workflows**: Automatically start workflows when forms are submitted
* **Data Processing**: Process form submissions and route data to other nodes
* **User Experience**: Provide a user-friendly interface for workflow interaction

#### Form Configuration Example[​](#form-configuration-example "Direct link to Form Configuration Example")

```
# Enable form endpoints in queue mode

webhook:

  mode: queue

  url: "https://yourdomain.com"

  count: 2



ingress:

  enabled: true

  hosts:

    - host: yourdomain.com

      paths:

        - path: /

          pathType: Prefix
```

info

**Form Documentation:** For detailed form setup and usage, see the [official n8n Form Trigger documentation](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.formtrigger/).

### Endpoint Routing[​](#endpoint-routing "Direct link to Endpoint Routing")

In queue mode, different endpoints are routed to appropriate nodes:

* **Main Node**: Handles UI, API, and test endpoints
* **Webhook Nodes**: Process webhook, form, and MCP endpoints
* **Worker Nodes**: Execute workflows triggered by any endpoint

tip

**Load Distribution:** This routing ensures optimal performance by directing traffic to the appropriate node types based on the request type.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**Requirements:** Queue mode requires PostgreSQL and Redis. SQLite is not supported for queue mode deployments.

### Required Components[​](#required-components "Direct link to Required Components")

1. **PostgreSQL Database** (required for queue mode)
2. **Redis Instance** (message broker)
3. **Kubernetes Cluster** with sufficient resources
4. **Storage Class** for persistent volumes

### Resource Requirements[​](#resource-requirements "Direct link to Resource Requirements")

* **Main Node**: 100m CPU, 128Mi memory minimum
* **Worker Nodes**: 500m CPU, 512Mi memory minimum per node
* **Webhook Nodes**: 100m CPU, 128Mi memory minimum per node
* **Redis**: 100m CPU, 128Mi memory minimum

## Basic Queue Mode Setup[​](#basic-queue-mode-setup "Direct link to Basic Queue Mode Setup")

note

**Getting Started:** Start with a basic queue mode setup and scale up as needed based on your workload requirements.

### 1. Enable PostgreSQL[​](#1-enable-postgresql "Direct link to 1. Enable PostgreSQL")

```
db:

  type: postgresdb



postgresql:

  enabled: true

  auth:

    username: n8n

    password: your-secure-password

    database: n8n

  primary:

    persistence:

      enabled: true

      size: 10Gi
```

### 2. Enable Redis[​](#2-enable-redis "Direct link to 2. Enable Redis")

```
redis:

  enabled: true

  architecture: standalone

  master:

    persistence:

      enabled: true

      size: 5Gi
```

### 3. Configure Worker Nodes[​](#3-configure-worker-nodes "Direct link to 3. Configure Worker Nodes")

```
worker:

  mode: queue

  count: 2

  concurrency: 10

  resources:

    requests:

      cpu: 500m

      memory: 512Mi

    limits:

      cpu: 2000m

      memory: 2Gi
```

### 4. Configure Webhook Nodes[​](#4-configure-webhook-nodes "Direct link to 4. Configure Webhook Nodes")

```
webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  count: 2

  resources:

    requests:

      cpu: 100m

      memory: 128Mi

    limits:

      cpu: 512m

      memory: 512Mi
```

### 5. Complete Basic Configuration[​](#5-complete-basic-configuration "Direct link to 5. Complete Basic Configuration")

```
# Basic queue mode setup

db:

  type: postgresdb



postgresql:

  enabled: true

  auth:

    username: n8n

    password: your-secure-password

    database: n8n

  primary:

    persistence:

      enabled: true

      size: 10Gi



redis:

  enabled: true

  architecture: standalone

  master:

    persistence:

      enabled: true

      size: 5Gi



worker:

  mode: queue

  count: 2

  concurrency: 10

  resources:

    requests:

      cpu: 500m

      memory: 512Mi

    limits:

      cpu: 2000m

      memory: 2Gi



webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  count: 2

  resources:

    requests:

      cpu: 100m

      memory: 128Mi

    limits:

      cpu: 512m

      memory: 512Mi



ingress:

  enabled: true

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix
```

## Advanced Queue Mode Configuration[​](#advanced-queue-mode-configuration "Direct link to Advanced Queue Mode Configuration")

tip

**Scaling Strategy:** Use autoscaling for dynamic workloads and manual scaling for predictable, steady-state workloads.

### Autoscaling Workers (HPA)[​](#autoscaling-workers-hpa "Direct link to Autoscaling Workers (HPA)")

Worker nodes execute workflows and process tasks from the Redis queue. Autoscaling worker pods ensures optimal performance during high workflow execution periods while reducing resource costs during low activity.

```
worker:

  mode: queue

  autoscaling:

    enabled: true

    minReplicas: 2

    maxReplicas: 10

    metrics:

      - type: Resource

        resource:

          name: memory

          target:

            type: Utilization

            averageUtilization: 80

      - type: Resource

        resource:

          name: cpu

          target:

            type: Utilization

            averageUtilization: 80

    behavior:

      scaleDown:

        stabilizationWindowSeconds: 300

        policies:

        - type: Percent

          value: 100

          periodSeconds: 15

      scaleUp:

        stabilizationWindowSeconds: 0

        policies:

        - type: Percent

          value: 100

          periodSeconds: 15

        - type: Pods

          value: 4

          periodSeconds: 15

        selectPolicy: Max
```

info

**Worker Autoscaling:** Horizontal Pod Autoscaler (HPA) automatically scales worker pods based on CPU and memory utilization metrics. Workers handle workflow execution, so scaling them ensures optimal performance during high workload periods while reducing costs during low activity. The behavior configuration controls scaling aggressiveness and stabilization periods.

### Autoscaling Webhooks (HPA)[​](#autoscaling-webhooks-hpa "Direct link to Autoscaling Webhooks (HPA)")

Webhook nodes handle incoming webhook requests and form submissions. Autoscaling webhook pods ensures optimal performance during high webhook traffic while reducing resource usage during low activity periods.

```
webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  autoscaling:

    enabled: true

    minReplicas: 2

    maxReplicas: 10

    metrics:

      - type: Resource

        resource:

          name: cpu

          target:

            type: Utilization

            averageUtilization: 80

      - type: Pods

        pods:

          metric:

            name: packets-per-second

          target:

            type: AverageValue

            averageValue: 1k
```

info

**Webhook Autoscaling:** Horizontal Pod Autoscaler (HPA) automatically scales webhook pods based on CPU utilization and network traffic metrics. Webhook nodes are lightweight and handle HTTP requests, making them ideal for autoscaling based on incoming traffic patterns.

### Deploy on All Nodes[​](#deploy-on-all-nodes "Direct link to Deploy on All Nodes")

```
worker:

  mode: queue

  allNodes: true  # Deploy one worker per node

  autoscaling:

    enabled: false  # Disable autoscaling when using allNodes



webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  allNodes: true  # Deploy one webhook per node

  autoscaling:

    enabled: false  # Disable autoscaling when using allNodes
```

## Persistence in Queue Mode[​](#persistence-in-queue-mode "Direct link to Persistence in Queue Mode")

info

**Persistence:** Configure persistent storage for main and worker nodes independently. Persistence is used to store workflows, configuration, and npm packages. Configure independently from hostAliases.

### Main Node Persistence Example[​](#main-node-persistence-example "Direct link to Main Node Persistence Example")

```
main:

  count: 1

  persistence:

    enabled: true

    volumeName: "n8n-main-data"

    mountPath: "/home/node/.n8n"

    size: 8Gi

    accessMode: ReadWriteOnce

    storageClass: "fast-ssd"

    annotations:

      helm.sh/resource-policy: keep
```

### Worker Node Persistence Example[​](#worker-node-persistence-example "Direct link to Worker Node Persistence Example")

```
worker:

  mode: queue

  count: 3

  persistence:

    enabled: true

    volumeName: "n8n-worker-data"

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteOnce
```

warning

**Autoscaling Limitations:** Worker nodes with `ReadWriteOnce` persistence cannot use autoscaling. Use `ReadWriteMany` for autoscaling or `ReadWriteOnce` with StatefulSets for fixed scaling.

### Worker Persistence with Autoscaling[​](#worker-persistence-with-autoscaling "Direct link to Worker Persistence with Autoscaling")

```
worker:

  mode: queue

  autoscaling:

    enabled: true

    minReplicas: 2

    maxReplicas: 10

  persistence:

    enabled: true

    volumeName: "n8n-worker-data"

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteMany  # For autoscaling

    storageClass: "fast-ssd"
```

### Worker Persistence with StatefulSet[​](#worker-persistence-with-statefulset "Direct link to Worker Persistence with StatefulSet")

```
worker:

  mode: queue

  count: 3

  persistence:

    enabled: true

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteOnce
```

info

**Automatic StatefulSet:** When persistence is enabled with `ReadWriteOnce` access mode, the chart automatically deploys worker nodes as StatefulSets. Each pod gets its own persistent volume with a unique name.

## Resource Management[​](#resource-management "Direct link to Resource Management")

### Pod Affinity and Anti-Affinity[​](#pod-affinity-and-anti-affinity "Direct link to Pod Affinity and Anti-Affinity")

tip

**Advanced Scheduling:** Use affinity rules to control pod placement and optimize resource utilization in queue mode deployments.

warning

**Deprecation Notice:** The top-level `affinity` field is deprecated. Use the specific affinity configurations under `main`, `worker`, and `webhook` blocks instead.

#### Spread Worker Pods Across Nodes[​](#spread-worker-pods-across-nodes "Direct link to Spread Worker Pods Across Nodes")

```
worker:

  mode: queue

  count: 3

  affinity:

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchLabels:

            app.kubernetes.io/name: n8n

            app.kubernetes.io/component: worker

        topologyKey: kubernetes.io/hostname
```

#### Spread Webhook Pods Across Zones[​](#spread-webhook-pods-across-zones "Direct link to Spread Webhook Pods Across Zones")

```
webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  count: 2

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchLabels:

              app.kubernetes.io/name: n8n

              app.kubernetes.io/component: webhook

          topologyKey: topology.kubernetes.io/zone
```

#### Co-locate Main and Worker Pods[​](#co-locate-main-and-worker-pods "Direct link to Co-locate Main and Worker Pods")

```
main:

  affinity:

    podAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchLabels:

              app.kubernetes.io/name: n8n

          topologyKey: kubernetes.io/hostname



worker:

  mode: queue

  affinity:

    podAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchLabels:

              app.kubernetes.io/name: n8n

              app.kubernetes.io/component: main

          topologyKey: kubernetes.io/hostname
```

#### Node Affinity for Specific Node Types[​](#node-affinity-for-specific-node-types "Direct link to Node Affinity for Specific Node Types")

```
worker:

  mode: queue

  affinity:

    nodeAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

        nodeSelectorTerms:

        - matchExpressions:

          - key: node-type

            operator: In

            values:

            - compute-optimized

          - key: kubernetes.io/os

            operator: In

            values:

            - linux



webhook:

  mode: queue

  affinity:

    nodeAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 1

        preference:

          matchExpressions:

          - key: node-role.kubernetes.io/worker

            operator: Exists
```

info

**Affinity Benefits:** Proper affinity configuration improves availability, resource utilization, and performance in queue mode deployments.

### External Redis Configuration[​](#external-redis-configuration "Direct link to External Redis Configuration")

```
# Disable built-in Redis

redis:

  enabled: false



# Configure external Redis

externalRedis:

  host: your-redis-host.com

  port: 6379

  username: default

  password: your-redis-password

  existingSecret: redis-secret  # Use Kubernetes secret
```

### High Availability Redis[​](#high-availability-redis "Direct link to High Availability Redis")

```
redis:

  enabled: true

  architecture: replication  # Master-slave replication



  master:

    persistence:

      enabled: true

      size: 10Gi

    resources:

      requests:

        cpu: 100m

        memory: 256Mi

      limits:

        cpu: 500m

        memory: 512Mi



  replica:

    replicaCount: 2

    persistence:

      enabled: true

      size: 10Gi

    resources:

      requests:

        cpu: 100m

        memory: 256Mi

      limits:

        cpu: 500m

        memory: 512Mi
```

## Production Queue Mode Examples[​](#production-queue-mode-examples "Direct link to Production Queue Mode Examples")

### Small Production Setup[​](#small-production-setup "Direct link to Small Production Setup")

```
# Small production (2-5 users)

db:

  type: postgresdb



postgresql:

  enabled: true

  auth:

    username: n8n

    password: your-secure-password

    database: n8n

  primary:

    persistence:

      enabled: true

      size: 20Gi



redis:

  enabled: true

  architecture: standalone

  master:

    persistence:

      enabled: true

      size: 10Gi



worker:

  mode: queue

  count: 3

  concurrency: 10

  resources:

    requests:

      cpu: 500m

      memory: 512Mi

    limits:

      cpu: 2000m

      memory: 2Gi



webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  count: 2

  resources:

    requests:

      cpu: 100m

      memory: 128Mi

    limits:

      cpu: 512m

      memory: 512Mi



ingress:

  enabled: true

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix
```

### Medium Production Setup[​](#medium-production-setup "Direct link to Medium Production Setup")

```
# Medium production (5-20 users)

db:

  type: postgresdb



postgresql:

  enabled: true

  auth:

    username: n8n

    password: your-secure-password

    database: n8n

  primary:

    persistence:

      enabled: true

      size: 50Gi

    resources:

      requests:

        cpu: 500m

        memory: 1Gi

      limits:

        cpu: 2000m

        memory: 4Gi



redis:

  enabled: true

  architecture: replication

  master:

    persistence:

      enabled: true

      size: 20Gi

    resources:

      requests:

        cpu: 200m

        memory: 512Mi

      limits:

        cpu: 1000m

        memory: 1Gi

  replica:

    replicaCount: 2

    persistence:

      enabled: true

      size: 20Gi



worker:

  mode: queue

  autoscaling:

    enabled: true

    minReplicas: 3

    maxReplicas: 15

    metrics:

      - type: Resource

        resource:

          name: memory

          target:

            type: Utilization

            averageUtilization: 80

      - type: Resource

        resource:

          name: cpu

          target:

            type: Utilization

            averageUtilization: 80

  resources:

    requests:

      cpu: 1000m

      memory: 1Gi

    limits:

      cpu: 4000m

      memory: 4Gi



webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  autoscaling:

    enabled: true

    minReplicas: 3

    maxReplicas: 10

  resources:

    requests:

      cpu: 200m

      memory: 256Mi

    limits:

      cpu: 1000m

      memory: 1Gi



ingress:

  enabled: true

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix
```

### Large Production Setup[​](#large-production-setup "Direct link to Large Production Setup")

```
# Large production (20+ users)

db:

  type: postgresdb



externalPostgresql:

  host: your-postgres-host.com

  port: 5432

  username: n8n

  password: your-secure-password

  database: n8n

  existingSecret: postgres-secret



externalRedis:

  host: your-redis-host.com

  port: 6379

  password: your-redis-password

  existingSecret: redis-secret



worker:

  mode: queue

  autoscaling:

    enabled: true

    minReplicas: 5

    maxReplicas: 50

    metrics:

      - type: Resource

        resource:

          name: memory

          target:

            type: Utilization

            averageUtilization: 70

      - type: Resource

        resource:

          name: cpu

          target:

            type: Utilization

            averageUtilization: 70

      - type: Pods

        pods:

          metric:

            name: executions-per-second

          target:

            type: AverageValue

            averageValue: 100

  resources:

    requests:

      cpu: 2000m

      memory: 2Gi

    limits:

      cpu: 8000m

      memory: 8Gi



webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  autoscaling:

    enabled: true

    minReplicas: 5

    maxReplicas: 20

  resources:

    requests:

      cpu: 500m

      memory: 512Mi

    limits:

      cpu: 2000m

      memory: 2Gi



ingress:

  enabled: true

  hosts:

    - host: n8n.yourdomain.com

      paths:

        - path: /

          pathType: Prefix
```

## Monitoring and Observability[​](#monitoring-and-observability "Direct link to Monitoring and Observability")

### ServiceMonitor Configuration[​](#servicemonitor-configuration "Direct link to ServiceMonitor Configuration")

```
serviceMonitor:

  enabled: true

  interval: 30s

  timeout: 10s

  labels:

    release: prometheus

  include:

    defaultMetrics: true

    cacheMetrics: true

    messageEventBusMetrics: true

    queueMetrics: true

    workflowIdLabel: true

    nodeTypeLabel: true
```

### Logging Configuration[​](#logging-configuration "Direct link to Logging Configuration")

```
log:

  level: info

  output:

    - console

  scopes:

    - concurrency

    - pubsub

    - redis

    - scaling

    - waiting-executions
```

### Health Checks[​](#health-checks "Direct link to Health Checks")

```
main:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 5

    periodSeconds: 5

    timeoutSeconds: 3

    failureThreshold: 3



worker:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 5

    periodSeconds: 5

    timeoutSeconds: 3

    failureThreshold: 3



webhook:

  livenessProbe:

    httpGet:

      path: /healthz

      port: http

    initialDelaySeconds: 30

    periodSeconds: 10

    timeoutSeconds: 5

    failureThreshold: 3



  readinessProbe:

    httpGet:

      path: /healthz/readiness

      port: http

    initialDelaySeconds: 5

    periodSeconds: 5

    timeoutSeconds: 3

    failureThreshold: 3
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

#### Redis Connection Issues[​](#redis-connection-issues "Direct link to Redis Connection Issues")

```
# Check Redis pod status

kubectl get pods -l app.kubernetes.io/name=redis



# Check Redis logs

kubectl logs -l app.kubernetes.io/name=redis



# Test Redis connection

kubectl exec -it <redis-pod> -- redis-cli ping
```

#### Worker Node Issues[​](#worker-node-issues "Direct link to Worker Node Issues")

```
# Check worker pod status

kubectl get pods -l app.kubernetes.io/component=worker



# Check worker logs

kubectl logs -l app.kubernetes.io/component=worker



# Check worker metrics

kubectl top pods -l app.kubernetes.io/component=worker
```

#### Webhook Node Issues[​](#webhook-node-issues "Direct link to Webhook Node Issues")

```
# Check webhook pod status

kubectl get pods -l app.kubernetes.io/component=webhook



# Check webhook logs

kubectl logs -l app.kubernetes.io/component=webhook



# Test webhook endpoint

curl -X POST https://webhook.yourdomain.com/webhook-test/18ca0dba-fd0f-415a-abb5-8fb65d10653b/webhook
```

### Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

#### Worker Concurrency Tuning[​](#worker-concurrency-tuning "Direct link to Worker Concurrency Tuning")

```
worker:

  mode: queue

  concurrency: 5  # Start with lower value, increase based on performance

  resources:

    requests:

      cpu: 1000m

      memory: 1Gi

    limits:

      cpu: 4000m

      memory: 4Gi
```

#### Redis Performance[​](#redis-performance "Direct link to Redis Performance")

```
redis:

  enabled: true

  architecture: replication

  master:

    persistence:

      enabled: true

      size: 20Gi

    resources:

      requests:

        cpu: 500m

        memory: 1Gi

      limits:

        cpu: 2000m

        memory: 2Gi

    configuration: |

      maxmemory 1gb

      maxmemory-policy allkeys-lru

      save 900 1

      save 300 10

      save 60 10000
```

#### Database Performance[​](#database-performance "Direct link to Database Performance")

```
db:

  type: postgresdb

  logging:

    enabled: true

    options: error

    maxQueryExecutionTime: 1000



postgresql:

  enabled: true

  primary:

    configuration: |

      shared_buffers = 256MB

      effective_cache_size = 1GB

      maintenance_work_mem = 64MB

      checkpoint_completion_target = 0.9

      wal_buffers = 16MB

      default_statistics_target = 100

      random_page_cost = 1.1

      effective_io_concurrency = 200

      work_mem = 4MB

      min_wal_size = 1GB

      max_wal_size = 4GB
```

## Best Practices[​](#best-practices "Direct link to Best Practices")

### Scaling[​](#scaling "Direct link to Scaling")

* Start with 2-3 worker nodes and scale based on demand
* Use autoscaling for variable workloads
* Monitor CPU and memory usage for scaling decisions
* Consider deploying workers on all nodes for high availability

### Performance[​](#performance "Direct link to Performance")

* Use PostgreSQL for production workloads
* Configure appropriate Redis memory limits
* Monitor queue depths and processing times
* Tune worker concurrency based on workload

### Reliability[​](#reliability "Direct link to Reliability")

* Use Redis replication for high availability
* Configure proper health checks and probes
* Set up monitoring and alerting
* Use persistent storage for databases and Redis

### Security[​](#security "Direct link to Security")

* Use Kubernetes secrets for sensitive data
* Enable network policies to restrict communication
* Use HTTPS for webhook endpoints
* Regularly update Redis and PostgreSQL versions

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Usage Guide](/docs/charts/n8n/usage.md) - Quick start and basic deployment
* [Configuration Guide](/docs/charts/n8n/configuration.md) - Detailed configuration options
* [Database Setup](/docs/charts/n8n/database-setup.md) - PostgreSQL and external database configuration
* [Storage Configuration](/docs/charts/n8n/storage.md) - Binary data storage options
* [Monitoring Setup](/docs/charts/n8n/monitoring.md) - Metrics and observability
* [Troubleshooting](/docs/charts/n8n/troubleshooting.md) - Common issues and solutions


---

# n8n Storage Configuration

n8n stores binary data (files, images, documents) separately from workflow metadata. This guide covers all storage options and their configuration for different deployment scenarios.

info

**Binary Data Storage:** Binary data includes files uploaded through workflows, images, documents, and other binary content. Choose the storage option that best fits your deployment architecture.

## Storage Options Overview[​](#storage-options-overview "Direct link to Storage Options Overview")

### Default Storage (In-Memory)[​](#default-storage-in-memory "Direct link to Default Storage (In-Memory)")

* **Use Case:** Development, testing, small deployments
* **Pros:** Simple setup, no external dependencies
* **Cons:** Data lost on pod restart, limited by memory
* **Storage:** In-memory storage

### Filesystem Storage[​](#filesystem-storage "Direct link to Filesystem Storage")

* **Use Case:** Single-node deployments, local storage
* **Pros:** Persistent data, simple configuration
* **Cons:** Not suitable for multi-node deployments
* **Storage:** Local filesystem with persistent volumes

### S3-Compatible Storage[​](#s3-compatible-storage "Direct link to S3-Compatible Storage")

* **Use Case:** Production, multi-node, cloud deployments
* **Pros:** Scalable, reliable, cloud-native
* **Cons:** Requires external storage service
* **Storage:** Object storage (AWS S3, MinIO, etc.)

warning

**Production Storage:** Default in-memory storage is not suitable for production. Use filesystem storage for single-node deployments or S3-compatible storage for multi-node deployments.

## Default Storage Configuration[​](#default-storage-configuration "Direct link to Default Storage Configuration")

tip

**Development Use:** Default storage is perfect for development and testing environments where data persistence is not critical.

### Basic Default Storage[​](#basic-default-storage "Direct link to Basic Default Storage")

```
binaryData:

  mode: "default"
```

## Filesystem Storage Configuration[​](#filesystem-storage-configuration "Direct link to Filesystem Storage Configuration")

note

**Single Node Only:** Filesystem storage is only suitable for single-node deployments. For queue mode or multi-node setups, use S3-compatible storage.

### Basic Filesystem Storage[​](#basic-filesystem-storage "Direct link to Basic Filesystem Storage")

```
binaryData:

  mode: "filesystem"

  localStoragePath: "/data/n8n"
```

### Filesystem with Persistent Volume[​](#filesystem-with-persistent-volume "Direct link to Filesystem with Persistent Volume")

tip

**Recommended Approach:** Use the built-in persistence configuration for easier management and automatic PVC creation.

```
binaryData:

  mode: "filesystem"

  localStoragePath: "/home/node/.n8n/binary-data"



# Enable persistence for filesystem storage

main:

  persistence:

    enabled: true

    volumeName: "n8n-binary-data"

    mountPath: "/home/node/.n8n"

    size: 10Gi

    accessMode: ReadWriteOnce

    storageClass: "fast-ssd"

    annotations:

      helm.sh/resource-policy: keep
```

info

**Automatic Management:** The chart automatically creates and manages the PersistentVolumeClaim when persistence is enabled.

### Filesystem with Custom Storage Class[​](#filesystem-with-custom-storage-class "Direct link to Filesystem with Custom Storage Class")

tip

**Storage Class Configuration:** Use the persistence configuration to specify custom storage classes for optimal performance.

```
binaryData:

  mode: "filesystem"

  localStoragePath: "/home/node/.n8n/binary-data"



# Enable persistence with custom storage class

main:

  persistence:

    enabled: true

    volumeName: "n8n-binary-data"

    mountPath: "/home/node/.n8n"

    size: 100Gi

    accessMode: ReadWriteOnce

    storageClass: "fast-ssd"  # Custom storage class

    annotations:

      helm.sh/resource-policy: keep
```

info

**Storage Class Benefits:** Custom storage classes can provide better performance, reliability, or cost optimization based on your infrastructure requirements.

## S3-Compatible Storage Configuration[​](#s3-compatible-storage-configuration "Direct link to S3-Compatible Storage Configuration")

tip

**Production Recommendation:** S3-compatible storage is the recommended option for production deployments, especially for queue mode or multi-node setups.

### AWS S3 Configuration[​](#aws-s3-configuration "Direct link to AWS S3 Configuration")

```
binaryData:

  mode: "s3"

  s3:

    host: s3.amazonaws.com

    bucketName: n8n-binary-data

    bucketRegion: us-east-1

    accessKey: your-access-key

    accessSecret: your-secret-key
```

warning

**Security:** Never hardcode S3 credentials in your values file. Use Kubernetes secrets or IAM roles for secure credential management.

### AWS S3 with IAM Roles (EKS)[​](#aws-s3-with-iam-roles-eks "Direct link to AWS S3 with IAM Roles (EKS)")

```
binaryData:

  mode: "s3"

  s3:

    host: s3.amazonaws.com

    bucketName: n8n-binary-data

    bucketRegion: us-east-1



# Use IAM role instead of access keys

main:

  serviceAccount:

    annotations:

      eks.amazonaws.com/role-arn: arn:aws:iam::123456789012:role/n8n-s3-role
```

info

**IAM Best Practice:** Using IAM roles is the recommended approach for AWS EKS deployments as it eliminates the need to manage access keys.

### Google Cloud Storage[​](#google-cloud-storage "Direct link to Google Cloud Storage")

```
binaryData:

  mode: "s3"

  s3:

    host: storage.googleapis.com

    bucketName: n8n-binary-data

    bucketRegion: us-central1

    accessKey: your-gcs-access-key

    accessSecret: your-gcs-secret-key
```

### Azure Blob Storage[​](#azure-blob-storage "Direct link to Azure Blob Storage")

```
binaryData:

  mode: "s3"

  s3:

    host: your-storage-account.blob.core.windows.net

    bucketName: n8n-binary-data

    bucketRegion: eastus

    accessKey: your-storage-account-name

    accessSecret: your-storage-account-key
```

### DigitalOcean Spaces[​](#digitalocean-spaces "Direct link to DigitalOcean Spaces")

```
binaryData:

  mode: "s3"

  s3:

    host: nyc3.digitaloceanspaces.com

    bucketName: n8n-binary-data

    bucketRegion: nyc3

    accessKey: your-spaces-access-key

    accessSecret: your-spaces-secret-key
```

### S3 with Kubernetes Secrets[​](#s3-with-kubernetes-secrets "Direct link to S3 with Kubernetes Secrets")

```
# Create secret for S3 credentials

apiVersion: v1

kind: Secret

metadata:

  name: s3-credentials

type: Opaque

data:

  access-key-id: <base64-encoded-access-key>

  secret-access-key: <base64-encoded-secret-key>
```

```
# Use secret in configuration

binaryData:

  mode: "s3"

  s3:

    host: s3.amazonaws.com

    bucketName: n8n-binary-data

    bucketRegion: us-east-1

    existingSecret: s3-credentials
```

### S3 with Custom Endpoint[​](#s3-with-custom-endpoint "Direct link to S3 with Custom Endpoint")

```
binaryData:

  mode: "s3"

  s3:

    host: s3.yourcompany.com

    bucketName: n8n-binary-data

    bucketRegion: us-east-1

    accessKey: your-access-key

    accessSecret: your-secret-key
```

## MinIO Integration[​](#minio-integration "Direct link to MinIO Integration")

### MinIO with Chart[​](#minio-with-chart "Direct link to MinIO with Chart")

```
binaryData:

  mode: "s3"

  s3:

    host: minio.yourdomain.com

    bucketName: n8n-bucket

    bucketRegion: us-east-1

    accessKey: n8n-user

    accessSecret: your-secret-key



minio:

  enabled: true

  mode: standalone

  rootUser: minioadmin

  rootPassword: minioadmin123

  persistence:

    enabled: true

    size: 20Gi

  buckets:

    - name: n8n-bucket

      policy: none

      versioning: false

  users:

    - accessKey: n8n-user

      secretKey: your-secret-key

      policy: n8n-policy

  policies:

    - name: n8n-policy

      statements:

        - actions:

            - "s3:AbortMultipartUpload"

            - "s3:GetObject"

            - "s3:DeleteObject"

            - "s3:PutObject"

            - "s3:ListMultipartUploadParts"

          resources:

            - "arn:aws:s3:::n8n-bucket/*"

        - actions:

            - "s3:GetBucketLocation"

            - "s3:ListBucket"

            - "s3:ListBucketMultipartUploads"

          resources:

            - "arn:aws:s3:::n8n-bucket"
```

### MinIO High Availability[​](#minio-high-availability "Direct link to MinIO High Availability")

```
binaryData:

  mode: "s3"

  s3:

    host: minio.yourdomain.com

    bucketName: n8n-bucket

    bucketRegion: us-east-1

    accessKey: n8n-user

    accessSecret: your-secret-key



minio:

  enabled: true

  mode: distributed

  rootUser: minioadmin

  rootPassword: minioadmin123

  replicas: 4

  drivesPerNode: 1

  persistence:

    enabled: true

    size: 20Gi

  buckets:

    - name: n8n-bucket

      policy: none

      versioning: false

  users:

    - accessKey: n8n-user

      secretKey: your-secret-key

      policy: n8n-policy
```

### MinIO with Ingress[​](#minio-with-ingress "Direct link to MinIO with Ingress")

```
binaryData:

  mode: "s3"

  s3:

    host: minio.yourdomain.com

    bucketName: n8n-bucket

    bucketRegion: us-east-1

    accessKey: n8n-user

    accessSecret: your-secret-key



minio:

  enabled: true

  mode: standalone

  rootUser: minioadmin

  rootPassword: minioadmin123

  persistence:

    enabled: true

    size: 20Gi

  ingress:

    enabled: true

    hosts:

      - minio.yourdomain.com

    path: /

  consoleIngress:

    enabled: true

    hosts:

      - minio-console.yourdomain.com

    path: /
```

## Storage Migration[​](#storage-migration "Direct link to Storage Migration")

### From Default to Filesystem[​](#from-default-to-filesystem "Direct link to From Default to Filesystem")

tip

**Simplified Migration:** Use the built-in persistence configuration for easier migration from default to filesystem storage.

1. **Backup current data** (if any)
2. **Update configuration**:

```
binaryData:

  mode: "filesystem"

  localStoragePath: "/home/node/.n8n/binary-data"



# Enable persistence for filesystem storage

main:

  persistence:

    enabled: true

    volumeName: "n8n-binary-data"

    mountPath: "/home/node/.n8n"

    size: 10Gi

    accessMode: ReadWriteOnce

    storageClass: "fast-ssd"

    annotations:

      helm.sh/resource-policy: keep
```

info

**Automatic PVC Creation:** The chart automatically creates a PersistentVolumeClaim when persistence is enabled. No manual PVC creation is required.

warning

**Data Migration:** Ensure your binary data is backed up before switching storage modes, as data may not be automatically migrated between storage types.

### From Filesystem to S3[​](#from-filesystem-to-s3 "Direct link to From Filesystem to S3")

tip

**Cloud Migration:** Migrate from local filesystem storage to S3-compatible storage for better scalability and reliability.

1. **Backup filesystem data**:

```
# Copy data from pod

kubectl cp <namespace>/<n8n-pod>:/home/node/.n8n/binary-data ./n8n-backup
```

2. **Upload to S3**:

```
# Upload to S3 bucket

aws s3 sync ./n8n-backup s3://n8n-binary-data/



# Or use other S3-compatible tools

# For MinIO: mc cp ./n8n-backup myminio/n8n-binary-data/

# For GCS: gsutil -m cp -r ./n8n-backup gs://n8n-binary-data/
```

3. **Update configuration**:

```
binaryData:

  mode: "s3"

  s3:

    host: s3.amazonaws.com

    bucketName: n8n-binary-data

    bucketRegion: us-east-1

    accessKey: your-access-key

    accessSecret: your-secret-key



# Optionally disable persistence when using S3

main:

  persistence:

    enabled: false  # Not needed for S3 storage
```

info

**S3 Benefits:** S3 storage provides better scalability, reliability, and cost-effectiveness for production deployments.

warning

**Data Verification:** After migration, verify that all binary data is accessible through the new S3 storage before removing the old filesystem data.

## Node Persistence Configuration[​](#node-persistence-configuration "Direct link to Node Persistence Configuration")

info

**Persistence:** Configure persistent storage for each node type independently. Persistence is used to store n8n data, workflows, and configuration. Configure independently from hostAliases.

### Main Node Persistence Example[​](#main-node-persistence-example "Direct link to Main Node Persistence Example")

```
main:

  persistence:

    enabled: true

    volumeName: "n8n-main-data"

    mountPath: "/home/node/.n8n"

    size: 8Gi

    accessMode: ReadWriteOnce
```

### Worker Node Persistence Example[​](#worker-node-persistence-example "Direct link to Worker Node Persistence Example")

```
worker:

  mode: queue

  persistence:

    enabled: true

    volumeName: "n8n-worker-data"

    mountPath: "/home/node/.n8n"

    size: 5Gi

    accessMode: ReadWriteMany  # For autoscaling
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Storage Issues[​](#common-storage-issues "Direct link to Common Storage Issues")

#### S3 Connection Issues[​](#s3-connection-issues "Direct link to S3 Connection Issues")

```
# Check S3 credentials

kubectl get secret s3-credentials -o yaml



# Test S3 connectivity

kubectl exec -it <n8n-pod> -- curl -I https://s3.amazonaws.com



# Check n8n logs for S3 errors

kubectl logs -l app.kubernetes.io/name=n8n | grep -i s3
```

#### Filesystem Permission Issues[​](#filesystem-permission-issues "Direct link to Filesystem Permission Issues")

```
# Check volume permissions

kubectl exec -it <n8n-pod> -- ls -la /data



# Fix permissions if needed

kubectl exec -it <n8n-pod> -- chown -R 1000:1000 /data
```

#### MinIO Issues[​](#minio-issues "Direct link to MinIO Issues")

```
# Check MinIO pod status

kubectl get pods -l app.kubernetes.io/name=minio



# Check MinIO logs

kubectl logs -l app.kubernetes.io/name=minio



# Test MinIO connectivity

kubectl exec -it <n8n-pod> -- curl -I http://minio-service:9000
```

### Storage Performance Issues[​](#storage-performance-issues "Direct link to Storage Performance Issues")

#### Filesystem Performance[​](#filesystem-performance "Direct link to Filesystem Performance")

```
# Use high-performance storage class

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: n8n-binary-pvc

spec:

  accessModes:

    - ReadWriteOnce

  storageClassName: fast-ssd  # Use SSD storage

  resources:

    requests:

      storage: 100Gi
```

## Best Practices[​](#best-practices "Direct link to Best Practices")

### Security[​](#security "Direct link to Security")

* Use IAM roles instead of access keys when possible
* Store credentials in Kubernetes secrets
* Enable bucket encryption for sensitive data
* Use network policies to restrict access
* Regularly rotate access keys

### Performance[​](#performance "Direct link to Performance")

* Use S3 for production workloads
* Configure appropriate file size limits
* Enable cleanup to prevent storage bloat
* Use high-performance storage for filesystem mode
* Monitor storage usage and costs

### Reliability[​](#reliability "Direct link to Reliability")

* Use S3 for multi-node deployments
* Enable versioning for critical data
* Set up backup strategies
* Monitor storage health
* Test disaster recovery procedures

### Cost Optimization[​](#cost-optimization "Direct link to Cost Optimization")

* Configure appropriate TTL for binary data
* Use lifecycle policies for S3 buckets
* Monitor storage usage and costs
* Clean up unused data regularly
* Use appropriate storage classes

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Usage Guide](/docs/charts/n8n/usage.md) - Quick start and basic deployment
* [Configuration Guide](/docs/charts/n8n/configuration.md) - Detailed configuration options
* [Database Setup](/docs/charts/n8n/database-setup.md) - PostgreSQL and external database configuration
* [Queue Mode Setup](/docs/charts/n8n/queue-mode.md) - Distributed execution with Redis
* [Monitoring Setup](/docs/charts/n8n/monitoring.md) - Metrics and observability
* [Troubleshooting](/docs/charts/n8n/troubleshooting.md) - Common issues and solutions


---

# n8n Troubleshooting Guide

This guide covers common issues and solutions when deploying n8n using the Helm chart.

info

**Troubleshooting Approach:** Always start with the quick diagnostics section to gather basic information about your deployment before diving into specific issues.

## Quick Diagnostics[​](#quick-diagnostics "Direct link to Quick Diagnostics")

tip

**Diagnostic Order:** Follow this order for systematic troubleshooting: Pod Status → Services → ConfigMaps/Secrets → Application Logs.

### Check Pod Status[​](#check-pod-status "Direct link to Check Pod Status")

```
# Check all n8n-related pods

kubectl get pods -l app.kubernetes.io/name=n8n



# Check pod details

kubectl describe pod <pod-name>



# Check pod logs

kubectl logs <pod-name>
```

### Check Services[​](#check-services "Direct link to Check Services")

```
# Check service status

kubectl get svc -l app.kubernetes.io/name=n8n



# Check service endpoints

kubectl get endpoints -l app.kubernetes.io/name=n8n
```

### Check ConfigMaps and Secrets[​](#check-configmaps-and-secrets "Direct link to Check ConfigMaps and Secrets")

```
# Check ConfigMaps

kubectl get configmap -l app.kubernetes.io/name=n8n



# Check Secrets

kubectl get secret -l app.kubernetes.io/name=n8n
```

## Common Issues[​](#common-issues "Direct link to Common Issues")

warning

**Issue Resolution:** Always check the logs first when troubleshooting. Most issues can be identified from application logs.

### Pod Startup Issues[​](#pod-startup-issues "Direct link to Pod Startup Issues")

#### Pod Stuck in Pending State[​](#pod-stuck-in-pending-state "Direct link to Pod Stuck in Pending State")

**Symptoms:**

* Pod remains in `Pending` state
* No events in pod description

**Solutions:**

1. **Check Resource Requests:**

```
kubectl describe pod <pod-name> | grep -A 10 "Events:"
```

2. **Check Node Resources:**

```
kubectl top nodes

kubectl describe node <node-name>
```

3. **Check Storage:**

```
kubectl get pvc

kubectl describe pvc <pvc-name>
```

note

**Resource Issues:** Pods stuck in Pending state are usually due to insufficient cluster resources or storage issues.

#### Pod Stuck in CrashLoopBackOff[​](#pod-stuck-in-crashloopbackoff "Direct link to Pod Stuck in CrashLoopBackOff")

**Symptoms:**

* Pod repeatedly crashes and restarts
* Exit code 1 or 137

**Solutions:**

1. **Check Application Logs:**

```
kubectl logs <pod-name> --previous
```

2. **Check Resource Limits:**

```
kubectl describe pod <pod-name> | grep -A 5 "Containers:"
```

3. **Check Configuration:**

```
kubectl get configmap <configmap-name> -o yaml
```

danger

**CrashLoopBackOff:** This indicates a serious configuration or resource issue. Check logs immediately and verify all configuration values.

### Database Connection Issues[​](#database-connection-issues "Direct link to Database Connection Issues")

warning

**Database Issues:** Database connection problems are among the most common issues. Always verify database credentials and connectivity.

#### PostgreSQL Connection Failures[​](#postgresql-connection-failures "Direct link to PostgreSQL Connection Failures")

**Symptoms:**

* Database connection timeout errors
* Authentication failures
* Cloud SQL Proxy sidecar errors (if using GKE/Cloud SQL)

**Solutions:**

1. **Check Database Pod:**

```
kubectl get pods -l app.kubernetes.io/name=postgresql

kubectl logs -l app.kubernetes.io/name=postgresql
```

2. **Test Database Connection:**

```
kubectl exec -it <n8n-pod> -- nc -zv <db-host> <db-port>
```

3. **Check Database Credentials:**

```
kubectl get secret <db-secret> -o yaml
```

4. **Verify Database Configuration:**

```
# Check values.yaml

db:

  type: postgresdb

  logging:

    enabled: true

    options: error

    maxQueryExecutionTime: 1000



postgresql:

  enabled: true

  auth:

    username: n8n

    password: your-secure-password

    database: n8n
```

5. **If using Cloud SQL Proxy (GKE/Cloud SQL):**

   * Check the Cloud SQL Proxy sidecar logs:
     <!-- -->
     ```
     kubectl logs <n8n-pod> -c cloudsql-proxy
     ```
   * Ensure the service account has the `Cloud SQL Client` role.
   * Verify the instance connection name is correct.
   * Make sure the proxy port matches `externalPostgresql.port`.
   * See [Cloud SQL Proxy docs](https://cloud.google.com/sql/docs/postgres/connect-run#kubernetes-engine) for more troubleshooting.

#### SQLite Issues[​](#sqlite-issues "Direct link to SQLite Issues")

**Symptoms:**

* Database lock errors
* Permission denied errors

**Solutions:**

1. **Check File Permissions:**

```
kubectl exec -it <n8n-pod> -- ls -la /home/node/.n8n/
```

2. **Check Disk Space:**

```
kubectl exec -it <n8n-pod> -- df -h
```

3. **Enable SQLite Logging:**

```
db:

  type: sqlite

  sqlite:

    database: "database.sqlite"

    poolSize: 0

    vacuum: true
```

tip

**SQLite Debugging:** Enable SQLite logging and VACUUM operations to identify and resolve database issues.

### Queue Mode Issues[​](#queue-mode-issues "Direct link to Queue Mode Issues")

info

**Queue Mode:** Queue mode issues often involve Redis connectivity or configuration problems. Verify Redis is running and accessible.

#### Redis Connection Problems[​](#redis-connection-problems "Direct link to Redis Connection Problems")

**Symptoms:**

* Queue mode not working
* Redis connection errors

**Solutions:**

1. **Check Redis Pod:**

```
kubectl get pods -l app.kubernetes.io/name=redis

kubectl logs -l app.kubernetes.io/name=redis
```

2. **Test Redis Connection:**

```
kubectl exec -it <n8n-pod> -- redis-cli -h <redis-host> ping
```

3. **Check Redis Configuration:**

```
redis:

  enabled: true

  architecture: standalone

  master:

    persistence:

      enabled: true

      size: 5Gi
```

#### Worker Node Issues[​](#worker-node-issues "Direct link to Worker Node Issues")

**Symptoms:**

* Workers not processing jobs
* Queue backlog

**Solutions:**

1. **Check Worker Pods:**

```
kubectl get pods -l app.kubernetes.io/component=worker

kubectl logs -l app.kubernetes.io/component=worker
```

2. **Check Worker Configuration:**

```
worker:

  mode: queue

  count: 2

  concurrency: 10

  resources:

    requests:

      cpu: 500m

      memory: 512Mi

    limits:

      cpu: 2000m

      memory: 2Gi
```

3. **Check Queue Status:**

```
kubectl exec -it <n8n-pod> -- curl -s http://localhost:5678/metrics | grep queue
```

### MCP and Form Endpoint Issues[​](#mcp-and-form-endpoint-issues "Direct link to MCP and Form Endpoint Issues")

info

**Advanced Endpoints:** MCP and Form endpoints are only available in queue mode with PostgreSQL database. Verify your configuration meets these requirements.

#### MCP Endpoint Problems[​](#mcp-endpoint-problems "Direct link to MCP Endpoint Problems")

**Symptoms:**

* MCP endpoints not accessible
* AI model integration failures
* MCP authentication errors

**Solutions:**

1. **Verify Queue Mode Configuration:**

```
# Ensure queue mode is enabled

webhook:

  mode: queue

  url: "https://yourdomain.com"



# Ensure PostgreSQL is configured

db:

  type: postgresdb
```

2. **Check MCP Endpoint Accessibility:**

```
# Test MCP endpoint

curl -I https://yourdomain.com/mcp/



# Test MCP test endpoint

curl -I https://yourdomain.com/mcp-test/
```

3. **Check Ingress Configuration:**

```
# Verify ingress includes MCP paths

kubectl get ingress -o yaml | grep -A 10 -B 5 mcp
```

4. **Check Webhook Node Logs:**

```
# MCP endpoints are handled by webhook nodes

kubectl logs -l app.kubernetes.io/component=webhook
```

5. **Verify MCP Authentication:**

```
# If using MCP authentication

ingress:

  annotations:

    nginx.ingress.kubernetes.io/auth-type: basic

    nginx.ingress.kubernetes.io/auth-secret: mcp-auth
```

warning

**MCP Requirements:** MCP endpoints require PostgreSQL database and queue mode. They are not available with SQLite or single-node deployments.

#### Form Endpoint Problems[​](#form-endpoint-problems "Direct link to Form Endpoint Problems")

**Symptoms:**

* Form endpoints not accessible
* Form submission failures
* Form waiting workflows not working

**Solutions:**

1. **Verify Form Endpoint Configuration:**

```
# Ensure queue mode is enabled

webhook:

  mode: queue

  url: "https://yourdomain.com"
```

2. **Check Form Endpoint Accessibility:**

```
# Test form endpoint

curl -I https://yourdomain.com/form/



# Test form test endpoint

curl -I https://yourdomain.com/form-test/



# Test form waiting endpoint

curl -I https://yourdomain.com/form-waiting/
```

3. **Check Form Trigger Node Configuration:**

```
# Verify form trigger is properly configured in n8n UI

# Check workflow execution logs

kubectl logs -l app.kubernetes.io/name=n8n | grep -i form
```

4. **Test Form Submission:**

```
# Test form submission

curl -X POST https://yourdomain.com/form/ \

  -H "Content-Type: application/json" \

  -d '{"test": "data"}'
```

5. **Check Webhook Node Status:**

```
# Form endpoints are handled by webhook nodes

kubectl get pods -l app.kubernetes.io/component=webhook

kubectl logs -l app.kubernetes.io/component=webhook
```

tip

**Form Testing:** Use the `/form-test/` endpoint to test form functionality before deploying to production.

#### Endpoint Routing Issues[​](#endpoint-routing-issues "Direct link to Endpoint Routing Issues")

**Symptoms:**

* Endpoints routed to wrong nodes
* Performance issues with specific endpoints

**Solutions:**

1. **Verify Endpoint Routing:**

```
# Check which nodes handle which endpoints

kubectl get pods -l app.kubernetes.io/name=n8n -o wide
```

2. **Check Service Configuration:**

```
# Verify service endpoints

kubectl get endpoints -l app.kubernetes.io/name=n8n
```

3. **Monitor Endpoint Performance:**

```
# Check metrics for endpoint performance

kubectl exec -it <n8n-pod> -- curl -s http://localhost:5678/metrics | grep api
```

info

**Routing Logic:** In queue mode, test endpoints (`/mcp-test/`, `/form-test/`) are handled by main nodes, while production endpoints (`/mcp/`, `/form/`) are handled by webhook nodes.

### Persistence Issues[​](#persistence-issues "Direct link to Persistence Issues")

info

**Enhanced Features:** The chart supports comprehensive persistence for all node types. This feature requires proper configuration to work correctly.

#### Common Persistence Issues[​](#common-persistence-issues "Direct link to Common Persistence Issues")

* PVC not bound
* Volume mount errors
* Data loss after pod restarts

#### Example Checks[​](#example-checks "Direct link to Example Checks")

```
# Check PVC status

kubectl get pvc -l app.kubernetes.io/name=n8n



# Check volume mounts in pods

kubectl describe pod <n8n-pod> | grep -A 10 "Volumes:"



# Check disk space

kubectl exec -it <n8n-pod> -- df -h
```

### Storage Issues[​](#storage-issues "Direct link to Storage Issues")

#### S3 Connection Problems[​](#s3-connection-problems "Direct link to S3 Connection Problems")

**Symptoms:**

* Binary data upload failures
* S3 authentication errors

**Solutions:**

1. **Check S3 Credentials:**

```
kubectl get secret <s3-secret> -o yaml
```

2. **Test S3 Connectivity:**

```
kubectl exec -it <n8n-pod> -- curl -I https://s3.amazonaws.com
```

3. **Check S3 Configuration:**

```
binaryData:

  mode: "s3"

  s3:

    host: s3.amazonaws.com

    bucketName: n8n-binary-data

    bucketRegion: us-east-1

    accessKey: your-access-key

    accessSecret: your-secret-key
```

#### Filesystem Storage Issues[​](#filesystem-storage-issues "Direct link to Filesystem Storage Issues")

**Symptoms:**

* Permission denied errors
* Disk space issues

**Solutions:**

1. **Check Volume Permissions:**

```
kubectl exec -it <n8n-pod> -- ls -la /data
```

2. **Check Disk Space:**

```
kubectl exec -it <n8n-pod> -- df -h
```

3. **Fix Permissions:**

```
kubectl exec -it <n8n-pod> -- chown -R 1000:1000 /data
```

### Network Issues[​](#network-issues "Direct link to Network Issues")

#### Ingress Problems[​](#ingress-problems "Direct link to Ingress Problems")

**Symptoms:**

* Cannot access n8n from outside
* 404 or 502 errors

**Solutions:**

1. **Check Ingress Status:**

```
kubectl get ingress

kubectl describe ingress <ingress-name>
```

2. **Check Ingress Controller:**

```
kubectl get pods -n ingress-nginx

kubectl logs -n ingress-nginx -l app.kubernetes.io/name=ingress-nginx
```

3. **Test Service:**

```
kubectl port-forward svc/<n8n-service> 8080:5678

curl http://localhost:8080
```

#### Service Connectivity[​](#service-connectivity "Direct link to Service Connectivity")

**Symptoms:**

* Pods cannot communicate
* Service discovery issues

**Solutions:**

1. **Check Service Endpoints:**

```
kubectl get endpoints <service-name>
```

2. **Test Pod-to-Pod Communication:**

```
kubectl exec -it <pod1> -- nc -zv <pod2-ip> <port>
```

3. **Check Network Policies:**

```
kubectl get networkpolicy

kubectl describe networkpolicy <policy-name>
```

### Performance Issues[​](#performance-issues "Direct link to Performance Issues")

#### High Memory Usage[​](#high-memory-usage "Direct link to High Memory Usage")

**Symptoms:**

* Pods being OOM killed
* Slow response times

**Solutions:**

1. **Check Memory Usage:**

```
kubectl top pods -l app.kubernetes.io/name=n8n
```

2. **Increase Memory Limits:**

```
main:

  resources:

    requests:

      memory: 512Mi

    limits:

      memory: 2Gi
```

3. **Enable Memory Monitoring:**

```
serviceMonitor:

  enabled: true

  include:

    defaultMetrics: true
```

#### High CPU Usage[​](#high-cpu-usage "Direct link to High CPU Usage")

**Symptoms:**

* Slow workflow execution
* High CPU utilization

**Solutions:**

1. **Check CPU Usage:**

```
kubectl top pods -l app.kubernetes.io/name=n8n
```

2. **Increase CPU Limits:**

```
main:

  resources:

    requests:

      cpu: 500m

    limits:

      cpu: 2000m
```

3. **Scale Workers:**

```
worker:

  mode: queue

  autoscaling:

    enabled: true

    minReplicas: 2

    maxReplicas: 10
```

## Debugging Commands[​](#debugging-commands "Direct link to Debugging Commands")

### General Debugging[​](#general-debugging "Direct link to General Debugging")

```
# Get detailed pod information

kubectl describe pod <pod-name>



# Get pod logs with timestamps

kubectl logs <pod-name> --timestamps



# Get logs from previous container

kubectl logs <pod-name> --previous



# Execute commands in pod

kubectl exec -it <pod-name> -- /bin/sh



# Check environment variables

kubectl exec -it <pod-name> -- env | grep N8N
```

### Database Debugging[​](#database-debugging "Direct link to Database Debugging")

```
# Connect to PostgreSQL

kubectl exec -it <postgres-pod> -- psql -U n8n -d n8n



# Check SQLite database

kubectl exec -it <n8n-pod> -- sqlite3 /home/node/.n8n/database.sqlite ".tables"



# Check database logs

kubectl logs <n8n-pod> | grep -i database
```

### Network Debugging[​](#network-debugging "Direct link to Network Debugging")

```
# Check DNS resolution

kubectl exec -it <pod-name> -- nslookup <service-name>



# Test network connectivity

kubectl exec -it <pod-name> -- nc -zv <host> <port>



# Check network policies

kubectl get networkpolicy

kubectl describe networkpolicy <policy-name>
```

### Storage Debugging[​](#storage-debugging "Direct link to Storage Debugging")

```
# Check volume mounts

kubectl exec -it <pod-name> -- mount | grep n8n



# Check file permissions

kubectl exec -it <pod-name> -- ls -la /data



# Check disk usage

kubectl exec -it <pod-name> -- df -h
```

### Affinity Debugging[​](#affinity-debugging "Direct link to Affinity Debugging")

tip

**Affinity Issues:** Pod affinity and anti-affinity rules can cause scheduling issues. Check affinity configuration when pods are stuck in Pending state.

#### Check Affinity Configuration[​](#check-affinity-configuration "Direct link to Check Affinity Configuration")

```
# Check current affinity settings

kubectl get pod <pod-name> -o yaml | grep -A 20 affinity



# Check node labels

kubectl get nodes --show-labels



# Check pod labels

kubectl get pods -l app.kubernetes.io/name=n8n --show-labels
```

#### Common Affinity Issues[​](#common-affinity-issues "Direct link to Common Affinity Issues")

**Symptoms:**

* Pods stuck in Pending state
* "0/1 nodes are available" errors
* Scheduling failures due to affinity rules

**Solutions:**

1. **Check Node Availability:**

```
# Check if nodes match affinity requirements

kubectl get nodes -l node-type=compute-optimized

kubectl get nodes -l storage-type=ssd
```

2. **Verify Topology Keys:**

```
# Check available topology keys

kubectl get nodes -o jsonpath='{.items[*].metadata.labels.topology\.kubernetes\.io/zone}' | tr ' ' '\n' | sort | uniq

kubectl get nodes -o jsonpath='{.items[*].metadata.labels.kubernetes\.io/hostname}' | tr ' ' '\n' | sort | uniq
```

3. **Check Affinity Rules:**

```
# Example: Debug affinity configuration

main:

  affinity:

    nodeAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

        nodeSelectorTerms:

        - matchExpressions:

          - key: node-type

            operator: In

            values:

            - compute-optimized  # Verify this label exists

    podAntiAffinity:

      requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchLabels:

            app.kubernetes.io/name: n8n

        topologyKey: kubernetes.io/hostname  # Verify this topology key exists
```

4. **Troubleshoot Anti-Affinity Conflicts:**

```
# Check if anti-affinity rules are too restrictive

kubectl get pods -l app.kubernetes.io/name=n8n -o wide



# Check node capacity

kubectl describe node <node-name> | grep -A 10 "Allocated resources"
```

#### Affinity Configuration Examples[​](#affinity-configuration-examples "Direct link to Affinity Configuration Examples")

**Fix: Relax Anti-Affinity Rules**

```
# Change from required to preferred

worker:

  mode: queue

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:  # Changed from requiredDuringSchedulingIgnoredDuringExecution

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchLabels:

              app.kubernetes.io/name: n8n

              app.kubernetes.io/component: worker

          topologyKey: kubernetes.io/hostname
```

**Fix: Use Correct Topology Keys**

```
# Use available topology keys

worker:

  mode: queue

  affinity:

    podAntiAffinity:

      preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchLabels:

              app.kubernetes.io/name: n8n

              app.kubernetes.io/component: worker

          topologyKey: topology.kubernetes.io/zone  # Use available topology key
```

warning

**Deprecation Notice:** The top-level `affinity` field is deprecated. Use the specific affinity configurations under `main`, `worker`, and `webhook` blocks instead.

info

**Affinity Debugging:** When troubleshooting scheduling issues, always check if affinity rules are preventing pod placement and verify that required node labels and topology keys exist.

## Log Analysis[​](#log-analysis "Direct link to Log Analysis")

### Common Log Patterns[​](#common-log-patterns "Direct link to Common Log Patterns")

#### Database Connection Errors[​](#database-connection-errors "Direct link to Database Connection Errors")

```
Error: connect ECONNREFUSED

Error: timeout acquiring a connection

Error: authentication failed
```

#### Queue Mode Errors[​](#queue-mode-errors "Direct link to Queue Mode Errors")

```
Error: Redis connection failed

Error: Queue processing failed

Error: Worker not responding
```

#### Storage Errors[​](#storage-errors "Direct link to Storage Errors")

```
Error: S3 upload failed

Error: Permission denied

Error: Disk space full
```

### Log Filtering[​](#log-filtering "Direct link to Log Filtering")

```
# Filter for errors

kubectl logs <pod-name> | grep -i error



# Filter for specific components

kubectl logs <pod-name> | grep -i database

kubectl logs <pod-name> | grep -i redis

kubectl logs <pod-name> | grep -i s3



# Filter by time

kubectl logs <pod-name> --since=1h

kubectl logs <pod-name> --since-time="2024-01-01T00:00:00Z"
```

## Recovery Procedures[​](#recovery-procedures "Direct link to Recovery Procedures")

### Pod Recovery[​](#pod-recovery "Direct link to Pod Recovery")

```
# Restart deployment

kubectl rollout restart deployment <deployment-name>



# Scale down and up

kubectl scale deployment <deployment-name> --replicas=0

kubectl scale deployment <deployment-name> --replicas=1



# Delete and recreate pod

kubectl delete pod <pod-name>
```

### Database Recovery[​](#database-recovery "Direct link to Database Recovery")

```
# Backup database

kubectl exec -it <n8n-pod> -- pg_dump -h <db-host> -U n8n -d n8n > backup.sql



# Restore database

kubectl exec -it <n8n-pod> -- psql -h <db-host> -U n8n -d n8n < backup.sql
```

### Configuration Recovery[​](#configuration-recovery "Direct link to Configuration Recovery")

```
# Check current configuration

kubectl get configmap <configmap-name> -o yaml



# Update configuration

kubectl patch configmap <configmap-name> --patch '{"data":{"key":"value"}}'



# Restart to apply changes

kubectl rollout restart deployment <deployment-name>
```

## Prevention[​](#prevention "Direct link to Prevention")

### Best Practices[​](#best-practices "Direct link to Best Practices")

1. **Resource Planning:**

   * Set appropriate resource requests and limits
   * Monitor resource usage regularly
   * Plan for scaling needs

2. **Monitoring:**

   * Enable comprehensive monitoring
   * Set up alerting for critical metrics
   * Regular log analysis

3. **Backup Strategy:**

   * Regular database backups
   * Configuration backups
   * Disaster recovery testing

4. **Security:**

   * Use Kubernetes secrets for sensitive data
   * Enable RBAC
   * Regular security updates

5. **Documentation:**

   * Document custom configurations
   * Maintain runbooks for common issues
   * Regular review and updates

## Getting Help[​](#getting-help "Direct link to Getting Help")

### Community Resources[​](#community-resources "Direct link to Community Resources")

* **GitHub Issues:** [Report bugs or request features](https://github.com/community-charts/helm-charts/issues)
* **Discussions:** [Community discussions](https://github.com/community-charts/helm-charts/discussions)
* **n8n Documentation:** [Official n8n docs](https://docs.n8n.io)

### Support Information[​](#support-information "Direct link to Support Information")

When seeking help, please provide:

1. **Environment Details:**

   * Kubernetes version
   * Helm version
   * Chart version
   * n8n version

2. **Configuration:**

   * Relevant parts of values.yaml
   * Custom configurations

3. **Error Information:**

   * Complete error messages
   * Pod logs
   * Events from `kubectl describe`

4. **Steps to Reproduce:**

   * Exact commands used
   * Expected vs actual behavior

## Next Steps[​](#next-steps "Direct link to Next Steps")

* [Usage Guide](/docs/charts/n8n/usage.md) - Quick start and basic deployment
* [Configuration Guide](/docs/charts/n8n/configuration.md) - Detailed configuration options
* [Database Setup](/docs/charts/n8n/database-setup.md) - PostgreSQL and external database configuration
* [Queue Mode Setup](/docs/charts/n8n/queue-mode.md) - Distributed execution with Redis
* [Storage Configuration](/docs/charts/n8n/storage.md) - Binary data storage options
* [Monitoring Setup](/docs/charts/n8n/monitoring.md) - Metrics and observability


---

# n8n Chart Usage Guide

[n8n](https://n8n.io) is a powerful workflow automation platform that enables seamless integration between applications and services through an intuitive visual interface. This Helm chart provides a production-ready deployment solution for running n8n on Kubernetes with enterprise-grade features and scalability.

info

**Quick Reference:**

* **Official Website:** <https://n8n.io>
* **GitHub Repository:** <https://github.com/n8n-io/n8n>
* **Documentation:** <https://docs.n8n.io>
* **ArtifactHub:** [n8n Helm Chart](https://artifacthub.io/packages/helm/community-charts/n8n)

## Why Choose This Chart?[​](#why-choose-this-chart "Direct link to Why Choose This Chart?")

tip

**Enterprise-Grade Solution:** This chart delivers production-ready features that transform n8n into a robust enterprise automation platform.

### Key Advantages[​](#key-advantages "Direct link to Key Advantages")

* **Production-Ready Architecture:** Deploy n8n with enterprise-level reliability and performance
* **Community-Driven Development:** Continuously maintained and thoroughly tested by the community
* **Scalable Design:** Advanced queue mode with dedicated worker and webhook nodes
* **Flexible Configuration:** Support for multiple database backends, external storage, and comprehensive monitoring
* **Security-First Approach:** Built-in security contexts, secrets management, and RBAC integration
* **Advanced Package Management:** **Exclusive npm package installation capabilities** - Deploy custom npm packages and community nodes directly within main and worker pods
* **External Task Runners:** **Unique external task runner support** - Execute workflows in isolated sidecar containers for enhanced security and performance

info

**Distinctive Features:** This chart offers capabilities unavailable in other n8n Helm charts, establishing it as the preferred solution for sophisticated deployments.

## Quick Start Guide[​](#quick-start-guide "Direct link to Quick Start Guide")

### Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**System Requirements:** Ensure all prerequisites are properly installed and configured before proceeding with deployment.

#### Required Components[​](#required-components "Direct link to Required Components")

* Kubernetes cluster (version 1.19 or higher)
* Helm 3.0 or higher
* kubectl configured for cluster access
* Storage class for persistent volumes (required for PostgreSQL/MinIO deployments)

#### Cloud-Specific Requirements[​](#cloud-specific-requirements "Direct link to Cloud-Specific Requirements")

**Google Cloud Platform (GKE):**

* For Google Cloud SQL (PostgreSQL) deployments, Cloud SQL Proxy sidecar is mandatory
* Refer to [Google Cloud SQL Setup](/docs/charts/n8n/database-setup.md#google-cloud-sql-gcp-with-cloud-sql-proxy) for detailed configuration

**AWS/Azure:**

* For AWS RDS/Aurora deployments, see [AWS RDS/Aurora Configuration](/docs/charts/n8n/database-setup.md#aws-rdsaurora-postgresql)
* For Azure Database for PostgreSQL, see [Azure Database Setup](/docs/charts/n8n/database-setup.md#azure-database-for-postgresql)

danger

**Version Compatibility:** Verify your Kubernetes cluster version meets the chart requirements to prevent deployment failures.

### Basic Deployment[​](#basic-deployment "Direct link to Basic Deployment")

```
# Add the community charts repository

helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update



# Deploy n8n with default configuration (SQLite backend)

helm install my-n8n community-charts/n8n -n <your-namespace>
```

tip

**Development Environment:** The basic SQLite deployment is ideal for development, testing, and evaluation purposes. For production environments, we recommend PostgreSQL with queue mode.

warning

**Data Persistence Warning:** SQLite data is ephemeral and will be lost upon pod termination. Implement PostgreSQL for production deployments requiring data persistence.

### Production Deployment with PostgreSQL[​](#production-deployment-with-postgresql "Direct link to Production Deployment with PostgreSQL")

```
# Deploy with PostgreSQL backend for production use

helm install my-n8n community-charts/n8n \

  --set db.type=postgresdb \

  --set postgresql.enabled=true \

  --set postgresql.auth.database=n8n \

  --set postgresql.auth.username=n8n \

  --set postgresql.auth.password=your-secure-password \

  -n <your-namespace>
```

note

**Security Best Practice:** Always employ strong, unique passwords for database credentials. Consider utilizing Kubernetes secrets for sensitive configuration data.

danger

**Production Database Requirement:** SQLite is unsuitable for production environments. PostgreSQL delivers superior performance, reliability, and supports advanced queue mode functionality.

### External Access Configuration[​](#external-access-configuration "Direct link to External Access Configuration")

```
# Deploy with ingress for external access

helm install my-n8n community-charts/n8n \

  --set ingress.enabled=true \

  --set ingress.hosts[0].host=n8n.yourdomain.com \

  --set db.type=postgresdb \

  --set postgresql.enabled=true \

  -n <your-namespace>
```

warning

**Security Configuration:** When exposing n8n through ingress, ensure proper TLS certificate configuration and security headers are implemented.

### Enterprise Queue Mode Deployment[​](#enterprise-queue-mode-deployment "Direct link to Enterprise Queue Mode Deployment")

```
# Deploy with queue mode for distributed execution and high availability

helm install my-n8n community-charts/n8n \

  --set db.type=postgresdb \

  --set postgresql.enabled=true \

  --set redis.enabled=true \

  --set worker.mode=queue \

  --set webhook.mode=queue \

  --set webhook.url=https://webhook.yourdomain.com \

  --set ingress.enabled=true \

  --set ingress.hosts[0].host=n8n.yourdomain.com \

  -n <your-namespace>
```

tip

**Production Recommendation:** Queue mode with PostgreSQL and Redis represents the optimal configuration for production environments, providing enhanced scalability, reliability, and performance characteristics.

info

**Queue Mode Benefits:** Queue mode enables distributed workflow execution, improved resource utilization, and enhanced reliability for high-volume automation scenarios.

tip

**Managed Redis Services:** For cloud-managed Redis on GCP, AWS, or Azure, refer to [Cloud Redis Configuration](/docs/charts/n8n/cloud-redis.md).

## Core Features[​](#core-features "Direct link to Core Features")

info

**Feature Overview:** These capabilities transform n8n into a comprehensive enterprise automation platform.

### Database Integration[​](#database-integration "Direct link to Database Integration")

* **SQLite** (default) - Simplified single-node deployments for development
* **PostgreSQL** - Enterprise-grade database support with Bitnami PostgreSQL or external instances

warning

**Database Selection:** SQLite is appropriate solely for development and testing scenarios. PostgreSQL is mandatory for all production deployments.

### Deployment Architectures[​](#deployment-architectures "Direct link to Deployment Architectures")

* **Standard Mode** - Single n8n instance deployment (default configuration)
* **Queue Mode** - Distributed execution architecture with dedicated worker nodes
* **Webhook Mode** - Specialized webhook processing nodes for high-throughput scenarios

tip

**Architecture Selection:** Choose the deployment architecture based on your workload requirements, scalability needs, and performance objectives.

### Advanced Endpoint Support (Queue Mode)[​](#advanced-endpoint-support-queue-mode "Direct link to Advanced Endpoint Support (Queue Mode)")

* **MCP Endpoints** - Model Context Protocol integration for AI assistant connectivity
* **Form Endpoints** - Interactive web form generation for workflow trigger mechanisms
* **Webhook Endpoints** - High-performance HTTP webhook processing for external system integration

info

**Queue Mode Requirement:** MCP and Form endpoints are exclusively available in queue mode deployments utilizing PostgreSQL database.

tip

**AI Integration Capabilities:** MCP endpoints facilitate seamless interaction between AI models, assistants, and n8n workflows through the Model Context Protocol.

#### MCP Service and Client Integration[​](#mcp-service-and-client-integration "Direct link to MCP Service and Client Integration")

n8n now provides a dedicated MCP webhook service and endpoints for scalable AI/LLM integration:

* **MCP Endpoint:** `/mcp/` (for AI assistants, LLMs, and tool clients)
* **MCP Test Endpoint:** `/mcp-test/`
* **MCP Webhook Service:** Deployed automatically when `webhook.mode=queue` and `db.type=postgresdb` and `webhook.mcp.enabled`

##### Example values.yaml for MCP[​](#example-valuesyaml-for-mcp "Direct link to Example values.yaml for MCP")

```
webhook:

  mode: queue

  url: "https://webhook.yourdomain.com"

  count: 2

  mcp:

    enabled: true

    # Customize resources, affinity, env, etc. under webhook.mcp
```

##### MCP Client Settings (Claude Desktop, Cursor, etc.)[​](#mcp-client-settings-claude-desktop-cursor-etc "Direct link to MCP Client Settings (Claude Desktop, Cursor, etc.)")

tip

[Supergateway](https://github.com/supercorp-ai/supergateway) runs MCP stdio-based servers over SSE (Server-Sent Events) with one command.

```
{

  "mcpServers": {

    "command": "npx",

    "args": [

      "-y",

      "supergateway",

      "--sse",

      "https://webhook.myhost/mcp/ab123c45-d678-9d0e-fg1a-2345bcd6ef7g"

    ]

  }

}
```

With header authentication:

```
{

  "mcpServers": {

    "command": "npx",

    "args": [

      "-y",

      "supergateway",

      "--sse",

      "https://webhook.myhost/mcp/ab123c45-d678-9d0e-fg1a-2345bcd6ef7g",

      "--header",

      "mykey:myvalue"

    ]

  }

}
```

* Set these in Claude Desktop, Cursor, or any compatible MCP client.
* Use `--header` for custom authentication (API keys, tokens, etc).

tip

**Scaling:**

* Scale the MCP service with `webhook.count`, `webhook.autoscaling`, or `webhook.allNodes`.
* Customize resources, affinity, and environment variables under `webhook.mcp`.

### Storage Solutions[​](#storage-solutions "Direct link to Storage Solutions")

* **Default Storage** - In-memory binary data storage for simple deployments
* **Filesystem Storage** - Local file system storage for single-node scenarios
* **S3-Compatible Storage** - External object storage integration (AWS S3, MinIO, and compatible services)

info

**Storage Strategy:** Implement S3-compatible storage for production environments to ensure data persistence and enable collaborative team workflows.

### Monitoring and Observability[​](#monitoring-and-observability "Direct link to Monitoring and Observability")

* **Prometheus Metrics** - Comprehensive built-in metrics endpoint
* **ServiceMonitor Integration** - Seamless Prometheus Operator compatibility
* **Health Monitoring** - Configurable liveness and readiness probe mechanisms
* **Logging Framework** - Flexible log level configuration and output management

tip

**Monitoring Implementation:** Enable comprehensive monitoring to track n8n performance metrics, identify potential bottlenecks, and ensure operational reliability.

### Security Framework[​](#security-framework "Direct link to Security Framework")

* **RBAC Integration** - Kubernetes role-based access control implementation
* **Security Contexts** - Non-root container execution for enhanced security
* **Secrets Management** - Kubernetes secrets integration for sensitive data
* **Network Policies** - Pod-to-pod communication control and isolation

warning

**Security Configuration:** Always implement proper security contexts and RBAC policies for production deployments to ensure compliance and protection.

### Pod Affinity and Anti-Affinity[​](#pod-affinity-and-anti-affinity "Direct link to Pod Affinity and Anti-Affinity")

* **Advanced Scheduling** - Control pod placement with affinity rules
* **Node Distribution** - Spread pods across nodes for high availability
* **Zone Distribution** - Distribute pods across availability zones
* **Resource Optimization** - Co-locate pods with specific node types

tip

**Scheduling Strategy:** Utilize affinity rules to optimize resource utilization and improve availability. Configure separate affinity rules for main, worker, and webhook nodes to achieve optimal performance.

warning

**Configuration Deprecation:** The top-level `affinity` field is deprecated. Implement specific affinity configurations under `main`, `worker`, and `webhook` blocks for enhanced control.

### Enhanced Persistence Support[​](#enhanced-persistence-support "Direct link to Enhanced Persistence Support")

* **Multi-Node Persistence** - Complete persistence solution for main, worker, and webhook nodes
* **StatefulSet Integration** - Automatic StatefulSet selection for optimal persistence configuration
* **Autoscaling Compatibility** - ReadWriteMany support for dynamic autoscaling deployments
* **Flexible Storage Options** - Custom storage classes, existing PVC integration, and volume annotations
* **Access Mode Optimization** - ReadWriteOnce for StatefulSets, ReadWriteMany for autoscaling scenarios

info

**Persistence Architecture:** Main nodes store workflows and configuration data, while worker nodes maintain npm packages for accelerated startup times. Webhook nodes utilize Deployments and do not support persistence.

warning

**Autoscaling Considerations:** Worker nodes configured with `ReadWriteOnce` persistence cannot utilize autoscaling functionality. Implement `ReadWriteMany` for autoscaling or `ReadWriteOnce` with StatefulSets for fixed scaling deployments.

## Unique Features[​](#unique-features "Direct link to Unique Features")

tip

**Distinctive Capabilities:** These exclusive features establish this n8n Helm chart as the premier solution for advanced automation deployments.

### Advanced npm Package Management[​](#advanced-npm-package-management "Direct link to Advanced npm Package Management")

This chart delivers **unparalleled npm package installation capabilities** that distinguish it from all other n8n Helm charts:

* **Custom npm Package Deployment** - Direct installation of any npm package within main and worker pods
* **Community Node Integration** - Seamless deployment of n8n community nodes for extended functionality
* **Private Registry Support** - Comprehensive support for private npm registries with authentication
* **Intelligent Package Management** - Automated package reinstallation for missing dependencies
* **Built-in Module Access** - Configured access to Node.js built-in modules for enhanced Code node capabilities

info

**Package Management Benefits:** This capability enables sophisticated workflow automation by facilitating custom npm packages and community node integration.

### External Task Runners (Exclusive Feature)[​](#external-task-runners-exclusive-feature "Direct link to External Task Runners (Exclusive Feature)")

This represents the **only n8n Helm chart** supporting external task runners, delivering enhanced security and performance:

* **Execution Isolation** - Workflow execution within dedicated sidecar containers
* **Security Enhancement** - Complete separation of execution environment from the main n8n application
* **Resource Isolation** - Dedicated resource allocation for task execution processes
* **Scalability Optimization** - Independent scaling of execution capacity
* **Enterprise-Grade Isolation** - Production-level isolation for sensitive workflow execution

warning

**Enterprise License Requirement:** External task runners are exclusively available in n8n Enterprise. Ensure you possess the appropriate license before implementing this feature.

danger

**License Verification:** External task runners mandate an n8n Enterprise license. Verify your license status before enabling this advanced functionality.

## Deployment Architecture Overview[​](#deployment-architecture-overview "Direct link to Deployment Architecture Overview")

info

**Architecture Selection:** Choose the deployment architecture that optimally aligns with your use case and operational requirements.

The n8n Helm chart supports three primary deployment architectures:

### Single Node Architecture (Default)[​](#single-node-architecture-default "Direct link to Single Node Architecture (Default)")

<!-- -->

tip

**Single Node Applications:** Ideal for development, testing, and small-scale deployments with minimal workflow volumes.

### Queue Mode Architecture (Production)[​](#queue-mode-architecture-production "Direct link to Queue Mode Architecture (Production)")

<!-- -->

info

**Queue Mode Advantages:** Delivers horizontal scaling capabilities, optimized resource utilization, and enhanced reliability for production workloads.

### External Task Runner Architecture[​](#external-task-runner-architecture "Direct link to External Task Runner Architecture")

<!-- -->

tip

**External Runner Benefits:** Provides enhanced security and performance isolation for sensitive workflow execution.

## Implementation Examples[​](#implementation-examples "Direct link to Implementation Examples")

info

**Practical Deployment Patterns:** These examples demonstrate real-world deployment scenarios for various use cases and requirements.

Explore the [comprehensive examples directory](https://github.com/community-charts/examples/tree/main/n8n-examples) for complete deployment scenarios:

* [Workers and Webhooks Configuration](https://github.com/community-charts/examples/tree/main/n8n-examples/workers-and-webhooks-example) - Queue mode with dedicated node architecture
* [Community Nodes Integration](https://github.com/community-charts/examples/tree/main/n8n-examples/community-nodes-packages-example) - Custom npm package deployment
* [External Task Runners Setup](https://github.com/community-charts/examples/tree/main/n8n-examples/internal-and-external-npm-packages-with-external-runner-example) - Isolated execution environment configuration

tip

**Example Implementation:** Study these examples to understand industry best practices and common deployment patterns for optimal results.

## System Maintenance[​](#system-maintenance "Direct link to System Maintenance")

### Upgrade Procedures[​](#upgrade-procedures "Direct link to Upgrade Procedures")

```
# Update the repository to latest version

helm repo update



# Perform system upgrade

helm upgrade my-n8n community-charts/n8n -n <your-namespace>
```

note

**Data Protection:** Always perform comprehensive data backups before upgrading, particularly when modifying database configurations.

warning

**Upgrade Validation:** Conduct thorough upgrade testing in a staging environment before implementing changes in production.

### System Removal[​](#system-removal "Direct link to System Removal")

```
# Remove the n8n deployment

helm uninstall my-n8n -n <your-namespace>



# Optional: Remove persistent volume claims (WARNING: This will permanently delete all data)

kubectl delete pvc -l app.kubernetes.io/instance=my-n8n -n <your-namespace>
```

danger

**Data Loss Warning:** Deleting persistent volume claims will permanently remove all n8n data including workflows, executions, and credentials. Ensure comprehensive backups are available before proceeding.

warning

**Removal Confirmation:** Verify the namespace and release name before uninstalling to prevent accidental data loss.

## Support and Resources[​](#support-and-resources "Direct link to Support and Resources")

info

**Community Support:** We're committed to helping you achieve success with your n8n deployment.

### Support Channels[​](#support-channels "Direct link to Support Channels")

* **GitHub Issues:** [Report bugs or request features](https://github.com/community-charts/helm-charts/issues)
* **Community Discussions:** [Engage with the community](https://github.com/community-charts/helm-charts/discussions)
* **Official Documentation:** [n8n official documentation](https://docs.n8n.io)

tip

**Community Engagement:** Participate in our community discussions to receive assistance from other users and share your deployment experiences.

## Next Steps[​](#next-steps "Direct link to Next Steps")

tip

**Implementation Guide:** Follow these guides sequentially for a comprehensive n8n deployment experience.

* [Configuration Guide](/docs/charts/n8n/configuration.md) - Comprehensive configuration options and parameters
* [Database Setup](/docs/charts/n8n/database-setup.md) - PostgreSQL and external database configuration
* [Queue Mode Setup](/docs/charts/n8n/queue-mode.md) - Distributed execution with Redis integration
* [Storage Configuration](/docs/charts/n8n/storage.md) - Binary data storage and persistence options
* [Monitoring Setup](/docs/charts/n8n/monitoring.md) - Metrics, observability, and alerting configuration
* [Troubleshooting](/docs/charts/n8n/troubleshooting.md) - Common issues, solutions, and diagnostic procedures


---

# Advanced Configuration

This guide covers advanced configuration options for production deployments and specialized use cases.

## Integrations[​](#integrations "Direct link to Integrations")

Outline supports various third-party integrations for enhanced functionality.

### OpenAI Integration[​](#openai-integration "Direct link to OpenAI Integration")

Enable AI-powered features with OpenAI:

```
integrations:

  openAI:

    enabled: true

    url: "https://api.openai.com/v1"

    apiKey: "your-openai-api-key"

    vectorDatabaseUrl: "postgresql://user:pass@host:port/db"
```

### Slack Integration[​](#slack-integration "Direct link to Slack Integration")

Enable Slack notifications and message actions:

```
integrations:

  slack:

    enabled: true

    verificationToken: "your-slack-verification-token"

    appId: "your-slack-app-id"

    messageActions: true
```

### Sentry Integration[​](#sentry-integration "Direct link to Sentry Integration")

Enable error tracking and monitoring:

```
integrations:

  sentry:

    enabled: true

    dsn: "https://your-sentry-dsn"

    tunnel: "https://your-sentry-tunnel"
```

### PDF Export Integration[​](#pdf-export-integration "Direct link to PDF Export Integration")

Enable PDF export functionality:

```
integrations:

  pdfExport:

    enabled: true

    gotenbergUrl: "http://gotenberg:3000"
```

### Iframely Integration[​](#iframely-integration "Direct link to Iframely Integration")

Enable link previews and metadata extraction:

```
integrations:

  iframely:

    enabled: true

    url: "https://iframely.yourdomain.com"

    apiKey: "your-iframely-api-key"
```

### Dropbox Integration[​](#dropbox-integration "Direct link to Dropbox Integration")

Enable Dropbox file integration:

```
integrations:

  dropbox:

    enabled: true

    appKey: "your-dropbox-app-key"
```

## SMTP Configuration[​](#smtp-configuration "Direct link to SMTP Configuration")

Configure email notifications and user invitations.

### Basic SMTP Setup[​](#basic-smtp-setup "Direct link to Basic SMTP Setup")

```
smtp:

  host: "smtp.gmail.com"

  port: 587

  username: "your-email@gmail.com"

  password: "your-app-password"

  fromEmail: "outline@yourdomain.com"

  replyEmail: "no-reply@yourdomain.com"

  secure: true
```

### SMTP with Existing Secret[​](#smtp-with-existing-secret "Direct link to SMTP with Existing Secret")

```
smtp:

  host: "smtp.yourdomain.com"

  port: 587

  username: "outline"

  existingSecret: "outline-smtp-secret"  # Must contain smtp-password key

  fromEmail: "outline@yourdomain.com"

  replyEmail: "no-reply@yourdomain.com"

  secure: true
```

### Advanced SMTP Configuration[​](#advanced-smtp-configuration "Direct link to Advanced SMTP Configuration")

```
smtp:

  host: "smtp.yourdomain.com"

  port: 587

  username: "outline"

  password: "strongpassword"

  fromEmail: "outline@yourdomain.com"

  replyEmail: "no-reply@yourdomain.com"

  secure: true

  tlsCiphers: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384"
```

## Monitoring and Observability[​](#monitoring-and-observability "Direct link to Monitoring and Observability")

### Health Checks[​](#health-checks "Direct link to Health Checks")

Configure custom health check endpoints:

```
livenessProbe:

  httpGet:

    path: /_health

    port: http

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 3



readinessProbe:

  httpGet:

    path: /_health

    port: http

  initialDelaySeconds: 10

  periodSeconds: 5

  timeoutSeconds: 3

  failureThreshold: 3
```

### Prometheus Monitoring[​](#prometheus-monitoring "Direct link to Prometheus Monitoring")

Add Prometheus annotations for monitoring:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "3000"

  prometheus.io/path: "/_health"
```

### Resource Monitoring[​](#resource-monitoring "Direct link to Resource Monitoring")

Configure resource requests and limits:

```
resources:

  limits:

    cpu: "2000m"

    memory: "4Gi"

  requests:

    cpu: "1000m"

    memory: "2Gi"
```

## Security Configuration[​](#security-configuration "Direct link to Security Configuration")

### Pod Security Context[​](#pod-security-context "Direct link to Pod Security Context")

Configure security context for enhanced security:

```
podSecurityContext:

  runAsUser: 1001

  runAsGroup: 1001

  fsGroup: 1001

  fsGroupChangePolicy: OnRootMismatch

  supplementalGroups: []

  sysctls: []



securityContext:

  allowPrivilegeEscalation: false

  readOnlyRootFilesystem: false

  runAsNonRoot: true

  runAsUser: 1001

  runAsGroup: 1001

  capabilities:

    drop:

      - ALL
```

### Network Policies[​](#network-policies "Direct link to Network Policies")

Create network policies for enhanced security:

```
apiVersion: networking.k8s.io/v1

kind: NetworkPolicy

metadata:

  name: outline-network-policy

spec:

  podSelector:

    matchLabels:

      app.kubernetes.io/name: outline

  policyTypes:

  - Ingress

  - Egress

  ingress:

  - from:

    - namespaceSelector:

        matchLabels:

          name: ingress-nginx

    ports:

    - protocol: TCP

      port: 3000

  egress:

  - to:

    - namespaceSelector:

        matchLabels:

          name: postgresql

    ports:

    - protocol: TCP

      port: 5432

  - to:

    - namespaceSelector:

        matchLabels:

          name: redis

    ports:

    - protocol: TCP

      port: 6379
```

## High Availability Configuration[​](#high-availability-configuration "Direct link to High Availability Configuration")

### Multi-Replica Deployment[​](#multi-replica-deployment "Direct link to Multi-Replica Deployment")

```
replicaCount: 3



strategy:

  type: RollingUpdate

  rollingUpdate:

    maxSurge: "25%"

    maxUnavailable: "25%"



affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - outline

        topologyKey: kubernetes.io/hostname
```

### Horizontal Pod Autoscaler[​](#horizontal-pod-autoscaler "Direct link to Horizontal Pod Autoscaler")

```
apiVersion: autoscaling/v2

kind: HorizontalPodAutoscaler

metadata:

  name: outline-hpa

spec:

  scaleTargetRef:

    apiVersion: apps/v1

    kind: Deployment

    name: outline

  minReplicas: 2

  maxReplicas: 10

  metrics:

    - type: Resource

      resource:

        name: memory

        target:

          type: Utilization

          averageUtilization: 80

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70
```

## Custom Environment Variables[​](#custom-environment-variables "Direct link to Custom Environment Variables")

Add custom environment variables:

```
extraEnvVars:

  NODE_ENV: "production"

  TZ: "UTC"

  DEBUG: "false"

  CUSTOM_FEATURE_FLAG: "enabled"
```

### Using Existing Secrets[​](#using-existing-secrets "Direct link to Using Existing Secrets")

Reference existing secrets for environment variables:

```
extraSecretNamesForEnvFrom:

  - my-custom-secret

  - another-secret
```

## Custom Volumes and Volume Mounts[​](#custom-volumes-and-volume-mounts "Direct link to Custom Volumes and Volume Mounts")

Add custom volumes and mounts:

```
volumes:

  - name: custom-config

    configMap:

      name: outline-custom-config

  - name: shared-storage

    persistentVolumeClaim:

      claimName: outline-shared-storage



volumeMounts:

  - name: custom-config

    mountPath: /app/custom-config

    readOnly: true

  - name: shared-storage

    mountPath: /app/shared
```

## Node Selection and Tolerations[​](#node-selection-and-tolerations "Direct link to Node Selection and Tolerations")

### Node Selector[​](#node-selector "Direct link to Node Selector")

```
nodeSelector:

  node-type: application

  environment: production
```

### Tolerations[​](#tolerations "Direct link to Tolerations")

```
tolerations:

  - key: "dedicated"

    operator: "Equal"

    value: "outline"

    effect: "NoSchedule"
```

### Affinity Rules[​](#affinity-rules "Direct link to Affinity Rules")

```
affinity:

  nodeAffinity:

    requiredDuringSchedulingIgnoredDuringExecution:

      nodeSelectorTerms:

      - matchExpressions:

        - key: kubernetes.io/os

          operator: In

          values:

          - linux

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - outline

        topologyKey: kubernetes.io/hostname
```

## Custom Init Containers[​](#custom-init-containers "Direct link to Custom Init Containers")

Add custom init containers:

```
initContainers:

  - name: wait-for-database

    image: postgres:15

    command:

      - /bin/sh

      - -c

      - |

        until pg_isready -h $PGHOST -p $PGPORT -U $PGUSER; do

          echo "Waiting for database..."

          sleep 2

        done

    env:

      - name: PGHOST

        value: "outline-postgresql"

      - name: PGPORT

        value: "5432"

      - name: PGUSER

        value: "outline"

      - name: PGPASSWORD

        valueFrom:

          secretKeyRef:

            name: outline-postgresql

            key: password
```

## Custom Sidecar Containers[​](#custom-sidecar-containers "Direct link to Custom Sidecar Containers")

Add sidecar containers for additional functionality:

```
extraContainers:

  - name: nginx-sidecar

    image: nginx:alpine

    ports:

      - name: nginx

        containerPort: 80

    volumeMounts:

      - name: nginx-config

        mountPath: /etc/nginx/nginx.conf

        subPath: nginx.conf

    resources:

      requests:

        memory: "64Mi"

        cpu: "50m"

      limits:

        memory: "128Mi"

        cpu: "100m"
```

## Service Account Configuration[​](#service-account-configuration "Direct link to Service Account Configuration")

### Custom Service Account[​](#custom-service-account "Direct link to Custom Service Account")

```
serviceAccount:

  create: true

  name: "outline-service-account"

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/outline-role"

    iam.gke.io/gcp-service-account: "outline@project.iam.gserviceaccount.com"
```

## Ingress Advanced Configuration[​](#ingress-advanced-configuration "Direct link to Ingress Advanced Configuration")

### Multiple Hosts and Paths[​](#multiple-hosts-and-paths "Direct link to Multiple Hosts and Paths")

```
ingress:

  enabled: true

  className: nginx

  annotations:

    cert-manager.io/cluster-issuer: letsencrypt-prod

    nginx.ingress.kubernetes.io/ssl-redirect: "true"

    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"



  hosts:

    - host: outline.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

    - host: wiki.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific



  tls:

    - secretName: outline-tls

      hosts:

        - outline.yourdomain.com

        - wiki.yourdomain.com
```

### Custom Ingress Annotations[​](#custom-ingress-annotations "Direct link to Custom Ingress Annotations")

```
ingress:

  enabled: true

  className: nginx

  annotations:

    cert-manager.io/cluster-issuer: letsencrypt-prod

    nginx.ingress.kubernetes.io/ssl-redirect: "true"

    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"

    nginx.ingress.kubernetes.io/proxy-body-size: "50m"

    nginx.ingress.kubernetes.io/proxy-read-timeout: "300"

    nginx.ingress.kubernetes.io/proxy-send-timeout: "300"

    nginx.ingress.kubernetes.io/rate-limit: "100"

    nginx.ingress.kubernetes.io/rate-limit-window: "1m"
```

## Complete Production Example[​](#complete-production-example "Direct link to Complete Production Example")

Here's a comprehensive production configuration:

```
# Production deployment

replicaCount: 3

strategy:

  type: RollingUpdate

  rollingUpdate:

    maxSurge: "25%"

    maxUnavailable: "25%"



secretKeyExternalSecret:

  name: "my-secret-key-secret"

  key: "secret-key"



utilsSecretExternalSecret:

  name: "my-utils-secret-secret"

  key: "utils-secret"



# Image configuration

image:

  repository: outlinewiki/outline

  pullPolicy: IfNotPresent



# Web configuration

web:

  concurrency: 2

  forceHttps: true

  skipSSLVerification: false



# URL and language

url: "https://outline.yourdomain.com"

defaultLanguage: en_US



# Rate limiting

rateLimiter:

  enabled: true

  limit: 100

  window: 60



# Auto updates

autoUpdate:

  enabled: false

  telemetry: false



# Logging

logging:

  level: info

  extraDebug: []



# Resources

resources:

  limits:

    cpu: 2000m

    memory: 4Gi

  requests:

    cpu: 1000m

    memory: 2Gi



# Security

podSecurityContext:

  runAsUser: 1001

  runAsGroup: 1001

  fsGroup: 1001

  fsGroupChangePolicy: OnRootMismatch



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

  runAsNonRoot: true

  runAsUser: 1001

  runAsGroup: 1001



# Ingress

ingress:

  enabled: true

  className: nginx

  annotations:

    cert-manager.io/cluster-issuer: letsencrypt-prod

    nginx.ingress.kubernetes.io/ssl-redirect: "true"

  hosts:

    - host: outline.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: outline-tls

      hosts:

        - outline.yourdomain.com



# Database

postgresql:

  enabled: true

  architecture: replication

  auth:

    username: outline

    password: strongpassword

    database: outline

  primary:

    persistence:

      enabled: true

      size: 50Gi

      storageClass: "fast-ssd"

  readReplicas:

    persistence:

      enabled: true

      size: 50Gi

      storageClass: "fast-ssd"



# Redis

redis:

  enabled: true

  architecture: standalone

  auth:

    enabled: true

  master:

    persistence:

      enabled: true

      size: 8Gi



# Storage

fileStorage:

  mode: s3

  s3:

    bucket: outline-prod

    region: us-east-1

    existingSecret: "outline-s3-secret"

    forcePathStyle: true

    acl: private



# Authentication

auth:

  google:

    enabled: true

    clientId: "your-google-client-id"

    clientSecret: "your-google-client-secret"



# SMTP

smtp:

  host: "smtp.yourdomain.com"

  port: 587

  username: "outline"

  existingSecret: "outline-smtp-secret"

  fromEmail: "outline@yourdomain.com"

  replyEmail: "no-reply@yourdomain.com"

  secure: true



# Integrations

integrations:

  sentry:

    enabled: true

    dsn: "https://your-sentry-dsn"

  slack:

    enabled: true

    verificationToken: "your-slack-token"

    appId: "your-slack-app-id"



# Affinity

affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

    - weight: 100

      podAffinityTerm:

        labelSelector:

          matchExpressions:

          - key: app.kubernetes.io/name

            operator: In

            values:

            - outline

        topologyKey: kubernetes.io/hostname



# Monitoring

podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "3000"
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [troubleshooting common issues](/docs/charts/outline/troubleshooting.md)
* Configure [authentication methods](/docs/charts/outline/authentication.md)
* Set up [storage options](/docs/charts/outline/storage.md)
* Configure [database settings](/docs/charts/outline/database.md)


---

# Authentication Setup

Outline supports multiple authentication methods. This guide covers all available authentication options and their configuration.

## Authentication Methods[​](#authentication-methods "Direct link to Authentication Methods")

Outline supports the following authentication providers:

* **Google**: Google OAuth2 authentication
* **Azure**: Microsoft Entra ID (Azure AD) authentication
* **OIDC**: Generic OpenID Connect authentication
* **Slack**: Slack OAuth authentication
* **GitHub**: GitHub OAuth authentication
* **GitLab**: GitLab OAuth authentication
* **Gitea**: Gitea OAuth authentication
* **Keycloak**: Keycloak OIDC authentication
* **Discord**: Discord OAuth authentication
* **Auth0**: Auth0 OIDC authentication
* **SAML**: SAML 2.0 authentication

## Google Authentication[​](#google-authentication "Direct link to Google Authentication")

Configure Google OAuth2 authentication:

```
auth:

  google:

    enabled: true

    clientId: "your-google-client-id"

    clientSecret: "your-google-client-secret"
```

info

Create a Google OAuth2 application in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials) and configure the redirect URI as `https://your-domain.com/auth/google.callback`.

## Azure Authentication[​](#azure-authentication "Direct link to Azure Authentication")

Configure Microsoft Entra ID (Azure AD) authentication:

```
auth:

  azure:

    enabled: true

    clientId: "your-azure-client-id"

    clientSecret: "your-azure-client-secret"

    resourceAppId: "optional-resource-app-id"  # Optional

    tenantId: "optional-tenant-id"  # Optional
```

tip

For Azure AD, configure the redirect URI as `https://your-domain.com/auth/azure.callback` in your Azure application.

## OpenID Connect (OIDC)[​](#openid-connect-oidc "Direct link to OpenID Connect (OIDC)")

Configure generic OpenID Connect authentication:

```
auth:

  oidc:

    enabled: true

    clientId: "your-client-id"

    clientSecret: "your-client-secret"

    authUri: "https://your-auth-server/auth"

    tokenUri: "https://your-auth-server/token"

    userInfoUri: "https://your-auth-server/userinfo"

    usernameClaim: "preferred_username"

    displayName: "OpenID Connect"

    scopes:

      - openid

      - profile

      - email
```

## Slack Authentication[​](#slack-authentication "Direct link to Slack Authentication")

Configure Slack OAuth authentication:

```
auth:

  slack:

    enabled: true

    clientId: "your-slack-client-id"

    clientSecret: "your-slack-client-secret"
```

info

Create a Slack app in the [Slack API Console](https://api.slack.com/apps) and configure the redirect URI as `https://your-domain.com/auth/slack.callback`.

## GitHub Authentication[​](#github-authentication "Direct link to GitHub Authentication")

Configure GitHub OAuth authentication:

```
auth:

  github:

    enabled: true

    clientId: "your-github-client-id"

    clientSecret: "your-github-client-secret"

    appName: "your-app-name"  # Optional

    appId: "your-app-id"  # Optional

    appPrivateKey: "your-private-key"  # Optional
```

tip

For GitHub Apps, you can also configure GitHub App authentication with additional parameters.

## GitLab Authentication[​](#gitlab-authentication "Direct link to GitLab Authentication")

Configure GitLab OAuth authentication:

```
auth:

  gitlab:

    enabled: true

    clientId: "your-gitlab-client-id"

    clientSecret: "your-gitlab-client-secret"

    baseUrl: "https://gitlab.com"  # Optional, for self-hosted instances
```

## Gitea Authentication[​](#gitea-authentication "Direct link to Gitea Authentication")

Configure Gitea OAuth authentication:

```
auth:

  gitea:

    enabled: true

    clientId: "your-gitea-client-id"

    clientSecret: "your-gitea-client-secret"

    baseUrl: "https://gitea.com"  # Optional, for self-hosted instances
```

## Keycloak Authentication[​](#keycloak-authentication "Direct link to Keycloak Authentication")

Configure Keycloak OIDC authentication:

```
auth:

  keycloak:

    enabled: true

    clientId: "your-keycloak-client-id"

    clientSecret: "your-keycloak-client-secret"

    baseUrl: "https://your-keycloak-server"

    realmName: "your-realm"
```

## Discord Authentication[​](#discord-authentication "Direct link to Discord Authentication")

Configure Discord OAuth authentication:

```
auth:

  discord:

    enabled: true

    clientId: "your-discord-client-id"

    clientSecret: "your-discord-client-secret"

    serverId: "your-server-id"

    serverRoles: []
```

info

Discord authentication requires a server ID and can optionally restrict access to specific server roles.

## Auth0 Authentication[​](#auth0-authentication "Direct link to Auth0 Authentication")

Configure Auth0 OIDC authentication:

```
auth:

  auth0:

    enabled: true

    clientId: "your-auth0-client-id"

    clientSecret: "your-auth0-client-secret"

    baseUrl: "https://your-auth0-domain"
```

## SAML Authentication[​](#saml-authentication "Direct link to SAML Authentication")

Configure SAML 2.0 authentication:

```
auth:

  saml:

    enabled: true

    ssoEndpoint: "https://your-saml-provider/sso"

    cert: "your-saml-certificate"
```

warning

SAML configuration requires the SSO endpoint URL and the certificate from your SAML identity provider.

## Multiple Authentication Methods[​](#multiple-authentication-methods "Direct link to Multiple Authentication Methods")

You can enable multiple authentication methods simultaneously. Users will see all enabled options on the login page:

```
auth:

  google:

    enabled: true

    clientId: "your-google-client-id"

    clientSecret: "your-google-client-secret"



  github:

    enabled: true

    clientId: "your-github-client-id"

    clientSecret: "your-github-client-secret"



  slack:

    enabled: true

    clientId: "your-slack-client-id"

    clientSecret: "your-slack-client-secret"
```

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically sets the following environment variables based on your authentication configuration:

| Variable               | Description                | Source                     |
| ---------------------- | -------------------------- | -------------------------- |
| `GOOGLE_CLIENT_ID`     | Google OAuth client ID     | `auth.google.clientId`     |
| `GOOGLE_CLIENT_SECRET` | Google OAuth client secret | `auth.google.clientSecret` |
| `AZURE_CLIENT_ID`      | Azure AD client ID         | `auth.azure.clientId`      |
| `AZURE_CLIENT_SECRET`  | Azure AD client secret     | `auth.azure.clientSecret`  |
| `OIDC_CLIENT_ID`       | OIDC client ID             | `auth.oidc.clientId`       |
| `OIDC_CLIENT_SECRET`   | OIDC client secret         | `auth.oidc.clientSecret`   |
| `SLACK_CLIENT_ID`      | Slack OAuth client ID      | `auth.slack.clientId`      |
| `SLACK_CLIENT_SECRET`  | Slack OAuth client secret  | `auth.slack.clientSecret`  |
| `GITHUB_CLIENT_ID`     | GitHub OAuth client ID     | `auth.github.clientId`     |
| `GITHUB_CLIENT_SECRET` | GitHub OAuth client secret | `auth.github.clientSecret` |

## Common OAuth Provider Setup[​](#common-oauth-provider-setup "Direct link to Common OAuth Provider Setup")

### Google OAuth2 Setup[​](#google-oauth2-setup "Direct link to Google OAuth2 Setup")

1. Go to [Google Cloud Console](https://console.cloud.google.com/apis/credentials)
2. Create a new OAuth 2.0 Client ID
3. Add authorized redirect URIs:
   <!-- -->
   * `https://your-domain.com/auth/google.callback`
4. Copy the Client ID and Client Secret to your values.yaml

### GitHub OAuth Setup[​](#github-oauth-setup "Direct link to GitHub OAuth Setup")

1. Go to [GitHub Developer Settings](https://github.com/settings/developers)
2. Create a new OAuth App
3. Set the Authorization callback URL to:
   <!-- -->
   * `https://your-domain.com/auth/github.callback`
4. Copy the Client ID and Client Secret to your values.yaml

### Slack OAuth Setup[​](#slack-oauth-setup "Direct link to Slack OAuth Setup")

1. Go to [Slack API Console](https://api.slack.com/apps)
2. Create a new app
3. Add OAuth & Permissions
4. Set the Redirect URLs to:
   <!-- -->
   * `https://your-domain.com/auth/slack.callback`
5. Copy the Client ID and Client Secret to your values.yaml

## Troubleshooting Authentication[​](#troubleshooting-authentication "Direct link to Troubleshooting Authentication")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Invalid Redirect URI**: Ensure the redirect URI in your OAuth provider matches exactly
2. **Client ID/Secret Errors**: Verify credentials are correct and the application is properly configured
3. **CORS Issues**: Ensure your domain is properly configured in the OAuth provider
4. **SSL Certificate Issues**: Use proper SSL certificates for production

### Debug Mode[​](#debug-mode "Direct link to Debug Mode")

Enable debug logging for authentication issues:

```
logging:

  level: debug

  extraDebug:

    - http

    - router
```

### Testing Authentication[​](#testing-authentication "Direct link to Testing Authentication")

1. **Check Environment Variables**:

   ```
   kubectl exec -it <pod-name> -- env | grep -E "(GOOGLE|AZURE|OIDC|SLACK|GITHUB)"
   ```

2. **Check Application Logs**:

   ```
   kubectl logs <pod-name> | grep -i auth
   ```

3. **Verify Secrets**:

   ```
   kubectl get secret <release-name>-auth-secret -o yaml
   ```

## Security Considerations[​](#security-considerations "Direct link to Security Considerations")

warning

* Store OAuth credentials securely using Kubernetes Secrets
* Use HTTPS in production
* Regularly rotate client secrets
* Implement proper RBAC for access control

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Configure [storage options](/docs/charts/outline/storage.md)
* Set up [database configuration](/docs/charts/outline/database.md)
* Explore [advanced configuration options](/docs/charts/outline/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/outline/troubleshooting.md)


---

# Configuration Guide

This guide covers the essential configuration options for deploying Outline using the Helm chart.

## Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

### Image Configuration[​](#image-configuration "Direct link to Image Configuration")

```
image:

  repository: outlinewiki/outline

  tag: ""  # Uses chart appVersion by default

  pullPolicy: IfNotPresent
```

### Service Configuration[​](#service-configuration "Direct link to Service Configuration")

```
service:

  type: ClusterIP

  port: 3000

  name: http

  annotations: {}
```

### Deployment Strategy[​](#deployment-strategy "Direct link to Deployment Strategy")

Choose between RollingUpdate and Recreate strategies:

```
strategy:

  type: RollingUpdate  # Recommended for multi-replica deployments

  rollingUpdate:

    maxSurge: "25%"

    maxUnavailable: "25%"
```

tip

Use `RollingUpdate` for production deployments with multiple replicas to ensure zero-downtime updates.

## Web Configuration[​](#web-configuration "Direct link to Web Configuration")

Configure web server settings:

```
web:

  concurrency: 1

  forceHttps: true

  skipSSLVerification: false
```

info

* **`concurrency`**: Number of worker processes (1-10)
* **`forceHttps`**: Redirect HTTP to HTTPS
* **`skipSSLVerification`**: Allow insecure connections (development only)

## URL Configuration[​](#url-configuration "Direct link to URL Configuration")

Set the application URL:

```
url: "https://outline.yourdomain.com"
```

tip

If not set, the URL will be auto-generated from ingress configuration or service definition.

## Language and Localization[​](#language-and-localization "Direct link to Language and Localization")

Configure default language:

```
defaultLanguage: en_US
```

Available languages: `en_US`, `en_GB`, `de_DE`, `fr_FR`, `es_ES`, `it_IT`, `ja_JP`, `ko_KR`, `pt_BR`, `ru_RU`, `tr_TR`, `zh_CN`, `zh_TW`

## Rate Limiting[​](#rate-limiting "Direct link to Rate Limiting")

Enable rate limiting for API protection:

```
rateLimiter:

  enabled: true

  limit: 100

  window: 60
```

## Auto Update Configuration[​](#auto-update-configuration "Direct link to Auto Update Configuration")

Configure automatic updates:

```
autoUpdate:

  enabled: false

  telemetry: false
```

warning

Disable auto updates in production to maintain control over your deployment.

## Logging Configuration[​](#logging-configuration "Direct link to Logging Configuration")

Configure application logging:

```
logging:

  level: info  # error, warn, info, http, verbose, debug, silly

  extraDebug: []  # Available modules: lifecycle, http, editor, router, collaboration, misc, store, plugins, policies
```

## Resource Management[​](#resource-management "Direct link to Resource Management")

Set resource requests and limits:

```
resources:

  limits:

    cpu: 1000m

    memory: 2Gi

  requests:

    cpu: 500m

    memory: 1Gi
```

## Health Checks[​](#health-checks "Direct link to Health Checks")

Configure liveness and readiness probes:

```
livenessProbe:

  httpGet:

    path: /_health

    port: http

  initialDelaySeconds: 10

  periodSeconds: 30

  timeoutSeconds: 3

  failureThreshold: 5



readinessProbe:

  httpGet:

    path: /_health

    port: http

  initialDelaySeconds: 10

  periodSeconds: 30

  timeoutSeconds: 3

  failureThreshold: 5
```

## Ingress Configuration[​](#ingress-configuration "Direct link to Ingress Configuration")

Enable ingress for external access:

```
ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

    cert-manager.io/cluster-issuer: letsencrypt-prod

  hosts:

    - host: outline.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: outline-tls

      hosts:

        - outline.yourdomain.com
```

## Security Context[​](#security-context "Direct link to Security Context")

Configure security settings:

```
podSecurityContext:

  fsGroup: 1001

  fsGroupChangePolicy: OnRootMismatch



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

  readOnlyRootFilesystem: false

  runAsNonRoot: true

  runAsUser: 1001

  runAsGroup: 1001
```

## Service Account[​](#service-account "Direct link to Service Account")

Configure service account settings:

```
serviceAccount:

  create: true

  automount: true

  name: ""

  annotations:

    eks.amazonaws.com/role-arn: "arn:aws:iam::123456789012:role/outline-role"
```

## Complete Example[​](#complete-example "Direct link to Complete Example")

Here's a complete configuration example for a production deployment:

```
# Basic deployment

replicaCount: 2

strategy:

  type: RollingUpdate

  rollingUpdate:

    maxSurge: "25%"

    maxUnavailable: "25%"



# Image configuration

image:

  repository: outlinewiki/outline

  pullPolicy: IfNotPresent



# Web configuration

web:

  concurrency: 2

  forceHttps: true

  skipSSLVerification: false



# URL and language

url: "https://outline.yourdomain.com"

defaultLanguage: en_US



# Rate limiting

rateLimiter:

  enabled: true

  limit: 100

  window: 60



# Auto updates

autoUpdate:

  enabled: false

  telemetry: false



# Logging

logging:

  level: info

  extraDebug: []



# Resources

resources:

  limits:

    cpu: 1000m

    memory: 2Gi

  requests:

    cpu: 500m

    memory: 1Gi



# Ingress

ingress:

  enabled: true

  className: nginx

  annotations:

    cert-manager.io/cluster-issuer: letsencrypt-prod

  hosts:

    - host: outline.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: outline-tls

      hosts:

        - outline.yourdomain.com



# Security

podSecurityContext:

  fsGroup: 1001

  fsGroupChangePolicy: OnRootMismatch



securityContext:

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

  runAsNonRoot: true

  runAsUser: 1001

  runAsGroup: 1001
```

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically sets these environment variables:

| Variable               | Description            | Default        |
| ---------------------- | ---------------------- | -------------- |
| `NODE_ENV`             | Node environment       | `production`   |
| `SECRET_KEY`           | Application secret key | Auto-generated |
| `UTILS_SECRET`         | Utils secret key       | Auto-generated |
| `PORT`                 | Application port       | `3000`         |
| `DEFAULT_LANGUAGE`     | Default language       | `en_US`        |
| `URL`                  | Application URL        | Auto-generated |
| `RATE_LIMITER_ENABLED` | Rate limiter enabled   | `false`        |
| `ENABLE_UPDATES`       | Auto updates enabled   | `false`        |
| `TELEMETRY`            | Telemetry enabled      | `false`        |
| `FORCE_HTTPS`          | Force HTTPS redirect   | `true`         |
| `WEB_CONCURRENCY`      | Worker processes       | `1`            |
| `LOG_LEVEL`            | Logging level          | `info`         |

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [authentication setup](/docs/charts/outline/authentication.md)
* Configure [storage options](/docs/charts/outline/storage.md)
* Set up [database configuration](/docs/charts/outline/database.md)
* Explore [advanced configuration options](/docs/charts/outline/advanced-configuration.md)


---

# Database Configuration

Outline requires a PostgreSQL database for storing application data. This guide covers both built-in and external database configuration options.

## Database Options[​](#database-options "Direct link to Database Options")

Outline supports two database deployment modes:

* **Built-in PostgreSQL**: Deploy PostgreSQL as part of the Helm chart
* **External PostgreSQL**: Connect to an existing PostgreSQL instance

## Built-in PostgreSQL[​](#built-in-postgresql "Direct link to Built-in PostgreSQL")

The chart includes a built-in PostgreSQL deployment using Bitnami's PostgreSQL chart.

### Basic Built-in PostgreSQL[​](#basic-built-in-postgresql "Direct link to Basic Built-in PostgreSQL")

```
postgresql:

  enabled: true

  architecture: standalone



  auth:

    username: outline

    password: strongpassword

    database: outline



  primary:

    persistence:

      enabled: true

      size: 8Gi
```

### Advanced Built-in PostgreSQL[​](#advanced-built-in-postgresql "Direct link to Advanced Built-in PostgreSQL")

```
postgresql:

  enabled: true

  architecture: standalone



  auth:

    username: outline

    password: strongpassword

    database: outline



  primary:

    persistence:

      enabled: true

      size: 20Gi

      storageClass: "fast-ssd"

      existingClaim: ""  # Use existing PVC



    service:

      ports:

        postgresql: 5432
```

### High Availability PostgreSQL[​](#high-availability-postgresql "Direct link to High Availability PostgreSQL")

For production deployments with high availability:

```
postgresql:

  enabled: true

  architecture: replication



  auth:

    username: outline

    password: strongpassword

    database: outline



  primary:

    persistence:

      enabled: true

      size: 50Gi

      storageClass: "fast-ssd"



  readReplicas:

    persistence:

      enabled: true

      size: 50Gi

      storageClass: "fast-ssd"
```

## External PostgreSQL[​](#external-postgresql "Direct link to External PostgreSQL")

Connect to an existing PostgreSQL instance outside the cluster.

### Basic External PostgreSQL[​](#basic-external-postgresql "Direct link to Basic External PostgreSQL")

```
postgresql:

  enabled: false



externalPostgresql:

  host: "your-postgresql-host"

  port: 5432

  database: outline

  username: outline

  password: strongpassword
```

### External PostgreSQL with Existing Secret[​](#external-postgresql-with-existing-secret "Direct link to External PostgreSQL with Existing Secret")

Use an existing Kubernetes secret for database credentials:

```
postgresql:

  enabled: false



externalPostgresql:

  host: "your-postgresql-host"

  port: 5432

  database: outline

  username: outline

  existingSecret: "my-postgresql-secret"

  passwordSecretKey: "postgres-password"
```

### External PostgreSQL Examples[​](#external-postgresql-examples "Direct link to External PostgreSQL Examples")

#### AWS RDS[​](#aws-rds "Direct link to AWS RDS")

```
postgresql:

  enabled: false



externalPostgresql:

  host: "outline-db.cluster-xyz.us-east-1.rds.amazonaws.com"

  port: 5432

  database: outline

  username: outline

  existingSecret: "outline-rds-secret"

  passwordSecretKey: "postgres-password"
```

#### Google Cloud SQL[​](#google-cloud-sql "Direct link to Google Cloud SQL")

```
postgresql:

  enabled: false



externalPostgresql:

  host: "outline-db.xyz.us-central1.sql.goog"

  port: 5432

  database: outline

  username: outline

  existingSecret: "outline-cloudsql-secret"

  passwordSecretKey: "postgres-password"
```

#### Azure Database for PostgreSQL[​](#azure-database-for-postgresql "Direct link to Azure Database for PostgreSQL")

```
postgresql:

  enabled: false



externalPostgresql:

  host: "outline-db.postgres.database.azure.com"

  port: 5432

  database: outline

  username: "outline@outline-db"

  existingSecret: "outline-azure-secret"

  passwordSecretKey: "postgres-password"
```

## Database Configuration[​](#database-configuration-1 "Direct link to Database Configuration")

Configure database connection settings:

```
database:

  connectionPoolMin: "5"

  connectionPoolMax: "20"

  sslMode: "require"  # disable, allow, require, prefer, verify-ca, verify-full
```

### SSL Configuration[​](#ssl-configuration "Direct link to SSL Configuration")

Configure SSL for database connections:

```
database:

  connectionPoolMin: "5"

  connectionPoolMax: "20"

  sslMode: "verify-full"  # For production with SSL certificates
```

info

SSL modes:

* `disable`: No SSL
* `allow`: Try SSL, fallback to non-SSL
* `require`: Require SSL
* `prefer`: Prefer SSL, fallback to non-SSL
* `verify-ca`: Verify server certificate
* `verify-full`: Verify server certificate and hostname

## Redis Configuration[​](#redis-configuration "Direct link to Redis Configuration")

Outline uses Redis for caching and session storage.

### Built-in Redis[​](#built-in-redis "Direct link to Built-in Redis")

```
redis:

  enabled: true

  architecture: standalone



  auth:

    enabled: true



  master:

    persistence:

      enabled: true

      size: 8Gi
```

### External Redis[​](#external-redis "Direct link to External Redis")

```
redis:

  enabled: false



externalRedis:

  host: "your-redis-host"

  port: 6379

  username: "default"

  password: "your-password"

  existingSecret: "my-redis-secret"

  usernameSecretKey: "redis-username"

  passwordSecretKey: "redis-password"
```

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically sets these environment variables based on your database configuration:

| Variable                       | Description         | Source                                                                     |
| ------------------------------ | ------------------- | -------------------------------------------------------------------------- |
| `PGUSER`                       | PostgreSQL username | `postgresql.auth.username` or `externalPostgresql.username`                |
| `PGPASSWORD`                   | PostgreSQL password | Secret reference                                                           |
| `PGPORT`                       | PostgreSQL port     | `postgresql.primary.service.ports.postgresql` or `externalPostgresql.port` |
| `PGHOST`                       | PostgreSQL host     | `postgresql.primary.service.name` or `externalPostgresql.host`             |
| `PGDATABASE`                   | PostgreSQL database | `postgresql.auth.database` or `externalPostgresql.database`                |
| `DATABASE_URL`                 | Full database URL   | Auto-generated from above variables                                        |
| `DATABASE_CONNECTION_POOL_MIN` | Min connections     | `database.connectionPoolMin`                                               |
| `DATABASE_CONNECTION_POOL_MAX` | Max connections     | `database.connectionPoolMax`                                               |
| `PGSSLMODE`                    | SSL mode            | `database.sslMode`                                                         |
| `REDIS_USERNAME`               | Redis username      | `externalRedis.username`                                                   |
| `REDIS_PASSWORD`               | Redis password      | Secret reference                                                           |
| `REDIS_HOST`                   | Redis host          | `redis.master.service.name` or `externalRedis.host`                        |
| `REDIS_PORT`                   | Redis port          | `redis.master.service.ports.redis` or `externalRedis.port`                 |
| `REDIS_URL`                    | Redis URL           | Auto-generated (when auth disabled)                                        |

## Database Migration[​](#database-migration "Direct link to Database Migration")

### From Built-in to External[​](#from-built-in-to-external "Direct link to From Built-in to External")

1. **Backup existing data**:

   ```
   # Backup from built-in PostgreSQL

   kubectl exec -it <postgresql-pod> -- pg_dump -U outline outline > outline-backup.sql
   ```

2. **Restore to external database**:

   ```
   # Restore to external PostgreSQL

   psql -h external-host -U outline -d outline < outline-backup.sql
   ```

3. **Update configuration**:

   ```
   postgresql:

     enabled: false



   externalPostgresql:

     host: "external-host"

     port: 5432

     database: outline

     username: outline

     existingSecret: "external-postgresql-secret"

     passwordSecretKey: "postgres-password"
   ```

### From External to Built-in[​](#from-external-to-built-in "Direct link to From External to Built-in")

1. **Backup external database**:

   ```
   pg_dump -h external-host -U outline outline > outline-backup.sql
   ```

2. **Update configuration**:

   ```
   postgresql:

     enabled: true

     auth:

       username: outline

       password: strongpassword

       database: outline



   externalPostgresql:

     host: ""
   ```

3. **Restore to built-in database**:

   ```
   kubectl exec -i <postgresql-pod> -- psql -U outline outline < outline-backup.sql
   ```

## Database Backup and Recovery[​](#database-backup-and-recovery "Direct link to Database Backup and Recovery")

### Automated Backups[​](#automated-backups "Direct link to Automated Backups")

Create a CronJob for automated database backups:

```
apiVersion: batch/v1

kind: CronJob

metadata:

  name: outline-db-backup

spec:

  schedule: "0 2 * * *"  # Daily at 2 AM

  jobTemplate:

    spec:

      template:

        spec:

          containers:

          - name: backup

            image: postgres:15

            command:

            - /bin/sh

            - -c

            - |

              pg_dump -h $PGHOST -U $PGUSER -d $PGDATABASE > /backup/outline-$(date +%Y%m%d).sql

            env:

            - name: PGHOST

              value: "outline-postgresql"

            - name: PGUSER

              value: "outline"

            - name: PGPASSWORD

              valueFrom:

                secretKeyRef:

                  name: outline-postgresql

                  key: password

            - name: PGDATABASE

              value: "outline"

            volumeMounts:

            - name: backup-storage

              mountPath: /backup

          volumes:

          - name: backup-storage

            persistentVolumeClaim:

              claimName: outline-backup-storage

          restartPolicy: OnFailure
```

### Manual Backup[​](#manual-backup "Direct link to Manual Backup")

```
# Backup built-in PostgreSQL

kubectl exec -it outline-postgresql-0 -- pg_dump -U outline outline > outline-backup.sql



# Backup external PostgreSQL

pg_dump -h your-host -U outline outline > outline-backup.sql
```

### Restore from Backup[​](#restore-from-backup "Direct link to Restore from Backup")

```
# Restore to built-in PostgreSQL

kubectl exec -i outline-postgresql-0 -- psql -U outline outline < outline-backup.sql



# Restore to external PostgreSQL

psql -h your-host -U outline outline < outline-backup.sql
```

## Troubleshooting Database Issues[​](#troubleshooting-database-issues "Direct link to Troubleshooting Database Issues")

### Common Problems[​](#common-problems "Direct link to Common Problems")

1. **Connection Refused**: Check database host, port, and network connectivity
2. **Authentication Failed**: Verify username, password, and database name
3. **SSL Issues**: Check SSL mode and certificate configuration
4. **Connection Pool Exhausted**: Increase connection pool limits

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check database environment variables

kubectl exec -it <pod-name> -- env | grep -E "(PG|DATABASE)"



# Test database connectivity

kubectl exec -it <pod-name> -- psql $DATABASE_URL -c "SELECT version();"



# Check Redis connectivity

kubectl exec -it <pod-name> -- redis-cli -h $REDIS_HOST -p $REDIS_PORT ping



# Check PostgreSQL logs

kubectl logs -f deployment/outline-postgresql



# Check Redis logs

kubectl logs -f deployment/outline-redis-master
```

### Database Monitoring[​](#database-monitoring "Direct link to Database Monitoring")

Add monitoring annotations for database tracking:

```
postgresql:

  primary:

    persistence:

      annotations:

        monitoring.kubernetes.io/enabled: "true"

        backup.kubernetes.io/schedule: "daily"
```

## Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

### Connection Pooling[​](#connection-pooling "Direct link to Connection Pooling")

Optimize connection pool settings based on your workload:

```
database:

  connectionPoolMin: "10"  # For high-traffic applications

  connectionPoolMax: "50"  # Adjust based on database capacity
```

### PostgreSQL Tuning[​](#postgresql-tuning "Direct link to PostgreSQL Tuning")

For built-in PostgreSQL, consider these optimizations:

```
postgresql:

  primary:

    extraEnvVars:

      POSTGRES_SHARED_PRELOAD_LIBRARIES: "pg_stat_statements"



    extraVolumes:

      - name: postgresql-config

        configMap:

          name: postgresql-config



    extraVolumeMounts:

      - name: postgresql-config

        mountPath: /opt/bitnami/postgresql/conf/postgresql.conf

        subPath: postgresql.conf
```

## Security Considerations[​](#security-considerations "Direct link to Security Considerations")

warning

* Use strong passwords for database users
* Enable SSL for database connections in production
* Use existing secrets for database credentials
* Implement proper network policies
* Regular database backups
* Monitor database access logs

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Configure [authentication methods](/docs/charts/outline/authentication.md)
* Set up [storage options](/docs/charts/outline/storage.md)
* Explore [advanced configuration options](/docs/charts/outline/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/outline/troubleshooting.md)


---

# Storage Configuration

Outline supports multiple file storage backends for storing documents, images, and other files. This guide covers all available storage options and their configuration.

## Storage Modes[​](#storage-modes "Direct link to Storage Modes")

Outline supports two storage modes:

* **Local**: Files stored on local filesystem with optional persistence
* **S3**: Files stored in S3-compatible object storage

## Local File Storage[​](#local-file-storage "Direct link to Local File Storage")

Local storage stores files on the container's filesystem with optional Kubernetes persistence.

### Basic Local Storage[​](#basic-local-storage "Direct link to Basic Local Storage")

```
fileStorage:

  mode: local

  local:

    rootDir: /var/lib/outline/data

    persistence:

      enabled: false
```

### Local Storage with Persistence[​](#local-storage-with-persistence "Direct link to Local Storage with Persistence")

Enable persistent storage for local file storage:

```
fileStorage:

  mode: local

  local:

    rootDir: /var/lib/outline/data

    persistence:

      enabled: true

      size: 8Gi

      accessModes:

        - ReadWriteOnce

      storageClass: "standard"
```

### Advanced Local Storage Configuration[​](#advanced-local-storage-configuration "Direct link to Advanced Local Storage Configuration")

```
fileStorage:

  mode: local

  local:

    rootDir: /var/lib/outline/data

    persistence:

      enabled: true

      size: 20Gi

      accessModes:

        - ReadWriteOnce

      storageClass: "fast-ssd"

      existingClaim: ""  # Use existing PVC

      annotations:

        backup.kubernetes.io/enabled: "true"
```

## S3-Compatible Storage[​](#s3-compatible-storage "Direct link to S3-Compatible Storage")

S3 storage allows you to use any S3-compatible object storage service.

### Basic S3 Configuration[​](#basic-s3-configuration "Direct link to Basic S3 Configuration")

```
fileStorage:

  mode: s3

  s3:

    bucket: outline

    region: us-east-1

    accessKeyId: "your-access-key"

    secretAccessKey: "your-secret-key"

    forcePathStyle: true

    acl: private
```

### S3 with Custom Endpoint[​](#s3-with-custom-endpoint "Direct link to S3 with Custom Endpoint")

For S3-compatible services like MinIO, Backblaze B2, or DigitalOcean Spaces:

```
fileStorage:

  mode: s3

  s3:

    bucket: outline

    region: us-east-1

    bucketUrl: "https://your-s3-compatible-endpoint"

    accessKeyId: "your-access-key"

    secretAccessKey: "your-secret-key"

    forcePathStyle: true

    acl: private
```

### S3 with Existing Secret[​](#s3-with-existing-secret "Direct link to S3 with Existing Secret")

Use an existing Kubernetes secret for S3 credentials:

```
fileStorage:

  mode: s3

  s3:

    bucket: outline

    region: us-east-1

    existingSecret: "my-s3-secret"  # Must contain access-key-id and secret-access-key keys

    forcePathStyle: true

    acl: private
```

## MinIO Integration[​](#minio-integration "Direct link to MinIO Integration")

The chart includes built-in MinIO support for S3-compatible storage.

### Enable MinIO[​](#enable-minio "Direct link to Enable MinIO")

```
minio:

  enabled: true

  rootUser: admin

  rootPassword: strongpassword



  persistence:

    enabled: true

    size: 40Gi

    storageClass: "standard"



  ingress:

    enabled: true

    hosts:

      - minio.yourdomain.com
```

### MinIO with Custom Configuration[​](#minio-with-custom-configuration "Direct link to MinIO with Custom Configuration")

```
minio:

  enabled: true

  mode: standalone

  rootUser: admin

  rootPassword: strongpassword



  replicas: 1

  drivesPerNode: 1

  pools: 1



  persistence:

    enabled: true

    size: 100Gi

    storageClass: "fast-ssd"



  resources:

    requests:

      memory: 1Gi



  ingress:

    enabled: true

    hosts:

      - minio.yourdomain.com



  consoleIngress:

    enabled: true

    hosts:

      - minio-console.yourdomain.com
```

### MinIO Buckets and Policies[​](#minio-buckets-and-policies "Direct link to MinIO Buckets and Policies")

Configure MinIO buckets and access policies:

```
minio:

  enabled: true

  rootUser: admin

  rootPassword: strongpassword



  buckets:

    - name: outline

      policy: none

      purge: false

      versioning: false



  policies:

    - name: outline-policy

      statements:

        - actions:

            - "s3:AbortMultipartUpload"

            - "s3:GetObject"

            - "s3:DeleteObject"

            - "s3:PutObject"

            - "s3:ListMultipartUploadParts"

          resources:

            - "arn:aws:s3:::outline/*"

        - actions:

            - "s3:GetBucketLocation"

            - "s3:ListBucket"

            - "s3:ListBucketMultipartUploads"

          resources:

            - "arn:aws:s3:::outline"



  users:

    - accessKey: outline

      secretKey: Change_Me

      policy: outline-policy
```

## File Upload Limits[​](#file-upload-limits "Direct link to File Upload Limits")

Configure file upload size limits:

```
fileStorage:

  mode: local  # or s3

  uploadMaxSize: "262144000"  # 250MB in bytes

  importMaxSize: "524288000"  # 500MB for imports

  workspaceImportMaxSize: "1048576000"  # 1GB for workspace imports
```

## Storage Recommendations[​](#storage-recommendations "Direct link to Storage Recommendations")

### Development Environment[​](#development-environment "Direct link to Development Environment")

```
fileStorage:

  mode: local

  local:

    rootDir: /var/lib/outline/data

    persistence:

      enabled: true

      size: 5Gi

      storageClass: "standard"
```

### Production Environment[​](#production-environment "Direct link to Production Environment")

```
fileStorage:

  mode: s3

  s3:

    bucket: outline-prod

    region: us-east-1

    existingSecret: "outline-s3-secret"

    forcePathStyle: true

    acl: private
```

### High Availability Setup[​](#high-availability-setup "Direct link to High Availability Setup")

```
fileStorage:

  mode: s3

  s3:

    bucket: outline-ha

    region: us-east-1

    existingSecret: "outline-s3-secret"

    forcePathStyle: true

    acl: private



minio:

  enabled: true

  mode: distributed

  replicas: 4

  drivesPerNode: 2

  pools: 2

  rootUser: admin

  rootPassword: strongpassword
```

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically sets these environment variables based on your storage configuration:

| Variable                                 | Description             | Source                                      |
| ---------------------------------------- | ----------------------- | ------------------------------------------- |
| `FILE_STORAGE`                           | Storage mode            | `fileStorage.mode`                          |
| `FILE_STORAGE_UPLOAD_MAX_SIZE`           | Upload size limit       | `fileStorage.uploadMaxSize`                 |
| `FILE_STORAGE_IMPORT_MAX_SIZE`           | Import size limit       | `fileStorage.importMaxSize`                 |
| `FILE_STORAGE_WORKSPACE_IMPORT_MAX_SIZE` | Workspace import limit  | `fileStorage.workspaceImportMaxSize`        |
| `FILE_STORAGE_LOCAL_ROOT_DIR`            | Local storage directory | `fileStorage.local.rootDir`                 |
| `AWS_ACCESS_KEY_ID`                      | S3 access key           | `fileStorage.s3.accessKeyId` or MinIO       |
| `AWS_SECRET_ACCESS_KEY`                  | S3 secret key           | `fileStorage.s3.secretAccessKey` or MinIO   |
| `AWS_S3_UPLOAD_BUCKET_NAME`              | S3 bucket name          | `fileStorage.s3.bucket` or MinIO            |
| `AWS_REGION`                             | S3 region               | `fileStorage.s3.region`                     |
| `AWS_S3_UPLOAD_BUCKET_URL`               | S3 endpoint URL         | MinIO ingress or `fileStorage.s3.bucketUrl` |
| `AWS_S3_FORCE_PATH_STYLE`                | Force path style        | `fileStorage.s3.forcePathStyle`             |
| `AWS_S3_ACL`                             | S3 ACL                  | `fileStorage.s3.acl`                        |

## Storage Migration[​](#storage-migration "Direct link to Storage Migration")

### From Local to S3[​](#from-local-to-s3 "Direct link to From Local to S3")

1. **Backup existing data**:

   ```
   kubectl exec -it <pod-name> -- tar czf /tmp/outline-backup.tar.gz /var/lib/outline/data

   kubectl cp <pod-name>:/tmp/outline-backup.tar.gz ./outline-backup.tar.gz
   ```

2. **Update configuration**:

   ```
   fileStorage:

     mode: s3

     s3:

       bucket: outline

       region: us-east-1

       existingSecret: "outline-s3-secret"
   ```

3. **Restore data to S3**:

   ```
   # Extract and upload to S3 bucket

   tar xzf outline-backup.tar.gz

   aws s3 sync var/lib/outline/data/ s3://outline/
   ```

### From S3 to Local[​](#from-s3-to-local "Direct link to From S3 to Local")

1. **Download data from S3**:

   ```
   aws s3 sync s3://outline/ ./outline-data/
   ```

2. **Update configuration**:

   ```
   fileStorage:

     mode: local

     local:

       rootDir: /var/lib/outline/data

       persistence:

         enabled: true

         size: 20Gi
   ```

3. **Upload data to pod**:

   ```
   kubectl cp ./outline-data/ <pod-name>:/var/lib/outline/data/
   ```

## Troubleshooting Storage Issues[​](#troubleshooting-storage-issues "Direct link to Troubleshooting Storage Issues")

### Common Problems[​](#common-problems "Direct link to Common Problems")

1. **Permission Denied**: Check file permissions and security context
2. **Storage Full**: Increase PVC size or S3 bucket capacity
3. **S3 Connection Issues**: Verify credentials and endpoint configuration
4. **MinIO Not Accessible**: Check MinIO ingress and service configuration

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check storage configuration

kubectl exec -it <pod-name> -- env | grep -E "(FILE_STORAGE|AWS_)"



# Check local storage

kubectl exec -it <pod-name> -- ls -la /var/lib/outline/data



# Check S3 connectivity

kubectl exec -it <pod-name> -- aws s3 ls s3://outline



# Check MinIO status

kubectl get pods -l app.kubernetes.io/name=minio
```

### Storage Monitoring[​](#storage-monitoring "Direct link to Storage Monitoring")

Add monitoring annotations for storage tracking:

```
fileStorage:

  local:

    persistence:

      annotations:

        monitoring.kubernetes.io/enabled: "true"

        backup.kubernetes.io/schedule: "daily"
```

## Security Considerations[​](#security-considerations "Direct link to Security Considerations")

warning

* Use existing secrets for S3 credentials instead of plain text
* Configure proper bucket policies and ACLs
* Enable encryption at rest for sensitive data
* Use IAM roles when possible instead of access keys

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Set up [database configuration](/docs/charts/outline/database.md)
* Configure [authentication methods](/docs/charts/outline/authentication.md)
* Explore [advanced configuration options](/docs/charts/outline/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/outline/troubleshooting.md)


---

# Troubleshooting

This guide covers common issues and their solutions when deploying Outline using the Helm chart.

## Pod Issues[​](#pod-issues "Direct link to Pod Issues")

### Pod Stuck in Pending State[​](#pod-stuck-in-pending-state "Direct link to Pod Stuck in Pending State")

**Symptoms**: Pod remains in `Pending` status

**Common Causes**:

* Insufficient cluster resources
* PVC binding issues
* Node selector constraints

**Solutions**:

```
# Check pod events

kubectl describe pod <pod-name>



# Check resource availability

kubectl get nodes -o custom-columns="NAME:.metadata.name,CPU:.status.capacity.cpu,MEMORY:.status.capacity.memory"



# Check PVC status

kubectl get pvc



# Check storage class

kubectl get storageclass
```

### Pod CrashLoopBackOff[​](#pod-crashloopbackoff "Direct link to Pod CrashLoopBackOff")

**Symptoms**: Pod repeatedly crashes and restarts

**Common Causes**:

* Database connection issues
* Configuration errors
* Resource constraints

**Solutions**:

```
# Check pod logs

kubectl logs <pod-name> --previous



# Check pod events

kubectl describe pod <pod-name>



# Check resource usage

kubectl top pod <pod-name>
```

### Pod Not Ready[​](#pod-not-ready "Direct link to Pod Not Ready")

**Symptoms**: Pod is running but not ready

**Common Causes**:

* Health check failures
* Database connectivity issues
* Application startup problems

**Solutions**:

```
# Check readiness probe

kubectl describe pod <pod-name> | grep -A 10 "Readiness"



# Check application logs

kubectl logs <pod-name> | grep -i "ready\|health"



# Test health endpoint

kubectl exec -it <pod-name> -- curl -f http://localhost:3000/_health
```

## Database Issues[​](#database-issues "Direct link to Database Issues")

### Database Connection Failed[​](#database-connection-failed "Direct link to Database Connection Failed")

**Symptoms**: Application cannot connect to PostgreSQL

**Common Causes**:

* Database not running
* Incorrect credentials
* Network connectivity issues

**Solutions**:

```
# Check database pod status

kubectl get pods -l app.kubernetes.io/name=postgresql



# Check database logs

kubectl logs -f deployment/outline-postgresql



# Test database connectivity

kubectl exec -it <outline-pod> -- psql $DATABASE_URL -c "SELECT 1;"



# Check database environment variables

kubectl exec -it <outline-pod> -- env | grep -E "(PG|DATABASE)"
```

### Redis Connection Issues[​](#redis-connection-issues "Direct link to Redis Connection Issues")

**Symptoms**: Application cannot connect to Redis

**Common Causes**:

* Redis not running
* Authentication issues
* Network connectivity problems

**Solutions**:

```
# Check Redis pod status

kubectl get pods -l app.kubernetes.io/name=redis



# Check Redis logs

kubectl logs -f deployment/outline-redis-master



# Test Redis connectivity

kubectl exec -it <outline-pod> -- redis-cli -h $REDIS_HOST -p $REDIS_PORT ping



# Check Redis environment variables

kubectl exec -it <outline-pod> -- env | grep -E "(REDIS)"
```

## Storage Issues[​](#storage-issues "Direct link to Storage Issues")

### PVC Binding Issues[​](#pvc-binding-issues "Direct link to PVC Binding Issues")

**Symptoms**: PersistentVolumeClaim remains in `Pending` status

**Common Causes**:

* No available storage class
* Insufficient storage capacity
* Storage class configuration issues

**Solutions**:

```
# Check PVC status

kubectl get pvc



# Check available storage classes

kubectl get storageclass



# Check persistent volumes

kubectl get pv



# Check storage class events

kubectl describe pvc <pvc-name>
```

### S3 Storage Issues[​](#s3-storage-issues "Direct link to S3 Storage Issues")

**Symptoms**: File uploads fail or S3 connectivity issues

**Common Causes**:

* Incorrect S3 credentials
* Network connectivity issues
* S3 bucket permissions

**Solutions**:

```
# Check S3 environment variables

kubectl exec -it <pod-name> -- env | grep -E "(AWS_)"



# Test S3 connectivity

kubectl exec -it <pod-name> -- aws s3 ls s3://your-bucket



# Check S3 credentials

kubectl get secret <release-name>-s3-secret -o yaml



# Verify bucket permissions

kubectl exec -it <pod-name> -- aws s3api get-bucket-acl --bucket your-bucket
```

### MinIO Issues[​](#minio-issues "Direct link to MinIO Issues")

**Symptoms**: MinIO not accessible or configuration problems

**Common Causes**:

* MinIO pod not running
* Ingress configuration issues
* Credential problems

**Solutions**:

```
# Check MinIO pod status

kubectl get pods -l app.kubernetes.io/name=minio



# Check MinIO logs

kubectl logs -f deployment/outline-minio



# Check MinIO service

kubectl get svc -l app.kubernetes.io/name=minio



# Test MinIO connectivity

kubectl exec -it <outline-pod> -- curl -f http://outline-minio:9000
```

## Authentication Issues[​](#authentication-issues "Direct link to Authentication Issues")

### OAuth Provider Problems[​](#oauth-provider-problems "Direct link to OAuth Provider Problems")

**Symptoms**: Users cannot authenticate via OAuth providers

**Common Causes**:

* Incorrect OAuth credentials
* Redirect URI mismatches
* Provider configuration issues

**Solutions**:

```
# Check authentication environment variables

kubectl exec -it <pod-name> -- env | grep -E "(GOOGLE|AZURE|OIDC|SLACK|GITHUB)"



# Check authentication secrets

kubectl get secret <release-name>-auth-secret -o yaml



# Check application logs for auth errors

kubectl logs <pod-name> | grep -i "auth\|oauth\|login"



# Verify redirect URIs in OAuth provider

# Ensure they match: https://your-domain.com/auth/provider.callback
```

### SAML Configuration Issues[​](#saml-configuration-issues "Direct link to SAML Configuration Issues")

**Symptoms**: SAML authentication fails

**Common Causes**:

* Incorrect SAML endpoint
* Certificate issues
* Configuration mismatches

**Solutions**:

```
# Check SAML environment variables

kubectl exec -it <pod-name> -- env | grep -E "(SAML)"



# Verify SAML certificate

kubectl get secret <release-name>-auth-secret -o yaml | grep SAML_CERT



# Check SAML endpoint configuration

kubectl exec -it <pod-name> -- env | grep SAML_SSO_ENDPOINT
```

## Network and Ingress Issues[​](#network-and-ingress-issues "Direct link to Network and Ingress Issues")

### Ingress Not Working[​](#ingress-not-working "Direct link to Ingress Not Working")

**Symptoms**: Cannot access Outline via ingress

**Common Causes**:

* Ingress controller not installed
* Incorrect ingress configuration
* DNS resolution issues

**Solutions**:

```
# Check ingress status

kubectl get ingress



# Check ingress controller

kubectl get pods -n ingress-nginx



# Check ingress events

kubectl describe ingress <ingress-name>



# Test ingress connectivity

curl -I https://your-domain.com/_health



# Check DNS resolution

nslookup your-domain.com
```

### SSL Certificate Issues[​](#ssl-certificate-issues "Direct link to SSL Certificate Issues")

**Symptoms**: SSL certificate errors or HTTPS not working

**Common Causes**:

* Certificate not issued
* Incorrect certificate configuration
* cert-manager issues

**Solutions**:

```
# Check certificate status

kubectl get certificate



# Check cert-manager pods

kubectl get pods -n cert-manager



# Check certificate events

kubectl describe certificate <certificate-name>



# Check TLS secret

kubectl get secret <tls-secret-name> -o yaml
```

## Application Issues[​](#application-issues "Direct link to Application Issues")

### Application Not Starting[​](#application-not-starting "Direct link to Application Not Starting")

**Symptoms**: Outline application fails to start

**Common Causes**:

* Missing environment variables
* Configuration errors
* Resource constraints

**Solutions**:

```
# Check application logs

kubectl logs <pod-name>



# Check environment variables

kubectl exec -it <pod-name> -- env | sort



# Check configuration

kubectl get configmap <release-name>-entrypoint -o yaml



# Check resource usage

kubectl top pod <pod-name>
```

### Performance Issues[​](#performance-issues "Direct link to Performance Issues")

**Symptoms**: Slow application performance

**Common Causes**:

* Insufficient resources
* Database performance issues
* Network latency

**Solutions**:

```
# Check resource usage

kubectl top pod <pod-name>

kubectl top node



# Check database performance

kubectl exec -it <postgresql-pod> -- psql -U outline -d outline -c "SELECT * FROM pg_stat_activity;"



# Check Redis performance

kubectl exec -it <redis-pod> -- redis-cli info memory



# Enable debug logging

kubectl patch deployment <deployment-name> -p '{"spec":{"template":{"spec":{"containers":[{"name":"outline","env":[{"name":"LOG_LEVEL","value":"debug"}]}]}}}}'
```

## Common Error Messages[​](#common-error-messages "Direct link to Common Error Messages")

### "Database connection failed"[​](#database-connection-failed-1 "Direct link to \"Database connection failed\"")

```
# Check database connectivity

kubectl exec -it <pod-name> -- psql $DATABASE_URL -c "SELECT 1;"



# Check database credentials

kubectl get secret <release-name>-postgresql -o yaml



# Verify database URL

kubectl exec -it <pod-name> -- echo $DATABASE_URL
```

### "Redis connection failed"[​](#redis-connection-failed "Direct link to \"Redis connection failed\"")

```
# Check Redis connectivity

kubectl exec -it <pod-name> -- redis-cli -h $REDIS_HOST -p $REDIS_PORT ping



# Check Redis credentials

kubectl get secret <release-name>-redis -o yaml



# Verify Redis URL

kubectl exec -it <pod-name> -- echo $REDIS_URL
```

### "File upload failed"[​](#file-upload-failed "Direct link to \"File upload failed\"")

```
# Check storage configuration

kubectl exec -it <pod-name> -- env | grep -E "(FILE_STORAGE|AWS_)"



# Check S3 connectivity

kubectl exec -it <pod-name> -- aws s3 ls s3://your-bucket



# Check local storage permissions

kubectl exec -it <pod-name> -- ls -la /var/lib/outline/data
```

### "Authentication failed"[​](#authentication-failed "Direct link to \"Authentication failed\"")

```
# Check authentication configuration

kubectl exec -it <pod-name> -- env | grep -E "(GOOGLE|AZURE|OIDC|SLACK|GITHUB)"



# Check authentication secrets

kubectl get secret <release-name>-auth-secret -o yaml



# Check application logs

kubectl logs <pod-name> | grep -i "auth"
```

## Debug Mode[​](#debug-mode "Direct link to Debug Mode")

Enable debug logging for troubleshooting:

```
logging:

  level: debug

  extraDebug:

    - http

    - router

    - store

    - policies
```

Apply debug configuration:

```
# Update deployment with debug logging

kubectl patch deployment <deployment-name> -p '{"spec":{"template":{"spec":{"containers":[{"name":"outline","env":[{"name":"LOG_LEVEL","value":"debug"},{"name":"DEBUG","value":"http,router,store,policies"}]}]}}}}'



# Check debug logs

kubectl logs -f <pod-name>
```

## Monitoring and Logging[​](#monitoring-and-logging "Direct link to Monitoring and Logging")

### Enable Application Monitoring[​](#enable-application-monitoring "Direct link to Enable Application Monitoring")

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "3000"

  prometheus.io/path: "/_health"
```

### Log Aggregation[​](#log-aggregation "Direct link to Log Aggregation")

Configure log aggregation for better debugging:

```
# Add logging sidecar

extraContainers:

  - name: log-aggregator

    image: fluent/fluent-bit:latest

    volumeMounts:

      - name: varlog

        mountPath: /var/log

      - name: varlibdockercontainers

        mountPath: /var/lib/docker/containers

        readOnly: true

    resources:

      requests:

        memory: "64Mi"

        cpu: "50m"

      limits:

        memory: "128Mi"

        cpu: "100m"
```

## Recovery Procedures[​](#recovery-procedures "Direct link to Recovery Procedures")

### Database Recovery[​](#database-recovery "Direct link to Database Recovery")

```
# Backup database

kubectl exec -it <postgresql-pod> -- pg_dump -U outline outline > outline-backup.sql



# Restore database

kubectl exec -i <postgresql-pod> -- psql -U outline outline < outline-backup.sql
```

### Application Recovery[​](#application-recovery "Direct link to Application Recovery")

```
# Restart application

kubectl rollout restart deployment <deployment-name>



# Check rollout status

kubectl rollout status deployment <deployment-name>



# Rollback if needed

kubectl rollout undo deployment <deployment-name>
```

### Storage Recovery[​](#storage-recovery "Direct link to Storage Recovery")

```
# Backup local storage

kubectl exec -it <pod-name> -- tar czf /tmp/outline-data.tar.gz /var/lib/outline/data

kubectl cp <pod-name>:/tmp/outline-data.tar.gz ./outline-data-backup.tar.gz



# Restore local storage

kubectl cp ./outline-data-backup.tar.gz <pod-name>:/tmp/

kubectl exec -it <pod-name> -- tar xzf /tmp/outline-data-backup.tar.gz -C /
```

## Getting Help[​](#getting-help "Direct link to Getting Help")

### Collecting Debug Information[​](#collecting-debug-information "Direct link to Collecting Debug Information")

```
# Collect all relevant information

kubectl get all -l app.kubernetes.io/name=outline

kubectl get pvc -l app.kubernetes.io/name=outline

kubectl get secrets -l app.kubernetes.io/name=outline

kubectl describe pod <pod-name>

kubectl logs <pod-name> --previous

kubectl exec -it <pod-name> -- env | sort
```

### Useful Commands[​](#useful-commands "Direct link to Useful Commands")

```
# Check all resources

kubectl get all -l app.kubernetes.io/name=outline



# Check events

kubectl get events --sort-by='.lastTimestamp'



# Check resource usage

kubectl top pods -l app.kubernetes.io/name=outline



# Check configuration

kubectl get configmap -l app.kubernetes.io/name=outline

kubectl get secret -l app.kubernetes.io/name=outline
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Review [configuration options](/docs/charts/outline/configuration.md)
* Check [authentication setup](/docs/charts/outline/authentication.md)
* Verify [storage configuration](/docs/charts/outline/storage.md)
* Confirm [database settings](/docs/charts/outline/database.md)
* Explore [advanced configuration](/docs/charts/outline/advanced-configuration.md)


---

# Outline Chart Usage Guide

[Outline](https://www.getoutline.com) is a modern team knowledge base and wiki. This chart lets you deploy Outline on Kubernetes for collaborative documentation and knowledge sharing.

* **Official Website:** <https://www.getoutline.com>
* **GitHub Repository:** <https://github.com/outline/outline>
* **Documentation:** <https://docs.getoutline.com/s/guide>
* **ArtifactHub:** [Outline Helm Chart](https://artifacthub.io/packages/helm/community-charts/outline)

## Why use this chart?[​](#why-use-this-chart "Direct link to Why use this chart?")

* Deploy Outline for your team or organization on Kubernetes
* Community-maintained and up-to-date
* Modern, user-friendly wiki platform
* Support for multiple authentication providers
* Flexible storage options (local and S3)
* Built-in PostgreSQL and Redis support

## Quick Start[​](#quick-start "Direct link to Quick Start")

### Prerequisites[​](#prerequisites "Direct link to Prerequisites")

* Kubernetes cluster (v1.23+)
* Helm 3.x
* Ingress controller (optional, for external access)
* Storage class (for persistent storage)

### Installation[​](#installation "Direct link to Installation")

1. **Add the Helm repository**:

   ```
   helm repo add community-charts https://community-charts.github.io/helm-charts

   helm repo update
   ```

2. **Install Outline**:

   ```
   helm install my-outline community-charts/outline -n <your-namespace>
   ```

3. **Check the deployment**:

   ```
   kubectl get pods -l app.kubernetes.io/name=outline

   kubectl get svc -l app.kubernetes.io/name=outline
   ```

## Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

### Minimal Configuration[​](#minimal-configuration "Direct link to Minimal Configuration")

Create a `values.yaml` file with basic settings:

```
# Basic deployment

replicaCount: 1



# Enable built-in PostgreSQL

postgresql:

  enabled: true

  auth:

    username: outline

    password: strongpassword

    database: outline

  primary:

    persistence:

      enabled: true

      size: 8Gi



# Enable built-in Redis

redis:

  enabled: true

  auth:

    enabled: true

  master:

    persistence:

      enabled: true

      size: 8Gi



# Local file storage

fileStorage:

  mode: local

  local:

    persistence:

      enabled: true

      size: 8Gi



# Ingress for external access

ingress:

  enabled: true

  className: nginx

  hosts:

    - host: outline.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific
```

### Install with Custom Values[​](#install-with-custom-values "Direct link to Install with Custom Values")

```
helm install my-outline community-charts/outline \

  -f values.yaml \

  -n <your-namespace>
```

## First-Time Setup[​](#first-time-setup "Direct link to First-Time Setup")

### 1. Access the Application[​](#1-access-the-application "Direct link to 1. Access the Application")

After installation, access Outline through your configured ingress or port-forward:

```
# Port-forward for local access

kubectl port-forward svc/my-outline 3000:3000
```

Then visit `http://localhost:3000` in your browser.

### 2. Create Your First User[​](#2-create-your-first-user "Direct link to 2. Create Your First User")

On first access, you'll be prompted to create an admin user:

1. Enter your email address
2. Choose a password
3. Complete the setup process

### 3. Configure Authentication[​](#3-configure-authentication "Direct link to 3. Configure Authentication")

Outline supports multiple authentication methods. Configure them in your `values.yaml`:

```
auth:

  google:

    enabled: true

    clientId: "your-google-client-id"

    clientSecret: "your-google-client-secret"



  github:

    enabled: true

    clientId: "your-github-client-id"

    clientSecret: "your-github-client-secret"
```

### 4. Set Up Email Notifications[​](#4-set-up-email-notifications "Direct link to 4. Set Up Email Notifications")

Configure SMTP for user invitations and notifications:

```
smtp:

  host: "smtp.gmail.com"

  port: 587

  username: "your-email@gmail.com"

  password: "your-app-password"

  fromEmail: "outline@yourdomain.com"

  replyEmail: "no-reply@yourdomain.com"

  secure: true
```

## Common Operations[​](#common-operations "Direct link to Common Operations")

### Upgrading Outline[​](#upgrading-outline "Direct link to Upgrading Outline")

```
# Update the repository

helm repo update



# Upgrade the release

helm upgrade my-outline community-charts/outline -n <your-namespace>
```

### Scaling the Application[​](#scaling-the-application "Direct link to Scaling the Application")

```
# Scale to multiple replicas

helm upgrade my-outline community-charts/outline \

  --set replicaCount=3 \

  -n <your-namespace>
```

### Backup and Restore[​](#backup-and-restore "Direct link to Backup and Restore")

#### Database Backup[​](#database-backup "Direct link to Database Backup")

```
# Backup PostgreSQL

kubectl exec -it my-outline-postgresql-0 -- pg_dump -U outline outline > outline-backup.sql
```

#### File Storage Backup[​](#file-storage-backup "Direct link to File Storage Backup")

```
# Backup local files

kubectl exec -it <outline-pod> -- tar czf /tmp/outline-data.tar.gz /var/lib/outline/data

kubectl cp <outline-pod>:/tmp/outline-data.tar.gz ./outline-data-backup.tar.gz
```

### Uninstalling Outline[​](#uninstalling-outline "Direct link to Uninstalling Outline")

```
# Uninstall the release

helm uninstall my-outline -n <your-namespace>



# Remove persistent data (optional)

kubectl delete pvc -l app.kubernetes.io/name=outline
```

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically configures these key environment variables:

| Variable       | Description           | Default        |
| -------------- | --------------------- | -------------- |
| `NODE_ENV`     | Node environment      | `production`   |
| `PORT`         | Application port      | `3000`         |
| `URL`          | Application URL       | Auto-generated |
| `DATABASE_URL` | PostgreSQL connection | Auto-generated |
| `REDIS_URL`    | Redis connection      | Auto-generated |
| `FILE_STORAGE` | Storage mode          | `local`        |
| `SECRET_KEY`   | Application secret    | Auto-generated |
| `UTILS_SECRET` | Utils secret          | Auto-generated |

## Health Checks[​](#health-checks "Direct link to Health Checks")

Outline provides health check endpoints:

```
# Check application health

curl http://localhost:3000/_health



# Check via kubectl

kubectl exec -it <pod-name> -- curl -f http://localhost:3000/_health
```

## Monitoring[​](#monitoring "Direct link to Monitoring")

### Basic Monitoring[​](#basic-monitoring "Direct link to Basic Monitoring")

```
# Check pod status

kubectl get pods -l app.kubernetes.io/name=outline



# Check resource usage

kubectl top pods -l app.kubernetes.io/name=outline



# Check logs

kubectl logs -f deployment/my-outline
```

### Prometheus Monitoring[​](#prometheus-monitoring "Direct link to Prometheus Monitoring")

Enable Prometheus monitoring:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "3000"

  prometheus.io/path: "/_health"
```

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Pod not starting**: Check resource limits and database connectivity
2. **Cannot access application**: Verify ingress configuration and DNS
3. **Authentication issues**: Check OAuth provider configuration
4. **File upload failures**: Verify storage configuration and permissions

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check pod events

kubectl describe pod <pod-name>



# Check application logs

kubectl logs <pod-name>



# Check environment variables

kubectl exec -it <pod-name> -- env | sort



# Test database connectivity

kubectl exec -it <pod-name> -- psql $DATABASE_URL -c "SELECT 1;"
```

### Enable Debug Logging[​](#enable-debug-logging "Direct link to Enable Debug Logging")

```
logging:

  level: debug

  extraDebug:

    - http

    - router

    - store
```

## Production Considerations[​](#production-considerations "Direct link to Production Considerations")

### Security[​](#security "Direct link to Security")

* Use strong passwords for database and Redis
* Enable SSL/TLS for all connections
* Configure proper RBAC
* Use existing secrets for sensitive data

### Performance[​](#performance "Direct link to Performance")

* Configure appropriate resource limits
* Use SSD storage for database
* Enable connection pooling
* Consider using external databases for high availability

### Backup Strategy[​](#backup-strategy "Direct link to Backup Strategy")

* Regular database backups
* File storage backups
* Test restore procedures
* Monitor backup success

## Configuration Examples[​](#configuration-examples "Direct link to Configuration Examples")

### Development Environment[​](#development-environment "Direct link to Development Environment")

```
replicaCount: 1

postgresql:

  enabled: true

  auth:

    username: outline

    password: devpassword

    database: outline

  primary:

    persistence:

      enabled: true

      size: 5Gi

redis:

  enabled: true

  auth:

    enabled: true

  master:

    persistence:

      enabled: true

      size: 5Gi

fileStorage:

  mode: local

  local:

    persistence:

      enabled: true

      size: 5Gi
```

### Production Environment[​](#production-environment "Direct link to Production Environment")

```
replicaCount: 1

postgresql:

  enabled: true

  architecture: replication

  auth:

    username: outline

    password: strongpassword

    database: outline

  primary:

    persistence:

      enabled: true

      size: 50Gi

      storageClass: "fast-ssd"

  readReplicas:

    persistence:

      enabled: true

      size: 50Gi

      storageClass: "fast-ssd"

redis:

  enabled: true

  architecture: standalone

  auth:

    enabled: true

  master:

    persistence:

      enabled: true

      size: 8Gi

fileStorage:

  mode: s3

  s3:

    bucket: outline-prod

    region: us-east-1

    existingSecret: "outline-s3-secret"

    forcePathStyle: true

    acl: private

ingress:

  enabled: true

  className: nginx

  annotations:

    cert-manager.io/cluster-issuer: letsencrypt-prod

  hosts:

    - host: outline.yourdomain.com

      paths:

        - path: /

          pathType: ImplementationSpecific

  tls:

    - secretName: outline-tls

      hosts:

        - outline.yourdomain.com
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [configuration options](/docs/charts/outline/configuration.md)
* Set up [authentication methods](/docs/charts/outline/authentication.md)
* Configure [storage options](/docs/charts/outline/storage.md)
* Set up [database configuration](/docs/charts/outline/database.md)
* Explore [advanced configuration options](/docs/charts/outline/advanced-configuration.md)
* Learn about [troubleshooting common issues](/docs/charts/outline/troubleshooting.md)


---

# Advanced Configuration

This page covers advanced configuration options for production-ready PyPI Server deployments, including high availability, monitoring, security, and performance optimization.

## High Availability[​](#high-availability "Direct link to High Availability")

### Multi-Replica Deployment[​](#multi-replica-deployment "Direct link to Multi-Replica Deployment")

For high availability, deploy multiple replicas with shared storage:

```
replicaCount: 3



strategy:

  type: RollingUpdate

  rollingUpdate:

    maxSurge: "100%"

    maxUnavailable: 0



volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc



volumeMounts:

  - name: packages

    mountPath: "/data/packages"



# Use ReadWriteMany storage class

# storageClassName: nfs-storage
```

### Pod Anti-Affinity[​](#pod-anti-affinity "Direct link to Pod Anti-Affinity")

Ensure replicas are distributed across nodes:

```
affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

              - key: app.kubernetes.io/name

                operator: In

                values:

                  - pypiserver

          topologyKey: kubernetes.io/hostname

    requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

                - pypiserver

        topologyKey: kubernetes.io/hostname
```

### Load Balancer Configuration[​](#load-balancer-configuration "Direct link to Load Balancer Configuration")

Configure service for load balancing:

```
service:

  type: LoadBalancer

  port: 8080

  annotations:

    service.beta.kubernetes.io/aws-load-balancer-type: nlb

    service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
```

## Monitoring and Observability[​](#monitoring-and-observability "Direct link to Monitoring and Observability")

### Prometheus Metrics[​](#prometheus-metrics "Direct link to Prometheus Metrics")

Enable Prometheus metrics collection:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "8080"

  prometheus.io/path: "/metrics"



podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"

  - "--fallback-url"

  - "https://pypi.org/simple/"

  - "--root"

  - "/data/packages"

  - "--server"

  - "gunicorn"

  - "--workers"

  - "4"
```

### Health Check Configuration[​](#health-check-configuration "Direct link to Health Check Configuration")

Enhanced health checks for better monitoring:

```
livenessProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 60

  periodSeconds: 30

  timeoutSeconds: 10

  failureThreshold: 3

  successThreshold: 1



readinessProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 3

  successThreshold: 1



startupProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 30
```

### Logging Configuration[​](#logging-configuration "Direct link to Logging Configuration")

Configure structured logging:

```
podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"

  - "--fallback-url"

  - "https://pypi.org/simple/"

  - "--root"

  - "/data/packages"

  - "--server"

  - "gunicorn"

  - "--workers"

  - "4"

  - "--log-level"

  - "info"

  - "--access-logfile"

  - "-"

  - "--error-logfile"

  - "-"
```

## Security Hardening[​](#security-hardening "Direct link to Security Hardening")

### Pod Security Standards[​](#pod-security-standards "Direct link to Pod Security Standards")

Implement Pod Security Standards:

```
podSecurityContext:

  runAsUser: 1000

  runAsGroup: 3000

  fsGroup: 2000

  fsGroupChangePolicy: OnRootMismatch

  supplementalGroups: [2000]

  seccompProfile:

    type: RuntimeDefault



securityContext:

  runAsNonRoot: true

  runAsUser: 1000

  readOnlyRootFilesystem: true

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL

  seccompProfile:

    type: RuntimeDefault
```

### Network Policies[​](#network-policies "Direct link to Network Policies")

Restrict network access:

```
# network-policy.yaml

apiVersion: networking.k8s.io/v1

kind: NetworkPolicy

metadata:

  name: pypi-network-policy

spec:

  podSelector:

    matchLabels:

      app.kubernetes.io/name: pypiserver

  policyTypes:

    - Ingress

    - Egress

  ingress:

    - from:

        - namespaceSelector:

            matchLabels:

              name: ingress-nginx

      ports:

        - protocol: TCP

          port: 8080

  egress:

    - to:

        - namespaceSelector:

            matchLabels:

              name: kube-system

      ports:

        - protocol: TCP

          port: 53

    - to:

        - ipBlock:

            cidr: 0.0.0.0/0

      ports:

        - protocol: TCP

          port: 443

        - protocol: TCP

          port: 80
```

### RBAC Configuration[​](#rbac-configuration "Direct link to RBAC Configuration")

Fine-grained access control:

```
serviceAccount:

  create: true

  automount: true

  annotations:

    eks.amazonaws.com/role-arn: arn:aws:iam::ACCOUNT:role/pypi-service-role



# rbac.yaml

apiVersion: rbac.authorization.k8s.io/v1

kind: Role

metadata:

  name: pypi-role

rules:

  - apiGroups: [""]

    resources: ["pods", "services", "endpoints"]

    verbs: ["get", "list", "watch"]

  - apiGroups: [""]

    resources: ["configmaps", "secrets"]

    verbs: ["get", "list", "watch"]



---

apiVersion: rbac.authorization.k8s.io/v1

kind: RoleBinding

metadata:

  name: pypi-role-binding

subjects:

  - kind: ServiceAccount

    name: pypi-service-account

    namespace: default

roleRef:

  kind: Role

  name: pypi-role

  apiGroup: rbac.authorization.k8s.io
```

## Performance Optimization[​](#performance-optimization "Direct link to Performance Optimization")

### Resource Optimization[​](#resource-optimization "Direct link to Resource Optimization")

Optimize resource allocation:

```
resources:

  limits:

    cpu: 1000m

    memory: 4Gi

  requests:

    cpu: 500m

    memory: 2Gi



# Horizontal Pod Autoscaler

apiVersion: autoscaling/v2

kind: HorizontalPodAutoscaler

metadata:

  name: pypi-hpa

spec:

  scaleTargetRef:

    apiVersion: apps/v1

    kind: Deployment

    name: pypi-deployment

  minReplicas: 2

  maxReplicas: 10

  metrics:

    - type: Resource

      resource:

        name: memory

        target:

          type: Utilization

          averageUtilization: 80

    - type: Resource

      resource:

        name: cpu

        target:

          type: Utilization

          averageUtilization: 70
```

### Caching Configuration[​](#caching-configuration "Direct link to Caching Configuration")

Implement caching for better performance:

```
podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"

  - "--fallback-url"

  - "https://pypi.org/simple/"

  - "--root"

  - "/data/packages"

  - "--server"

  - "gunicorn"

  - "--workers"

  - "4"

  - "--worker-connections"

  - "1000"

  - "--max-requests"

  - "1000"

  - "--max-requests-jitter"

  - "100"
```

## Backup and Disaster Recovery[​](#backup-and-disaster-recovery "Direct link to Backup and Disaster Recovery")

### Automated Backups[​](#automated-backups "Direct link to Automated Backups")

Implement automated backup strategy:

```
# backup-cronjob.yaml

apiVersion: batch/v1

kind: CronJob

metadata:

  name: pypi-backup

spec:

  schedule: "0 2 * * *"  # Daily at 2 AM

  concurrencyPolicy: Forbid

  jobTemplate:

    spec:

      template:

        spec:

          serviceAccountName: pypi-backup-sa

          containers:

          - name: backup

            image: alpine:latest

            command:

            - /bin/sh

            - -c

            - |

              apk add --no-cache rsync

              BACKUP_DATE=$(date +%Y%m%d_%H%M%S)

              BACKUP_FILE="pypi-packages-${BACKUP_DATE}.tar.gz"



              # Create backup

              tar -czf /backup/${BACKUP_FILE} -C /data packages/



              # Upload to S3 (if configured)

              if [ -n "$S3_BUCKET" ]; then

                aws s3 cp /backup/${BACKUP_FILE} s3://${S3_BUCKET}/backups/

              fi



              # Clean old backups (keep last 7 days)

              find /backup -name "pypi-packages-*.tar.gz" -mtime +7 -delete

            env:

            - name: S3_BUCKET

              value: "pypi-backups"

            volumeMounts:

            - name: packages

              mountPath: /data/packages

            - name: backup-storage

              mountPath: /backup

          volumes:

          - name: packages

            persistentVolumeClaim:

              claimName: pypi-packages-pvc

          - name: backup-storage

            persistentVolumeClaim:

              claimName: pypi-backup-pvc

          restartPolicy: OnFailure
```

### Disaster Recovery Plan[​](#disaster-recovery-plan "Direct link to Disaster Recovery Plan")

Create a disaster recovery configuration:

```
# disaster-recovery.yaml

apiVersion: v1

kind: ConfigMap

metadata:

  name: pypi-dr-config

data:

  restore-script.sh: |

    #!/bin/sh

    set -e



    echo "Starting PyPI Server disaster recovery..."



    # Restore from latest backup

    LATEST_BACKUP=$(ls -t /backup/pypi-packages-*.tar.gz | head -1)



    if [ -z "$LATEST_BACKUP" ]; then

      echo "No backup found!"

      exit 1

    fi



    echo "Restoring from: $LATEST_BACKUP"



    # Stop PyPI Server

    kubectl scale deployment pypi-deployment --replicas=0



    # Wait for pods to terminate

    kubectl wait --for=delete pod -l app.kubernetes.io/name=pypiserver --timeout=300s



    # Restore packages

    tar -xzf "$LATEST_BACKUP" -C /data/



    # Restart PyPI Server

    kubectl scale deployment pypi-deployment --replicas=3



    echo "Disaster recovery completed successfully"
```

## Production Deployment Example[​](#production-deployment-example "Direct link to Production Deployment Example")

Complete production-ready configuration:

```
# values-production.yaml

replicaCount: 3



image:

  repository: pypiserver/pypiserver

  tag: ""

  pullPolicy: IfNotPresent



service:

  type: LoadBalancer

  port: 8080

  annotations:

    service.beta.kubernetes.io/aws-load-balancer-type: nlb

    service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"



ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

    cert-manager.io/cluster-issuer: letsencrypt-prod

    nginx.ingress.kubernetes.io/ssl-redirect: "true"

    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"

  hosts:

    - host: pypi.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: pypi-tls

      hosts:

        - pypi.yourdomain.com



podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"

  - "--fallback-url"

  - "https://pypi.org/simple/"

  - "--root"

  - "/data/packages"

  - "--server"

  - "gunicorn"

  - "--workers"

  - "4"

  - "--worker-connections"

  - "1000"

  - "--max-requests"

  - "1000"

  - "--max-requests-jitter"

  - "100"

  - "--log-level"

  - "info"



resources:

  limits:

    cpu: 1000m

    memory: 4Gi

  requests:

    cpu: 500m

    memory: 2Gi



securityContext:

  runAsNonRoot: true

  runAsUser: 1000

  readOnlyRootFilesystem: true

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL



podSecurityContext:

  runAsUser: 1000

  runAsGroup: 3000

  fsGroup: 2000

  fsGroupChangePolicy: OnRootMismatch

  supplementalGroups: [2000]

  seccompProfile:

    type: RuntimeDefault



livenessProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 60

  periodSeconds: 30

  timeoutSeconds: 10

  failureThreshold: 3



readinessProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 3



startupProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 30



strategy:

  type: RollingUpdate

  rollingUpdate:

    maxSurge: "100%"

    maxUnavailable: 0



affinity:

  podAntiAffinity:

    requiredDuringSchedulingIgnoredDuringExecution:

      - labelSelector:

          matchExpressions:

            - key: app.kubernetes.io/name

              operator: In

              values:

                - pypiserver

        topologyKey: kubernetes.io/hostname



volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc

  - name: auth

    secret:

      secretName: pypi-auth



volumeMounts:

  - name: packages

    mountPath: "/data/packages"

  - name: auth

    mountPath: "/data/.htpasswd"

    subPath: ".htpasswd"



podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "8080"

  prometheus.io/path: "/metrics"



serviceAccount:

  create: true

  automount: true

  annotations:

    eks.amazonaws.com/role-arn: arn:aws:iam::ACCOUNT:role/pypi-service-role
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [storage configuration](/docs/charts/pypiserver/storage.md) for persistent data
* Explore [troubleshooting](/docs/charts/pypiserver/troubleshooting.md) for common issues
* Review [configuration](/docs/charts/pypiserver/configuration.md) for basic settings
* Check the [usage guide](/docs/charts/pypiserver/usage.md) for deployment examples


---

# Configuration

This page covers all configuration options available for the PyPI Server Helm chart. You can customize the deployment by creating a custom `values.yaml` file or passing values directly to the Helm command.

## Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

### Image Configuration[​](#image-configuration "Direct link to Image Configuration")

```
image:

  repository: pypiserver/pypiserver

  tag: ""  # Uses chart appVersion by default

  pullPolicy: IfNotPresent
```

### Replica Configuration[​](#replica-configuration "Direct link to Replica Configuration")

```
replicaCount: 1
```

note

PyPI Server is designed to be lightweight and typically runs as a single instance. For high availability, consider using multiple replicas with proper volume sharing.

### Service Configuration[​](#service-configuration "Direct link to Service Configuration")

```
service:

  type: ClusterIP

  port: 8080

  name: http

  annotations: {}
```

## PyPI Server Arguments[​](#pypi-server-arguments "Direct link to PyPI Server Arguments")

The chart allows you to customize PyPI Server startup arguments:

```
podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "."

  - "--overwrite"
```

### Common PyPI Server Arguments[​](#common-pypi-server-arguments "Direct link to Common PyPI Server Arguments")

| Argument             | Description                                                                         | Example                                     |
| -------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------- |
| `-a, --authenticate` | Comma-separated list of package names that require authentication                   | `-a "my-package,private-package"`           |
| `-P, --passwords`    | Path to password file                                                               | `-P "/data/.htpasswd"`                      |
| `--overwrite`        | Allow overwriting existing packages                                                 | `--overwrite`                               |
| `--fallback-url`     | Fallback URL for packages not found locally                                         | `--fallback-url "https://pypi.org/simple/"` |
| `--server`           | Server method (auto, cherrypy, paste, twisted, gunicorn, gevent, tornado, waitress) | `--server "gunicorn"`                       |
| `--port`             | Port to listen on                                                                   | `--port "8080"`                             |
| `--interface`        | Interface to bind to                                                                | `--interface "0.0.0.0"`                     |

## Ingress Configuration[​](#ingress-configuration "Direct link to Ingress Configuration")

Enable and configure ingress for external access:

```
ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

    cert-manager.io/cluster-issuer: letsencrypt-prod

  hosts:

    - host: pypi.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: pypi-tls

      hosts:

        - pypi.yourdomain.com
```

## Resource Management[​](#resource-management "Direct link to Resource Management")

Configure resource limits and requests:

```
resources:

  limits:

    cpu: 500m

    memory: 2Gi

  requests:

    cpu: 200m

    memory: 1Gi
```

## Security Configuration[​](#security-configuration "Direct link to Security Configuration")

### Pod Security Context[​](#pod-security-context "Direct link to Pod Security Context")

```
podSecurityContext:

  runAsUser: 1000

  runAsGroup: 3000

  fsGroup: 2000

  fsGroupChangePolicy: OnRootMismatch
```

### Container Security Context[​](#container-security-context "Direct link to Container Security Context")

```
securityContext:

  runAsNonRoot: true

  runAsUser: 1000

  readOnlyRootFilesystem: true

  allowPrivilegeEscalation: false

  capabilities:

    drop:

      - ALL
```

## Health Checks[​](#health-checks "Direct link to Health Checks")

Configure liveness and readiness probes:

```
livenessProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 30

  periodSeconds: 10

  timeoutSeconds: 5

  failureThreshold: 3



readinessProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 5

  periodSeconds: 5

  timeoutSeconds: 3

  failureThreshold: 3
```

## Deployment Strategy[​](#deployment-strategy "Direct link to Deployment Strategy")

```
strategy:

  type: Recreate

  # Alternative: RollingUpdate

  # rollingUpdate:

  #   maxSurge: "100%"

  #   maxUnavailable: 0
```

## Node Scheduling[​](#node-scheduling "Direct link to Node Scheduling")

### Node Selector[​](#node-selector "Direct link to Node Selector")

```
nodeSelector:

  kubernetes.io/os: linux

  node-role.kubernetes.io/worker: "true"
```

### Affinity Rules[​](#affinity-rules "Direct link to Affinity Rules")

```
affinity:

  podAntiAffinity:

    preferredDuringSchedulingIgnoredDuringExecution:

      - weight: 100

        podAffinityTerm:

          labelSelector:

            matchExpressions:

              - key: app.kubernetes.io/name

                operator: In

                values:

                  - pypiserver

          topologyKey: kubernetes.io/hostname
```

### Tolerations[​](#tolerations "Direct link to Tolerations")

```
tolerations:

  - key: "dedicated"

    operator: "Equal"

    value: "pypiserver"

    effect: "NoSchedule"
```

## Service Account[​](#service-account "Direct link to Service Account")

```
serviceAccount:

  create: true

  automount: true

  annotations: {}

  name: ""
```

## Complete Example[​](#complete-example "Direct link to Complete Example")

Here's a complete example of a production-ready configuration:

```
# values.yaml

replicaCount: 1



image:

  repository: pypiserver/pypiserver

  tag: ""

  pullPolicy: IfNotPresent



service:

  type: ClusterIP

  port: 8080

  name: http



ingress:

  enabled: true

  className: nginx

  annotations:

    kubernetes.io/ingress.class: nginx

    cert-manager.io/cluster-issuer: letsencrypt-prod

  hosts:

    - host: pypi.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: pypi-tls

      hosts:

        - pypi.yourdomain.com



podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"

  - "--fallback-url"

  - "https://pypi.org/simple/"



resources:

  limits:

    cpu: 500m

    memory: 2Gi

  requests:

    cpu: 200m

    memory: 1Gi



securityContext:

  runAsNonRoot: true

  runAsUser: 1000

  readOnlyRootFilesystem: true

  allowPrivilegeEscalation: false



podSecurityContext:

  runAsUser: 1000

  runAsGroup: 3000

  fsGroup: 2000



volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc

  - name: auth

    secret:

      secretName: pypi-auth



volumeMounts:

  - name: packages

    mountPath: "/data/packages"

  - name: auth

    mountPath: "/data/.htpasswd"

    subPath: ".htpasswd"
```

## Environment Variables[​](#environment-variables "Direct link to Environment Variables")

The chart automatically sets the following environment variables:

* `PYPISERVER_PORT`: Set to the service port (default: 8080)

You can add custom environment variables using the `env` section in the deployment template or by modifying the chart.

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [storage configuration](/docs/charts/pypiserver/storage.md) for persistent package storage
* Explore [advanced configuration](/docs/charts/pypiserver/advanced-configuration.md) options
* Check [troubleshooting](/docs/charts/pypiserver/troubleshooting.md) for common issues
* Review the [usage guide](/docs/charts/pypiserver/usage.md) for deployment examples


---

# Storage

PyPI Server requires persistent storage to maintain Python packages across pod restarts and deployments. This page covers storage configuration options and best practices.

## Storage Overview[​](#storage-overview "Direct link to Storage Overview")

PyPI Server stores packages in a directory structure that mirrors the PyPI format. The main storage requirements are:

* **Package Storage**: Python package files (`.whl`, `.tar.gz`, etc.)
* **Authentication Files**: Password files for protected packages
* **Configuration**: Server configuration and metadata

## Basic Storage Configuration[​](#basic-storage-configuration "Direct link to Basic Storage Configuration")

### Persistent Volume Claims[​](#persistent-volume-claims "Direct link to Persistent Volume Claims")

Create a PersistentVolumeClaim for package storage:

```
apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: pypi-packages-pvc

  namespace: your-namespace

spec:

  accessModes:

    - ReadWriteOnce

  resources:

    requests:

      storage: 10Gi

  storageClassName: standard
```

### Chart Configuration[​](#chart-configuration "Direct link to Chart Configuration")

Configure the chart to use persistent storage:

```
volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc

  - name: auth

    secret:

      secretName: pypi-auth



volumeMounts:

  - name: packages

    mountPath: "/data/packages"

  - name: auth

    mountPath: "/data/.htpasswd"

    subPath: ".htpasswd"
```

## Storage Classes[​](#storage-classes "Direct link to Storage Classes")

### Local Storage[​](#local-storage "Direct link to Local Storage")

For single-node deployments or development:

```
apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: pypi-packages-pvc

spec:

  accessModes:

    - ReadWriteOnce

  resources:

    requests:

      storage: 10Gi

  storageClassName: local-storage
```

### Network Storage[​](#network-storage "Direct link to Network Storage")

For multi-node clusters, use network-attached storage:

```
# NFS Example

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: pypi-packages-pvc

spec:

  accessModes:

    - ReadWriteMany  # Allows multiple pods to access

  resources:

    requests:

      storage: 50Gi

  storageClassName: nfs-storage
```

### Cloud Storage[​](#cloud-storage "Direct link to Cloud Storage")

For cloud environments, use cloud-native storage:

```
# AWS EBS Example

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: pypi-packages-pvc

spec:

  accessModes:

    - ReadWriteOnce

  resources:

    requests:

      storage: 100Gi

  storageClassName: gp3
```

## Authentication Storage[​](#authentication-storage "Direct link to Authentication Storage")

### Password File Storage[​](#password-file-storage "Direct link to Password File Storage")

Store authentication credentials securely:

```
# Create a secret with password file

apiVersion: v1

kind: Secret

metadata:

  name: pypi-auth

type: Opaque

stringData:

  .htpasswd: |

    admin:$apr1$xyz123$hashedpassword

    user:$apr1$abc456$hashedpassword
```

### Mount Authentication Files[​](#mount-authentication-files "Direct link to Mount Authentication Files")

```
volumes:

  - name: auth

    secret:

      secretName: pypi-auth



volumeMounts:

  - name: auth

    mountPath: "/data/.htpasswd"

    subPath: ".htpasswd"
```

## High Availability Storage[​](#high-availability-storage "Direct link to High Availability Storage")

### Shared Storage for Multiple Replicas[​](#shared-storage-for-multiple-replicas "Direct link to Shared Storage for Multiple Replicas")

For high availability with multiple replicas:

```
replicaCount: 3



volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc



volumeMounts:

  - name: packages

    mountPath: "/data/packages"



# Use ReadWriteMany access mode

# storageClassName: nfs-storage
```

### Storage Backups[​](#storage-backups "Direct link to Storage Backups")

Implement regular backups for your package storage:

```
# Example backup job

apiVersion: batch/v1

kind: CronJob

metadata:

  name: pypi-backup

spec:

  schedule: "0 2 * * *"  # Daily at 2 AM

  jobTemplate:

    spec:

      template:

        spec:

          containers:

          - name: backup

            image: alpine:latest

            command:

            - /bin/sh

            - -c

            - |

              tar -czf /backup/pypi-packages-$(date +%Y%m%d).tar.gz /data/packages

            volumeMounts:

            - name: packages

              mountPath: /data/packages

            - name: backup-storage

              mountPath: /backup

          volumes:

          - name: packages

            persistentVolumeClaim:

              claimName: pypi-packages-pvc

          - name: backup-storage

            persistentVolumeClaim:

              claimName: pypi-backup-pvc

          restartPolicy: OnFailure
```

## Storage Performance[​](#storage-performance "Direct link to Storage Performance")

### SSD Storage[​](#ssd-storage "Direct link to SSD Storage")

For better performance with large package repositories:

```
apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: pypi-packages-pvc

spec:

  accessModes:

    - ReadWriteOnce

  resources:

    requests:

      storage: 100Gi

  storageClassName: ssd-storage  # Use SSD storage class
```

### Storage Monitoring[​](#storage-monitoring "Direct link to Storage Monitoring")

Monitor storage usage and performance:

```
# Add storage monitoring annotations

podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "8080"

  prometheus.io/path: "/metrics"
```

## Complete Storage Example[​](#complete-storage-example "Direct link to Complete Storage Example")

Here's a complete example with all storage components:

```
# values.yaml

replicaCount: 1



volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc

  - name: auth

    secret:

      secretName: pypi-auth

  - name: config

    configMap:

      name: pypi-config



volumeMounts:

  - name: packages

    mountPath: "/data/packages"

  - name: auth

    mountPath: "/data/.htpasswd"

    subPath: ".htpasswd"

  - name: config

    mountPath: "/data/config"

    readOnly: true



podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"

  - "--fallback-url"

  - "https://pypi.org/simple/"

  - "--root"

  - "/data/packages"
```

### Required Kubernetes Resources[​](#required-kubernetes-resources "Direct link to Required Kubernetes Resources")

```
# pypi-storage.yaml

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

  name: pypi-packages-pvc

spec:

  accessModes:

    - ReadWriteOnce

  resources:

    requests:

      storage: 50Gi

  storageClassName: standard



---

apiVersion: v1

kind: Secret

metadata:

  name: pypi-auth

type: Opaque

stringData:

  .htpasswd: |

    admin:$apr1$xyz123$hashedpassword



---

apiVersion: v1

kind: ConfigMap

metadata:

  name: pypi-config

data:

  server.conf: |

    [server]

    port = 8080

    interface = 0.0.0.0
```

## Storage Best Practices[​](#storage-best-practices "Direct link to Storage Best Practices")

### 1. Size Planning[​](#1-size-planning "Direct link to 1. Size Planning")

* **Development**: 10-50 Gi
* **Production**: 100+ Gi (depending on package count)
* **Enterprise**: 500+ Gi with monitoring

### 2. Access Patterns[​](#2-access-patterns "Direct link to 2. Access Patterns")

* **Single Instance**: `ReadWriteOnce`
* **Multiple Replicas**: `ReadWriteMany` with shared storage
* **Backup**: Separate storage for backups

### 3. Security[​](#3-security "Direct link to 3. Security")

* Use secrets for authentication files
* Implement proper RBAC for storage access
* Encrypt storage at rest

### 4. Performance[​](#4-performance "Direct link to 4. Performance")

* Use SSD storage for better I/O performance
* Implement caching strategies
* Monitor storage metrics

### 5. Backup Strategy[​](#5-backup-strategy "Direct link to 5. Backup Strategy")

* Regular automated backups
* Test restore procedures
* Store backups in different locations

## Troubleshooting Storage Issues[​](#troubleshooting-storage-issues "Direct link to Troubleshooting Storage Issues")

### Common Issues[​](#common-issues "Direct link to Common Issues")

1. **Permission Denied**: Check security context and file permissions
2. **Storage Full**: Monitor usage and implement cleanup policies
3. **Mount Failures**: Verify PVC exists and is bound
4. **Performance Issues**: Consider SSD storage or caching

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check PVC status

kubectl get pvc



# Check pod storage

kubectl exec -it <pod-name> -- df -h



# Check storage permissions

kubectl exec -it <pod-name> -- ls -la /data/



# Check storage usage

kubectl exec -it <pod-name> -- du -sh /data/packages/
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [advanced configuration](/docs/charts/pypiserver/advanced-configuration.md) options
* Explore [troubleshooting](/docs/charts/pypiserver/troubleshooting.md) for storage issues
* Review [configuration](/docs/charts/pypiserver/configuration.md) for other settings
* Check the [usage guide](/docs/charts/pypiserver/usage.md) for deployment examples


---

# Troubleshooting

This page covers common issues you may encounter when deploying and running PyPI Server on Kubernetes, along with debugging commands and solutions.

## Common Issues[​](#common-issues "Direct link to Common Issues")

### 1. Pod Startup Issues[​](#1-pod-startup-issues "Direct link to 1. Pod Startup Issues")

#### Pod Stuck in Pending State[​](#pod-stuck-in-pending-state "Direct link to Pod Stuck in Pending State")

**Symptoms:**

* Pod remains in `Pending` state
* No events or error messages

**Debug Commands:**

```
# Check pod status

kubectl get pods -l app.kubernetes.io/name=pypiserver



# Check pod events

kubectl describe pod <pod-name>



# Check node resources

kubectl describe nodes



# Check PVC status

kubectl get pvc

kubectl describe pvc pypi-packages-pvc
```

**Solutions:**

* Ensure PVC exists and is bound
* Check node resources and taints
* Verify storage class is available
* Check resource requests/limits

#### Pod CrashLoopBackOff[​](#pod-crashloopbackoff "Direct link to Pod CrashLoopBackOff")

**Symptoms:**

* Pod repeatedly crashes and restarts
* Status shows `CrashLoopBackOff`

**Debug Commands:**

```
# Check pod logs

kubectl logs <pod-name> --previous



# Check pod events

kubectl describe pod <pod-name>



# Check container status

kubectl get pods <pod-name> -o yaml
```

**Common Causes:**

* Incorrect volume mounts
* Permission issues
* Missing configuration files
* Resource constraints

### 2. Storage Issues[​](#2-storage-issues "Direct link to 2. Storage Issues")

#### Permission Denied Errors[​](#permission-denied-errors "Direct link to Permission Denied Errors")

**Symptoms:**

* `Permission denied` in logs
* Cannot write to package directory

**Debug Commands:**

```
# Check volume mounts

kubectl exec -it <pod-name> -- ls -la /data/



# Check file permissions

kubectl exec -it <pod-name> -- ls -la /data/packages/



# Check security context

kubectl get pod <pod-name> -o yaml | grep -A 10 securityContext
```

**Solutions:**

```
# Fix security context

podSecurityContext:

  runAsUser: 1000

  runAsGroup: 3000

  fsGroup: 2000

  fsGroupChangePolicy: OnRootMismatch



securityContext:

  runAsNonRoot: true

  runAsUser: 1000
```

#### Storage Full[​](#storage-full "Direct link to Storage Full")

**Symptoms:**

* `No space left on device` errors
* Cannot upload new packages

**Debug Commands:**

```
# Check storage usage

kubectl exec -it <pod-name> -- df -h



# Check package directory size

kubectl exec -it <pod-name> -- du -sh /data/packages/



# Check PVC capacity

kubectl get pvc pypi-packages-pvc
```

**Solutions:**

* Increase PVC size
* Clean up old packages
* Implement storage monitoring

### 3. Network Issues[​](#3-network-issues "Direct link to 3. Network Issues")

#### Service Not Accessible[​](#service-not-accessible "Direct link to Service Not Accessible")

**Symptoms:**

* Cannot access PyPI Server from outside cluster
* Connection refused errors

**Debug Commands:**

```
# Check service status

kubectl get svc -l app.kubernetes.io/name=pypiserver



# Check endpoints

kubectl get endpoints -l app.kubernetes.io/name=pypiserver



# Test service connectivity

kubectl run test-pod --image=busybox --rm -it --restart=Never -- wget -O- http://<service-name>:8080



# Check ingress status

kubectl get ingress

kubectl describe ingress <ingress-name>
```

**Solutions:**

* Verify service configuration
* Check ingress controller
* Ensure port mappings are correct

#### Ingress Issues[​](#ingress-issues "Direct link to Ingress Issues")

**Symptoms:**

* Ingress not routing traffic
* SSL/TLS certificate issues

**Debug Commands:**

```
# Check ingress controller logs

kubectl logs -n ingress-nginx deployment/ingress-nginx-controller



# Check ingress events

kubectl describe ingress <ingress-name>



# Test ingress connectivity

curl -I https://pypi.yourdomain.com
```

**Solutions:**

* Verify ingress annotations
* Check certificate configuration
* Ensure DNS resolution

### 4. Authentication Issues[​](#4-authentication-issues "Direct link to 4. Authentication Issues")

#### Password File Problems[​](#password-file-problems "Direct link to Password File Problems")

**Symptoms:**

* Authentication failures
* Cannot access protected packages

**Debug Commands:**

```
# Check password file

kubectl exec -it <pod-name> -- cat /data/.htpasswd



# Check secret

kubectl get secret pypi-auth -o yaml



# Test authentication

curl -u username:password https://pypi.yourdomain.com/simple/
```

**Solutions:**

* Verify password file format
* Check secret configuration
* Ensure proper volume mounting

### 5. Performance Issues[​](#5-performance-issues "Direct link to 5. Performance Issues")

#### Slow Package Uploads/Downloads[​](#slow-package-uploadsdownloads "Direct link to Slow Package Uploads/Downloads")

**Symptoms:**

* Long response times
* Timeout errors

**Debug Commands:**

```
# Check resource usage

kubectl top pod <pod-name>



# Check pod metrics

kubectl exec -it <pod-name> -- cat /proc/cpuinfo

kubectl exec -it <pod-name> -- cat /proc/meminfo



# Check network performance

kubectl exec -it <pod-name> -- ping -c 3 google.com
```

**Solutions:**

* Increase resource limits
* Use SSD storage
* Optimize server configuration
* Add more replicas

## Debugging Commands[​](#debugging-commands "Direct link to Debugging Commands")

### General Debugging[​](#general-debugging "Direct link to General Debugging")

```
# Get all resources

kubectl get all -l app.kubernetes.io/name=pypiserver



# Check events

kubectl get events --sort-by='.lastTimestamp'



# Check logs with timestamps

kubectl logs <pod-name> --timestamps



# Follow logs in real-time

kubectl logs <pod-name> -f



# Check pod details

kubectl describe pod <pod-name>



# Check service details

kubectl describe svc <service-name>
```

### Storage Debugging[​](#storage-debugging "Direct link to Storage Debugging")

```
# Check PVC status

kubectl get pvc

kubectl describe pvc pypi-packages-pvc



# Check storage usage

kubectl exec -it <pod-name> -- df -h

kubectl exec -it <pod-name> -- du -sh /data/packages/



# Check file permissions

kubectl exec -it <pod-name> -- ls -la /data/

kubectl exec -it <pod-name> -- id



# Check volume mounts

kubectl get pod <pod-name> -o yaml | grep -A 20 volumeMounts
```

### Network Debugging[​](#network-debugging "Direct link to Network Debugging")

```
# Check service endpoints

kubectl get endpoints <service-name>



# Test service connectivity

kubectl run test-pod --image=busybox --rm -it --restart=Never -- wget -O- http://<service-name>:8080



# Check ingress status

kubectl get ingress

kubectl describe ingress <ingress-name>



# Test external connectivity

curl -I http://<service-ip>:8080

curl -I https://pypi.yourdomain.com
```

### Application Debugging[​](#application-debugging "Direct link to Application Debugging")

```
# Check PyPI Server process

kubectl exec -it <pod-name> -- ps aux



# Check listening ports

kubectl exec -it <pod-name> -- netstat -tlnp



# Check environment variables

kubectl exec -it <pod-name> -- env | grep PYPISERVER



# Check configuration

kubectl exec -it <pod-name> -- cat /data/.htpasswd
```

## Health Check Issues[​](#health-check-issues "Direct link to Health Check Issues")

### Liveness Probe Failures[​](#liveness-probe-failures "Direct link to Liveness Probe Failures")

**Symptoms:**

* Pod restarts frequently
* Health endpoint returns errors

**Debug Commands:**

```
# Test health endpoint

kubectl exec -it <pod-name> -- wget -O- http://localhost:8080/health



# Check probe configuration

kubectl get pod <pod-name> -o yaml | grep -A 10 livenessProbe



# Check application logs

kubectl logs <pod-name> --previous
```

**Solutions:**

```
# Adjust probe settings

livenessProbe:

  httpGet:

    path: /health

    port: http

  initialDelaySeconds: 60

  periodSeconds: 30

  timeoutSeconds: 10

  failureThreshold: 3
```

### Readiness Probe Failures[​](#readiness-probe-failures "Direct link to Readiness Probe Failures")

**Symptoms:**

* Service endpoints not ready
* Traffic not routed to pod

**Debug Commands:**

```
# Check readiness status

kubectl get pods -o wide



# Test readiness endpoint

kubectl exec -it <pod-name> -- wget -O- http://localhost:8080/health



# Check probe configuration

kubectl get pod <pod-name> -o yaml | grep -A 10 readinessProbe
```

## Resource Issues[​](#resource-issues "Direct link to Resource Issues")

### Memory Issues[​](#memory-issues "Direct link to Memory Issues")

**Symptoms:**

* `OOMKilled` errors
* High memory usage

**Debug Commands:**

```
# Check memory usage

kubectl top pod <pod-name>



# Check memory limits

kubectl get pod <pod-name> -o yaml | grep -A 5 resources



# Check memory stats

kubectl exec -it <pod-name> -- cat /proc/meminfo
```

**Solutions:**

```
# Increase memory limits

resources:

  limits:

    memory: 4Gi

  requests:

    memory: 2Gi
```

### CPU Issues[​](#cpu-issues "Direct link to CPU Issues")

**Symptoms:**

* Slow response times
* High CPU usage

**Debug Commands:**

```
# Check CPU usage

kubectl top pod <pod-name>



# Check CPU limits

kubectl get pod <pod-name> -o yaml | grep -A 5 resources



# Check CPU stats

kubectl exec -it <pod-name> -- cat /proc/cpuinfo
```

## Configuration Issues[​](#configuration-issues "Direct link to Configuration Issues")

### Values File Problems[​](#values-file-problems "Direct link to Values File Problems")

**Symptoms:**

* Helm install/upgrade fails
* Unexpected behavior

**Debug Commands:**

```
# Validate values file

helm template . -f values.yaml --dry-run



# Check rendered templates

helm template . -f values.yaml



# Validate against schema

helm template . -f values.yaml --validate
```

### Environment Variable Issues[​](#environment-variable-issues "Direct link to Environment Variable Issues")

**Symptoms:**

* Application not using expected configuration
* Missing environment variables

**Debug Commands:**

```
# Check environment variables

kubectl exec -it <pod-name> -- env



# Check specific variable

kubectl exec -it <pod-name> -- echo $PYPISERVER_PORT



# Check deployment configuration

kubectl get deployment <deployment-name> -o yaml | grep -A 10 env
```

## Recovery Procedures[​](#recovery-procedures "Direct link to Recovery Procedures")

### Pod Recovery[​](#pod-recovery "Direct link to Pod Recovery")

```
# Restart deployment

kubectl rollout restart deployment <deployment-name>



# Check rollout status

kubectl rollout status deployment <deployment-name>



# Rollback to previous version

kubectl rollout undo deployment <deployment-name>
```

### Data Recovery[​](#data-recovery "Direct link to Data Recovery")

```
# Create backup before troubleshooting

kubectl exec -it <pod-name> -- tar -czf /tmp/backup.tar.gz /data/packages/



# Copy backup from pod

kubectl cp <pod-name>:/tmp/backup.tar.gz ./backup.tar.gz



# Restore data if needed

kubectl cp ./backup.tar.gz <new-pod-name>:/tmp/

kubectl exec -it <new-pod-name> -- tar -xzf /tmp/backup.tar.gz -C /
```

### Service Recovery[​](#service-recovery "Direct link to Service Recovery")

```
# Restart service

kubectl delete svc <service-name>

kubectl apply -f service.yaml



# Check service endpoints

kubectl get endpoints <service-name>



# Test service connectivity

kubectl run test-pod --image=busybox --rm -it --restart=Never -- wget -O- http://<service-name>:8080
```

## Monitoring and Alerting[​](#monitoring-and-alerting "Direct link to Monitoring and Alerting")

### Set Up Monitoring[​](#set-up-monitoring "Direct link to Set Up Monitoring")

```
# Add monitoring annotations

podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "8080"

  prometheus.io/path: "/metrics"



# Create ServiceMonitor for Prometheus

apiVersion: monitoring.coreos.com/v1

kind: ServiceMonitor

metadata:

  name: pypi-monitor

spec:

  selector:

    matchLabels:

      app.kubernetes.io/name: pypiserver

  endpoints:

    - port: http

      path: /metrics
```

### Common Alerts[​](#common-alerts "Direct link to Common Alerts")

```
# Example Prometheus alert rules

groups:

  - name: pypi-server

    rules:

      - alert: PyPIServerDown

        expr: up{app="pypiserver"} == 0

        for: 1m

        labels:

          severity: critical

        annotations:

          summary: "PyPI Server is down"



      - alert: PyPIServerHighMemory

        expr: container_memory_usage_bytes{container="pypiserver"} > 3e9

        for: 5m

        labels:

          severity: warning

        annotations:

          summary: "PyPI Server memory usage is high"
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Review [configuration](/docs/charts/pypiserver/configuration.md) for proper setup
* Learn about [storage](/docs/charts/pypiserver/storage.md) configuration
* Explore [advanced configuration](/docs/charts/pypiserver/advanced-configuration.md) options
* Check the [usage guide](/docs/charts/pypiserver/usage.md) for deployment examples


---

# PyPI Server Chart Usage

[PyPI Server](https://github.com/pypiserver/pypiserver) is a minimal PyPI compatible server for hosting your own Python packages. This chart helps you deploy a private PyPI server on Kubernetes.

* **Official Website:** <https://github.com/pypiserver/pypiserver>
* **GitHub Repository:** <https://github.com/pypiserver/pypiserver>
* **Documentation:** <https://github.com/pypiserver/pypiserver?tab=readme-ov-file#pypiserver>
* **ArtifactHub:** [PyPI Server Helm Chart](https://artifacthub.io/packages/helm/community-charts/pypiserver)

## Why use this chart?[​](#why-use-this-chart "Direct link to Why use this chart?")

* Host your own private Python package repository
* Community-maintained and up-to-date
* Simple, lightweight, and easy to use

## Installation[​](#installation "Direct link to Installation")

```
helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update

helm install my-pypiserver community-charts/pypiserver -n <your-namespace>
```

Replace `<your-namespace>` with your target namespace. For advanced configuration, see [values.yaml](https://github.com/community-charts/helm-charts/blob/main/charts/pypiserver/values.yaml) and [ArtifactHub page](https://artifacthub.io/packages/helm/community-charts/pypiserver).

## Basic Usage[​](#basic-usage "Direct link to Basic Usage")

### Quick Start[​](#quick-start "Direct link to Quick Start")

Deploy PyPI Server with default settings:

```
# Create namespace

kubectl create namespace pypi



# Install chart

helm install pypi community-charts/pypiserver -n pypi



# Check deployment

kubectl get pods -n pypi

kubectl get svc -n pypi
```

### Access the Server[​](#access-the-server "Direct link to Access the Server")

```
# Port forward to access locally

kubectl port-forward svc/pypi 8080:8080 -n pypi



# Access in browser: http://localhost:8080
```

### Upload Packages[​](#upload-packages "Direct link to Upload Packages")

```
# Upload a package

pip install twine

twine upload --repository-url http://localhost:8080 your-package.whl



# Or use pip to install from your server

pip install --index-url http://localhost:8080/simple/ your-package
```

## Configuration Examples[​](#configuration-examples "Direct link to Configuration Examples")

### Basic Configuration[​](#basic-configuration "Direct link to Basic Configuration")

```
# values-basic.yaml

replicaCount: 1



service:

  type: ClusterIP

  port: 8080



ingress:

  enabled: true

  className: nginx

  hosts:

    - host: pypi.yourdomain.com

      paths:

        - path: /

          pathType: Prefix
```

### Production Configuration[​](#production-configuration "Direct link to Production Configuration")

```
# values-production.yaml

replicaCount: 3



service:

  type: LoadBalancer

  port: 8080



ingress:

  enabled: true

  className: nginx

  annotations:

    cert-manager.io/cluster-issuer: letsencrypt-prod

  hosts:

    - host: pypi.yourdomain.com

      paths:

        - path: /

          pathType: Prefix

  tls:

    - secretName: pypi-tls

      hosts:

        - pypi.yourdomain.com



resources:

  limits:

    cpu: 1000m

    memory: 4Gi

  requests:

    cpu: 500m

    memory: 2Gi



volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc



volumeMounts:

  - name: packages

    mountPath: "/data/packages"
```

## Package Management[​](#package-management "Direct link to Package Management")

### Uploading Packages[​](#uploading-packages "Direct link to Uploading Packages")

```
# Using twine

twine upload --repository-url https://pypi.yourdomain.com your-package.whl



# Using pip

pip install --index-url https://pypi.yourdomain.com/simple/ your-package



# Using curl

curl -X POST -F "content=@your-package.whl" https://pypi.yourdomain.com/upload/
```

### Authentication[​](#authentication "Direct link to Authentication")

For protected packages, create a password file:

```
# Create password file

htpasswd -c .htpasswd username



# Create Kubernetes secret

kubectl create secret generic pypi-auth --from-file=.htpasswd -n pypi



# Update values.yaml

volumes:

  - name: auth

    secret:

      secretName: pypi-auth



volumeMounts:

  - name: auth

    mountPath: "/data/.htpasswd"

    subPath: ".htpasswd"



podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"
```

### Package Organization[​](#package-organization "Direct link to Package Organization")

Organize packages by project or team:

```
# Create package directories

mkdir -p packages/{team-a,team-b,public}



# Upload to specific directories

twine upload --repository-url https://pypi.yourdomain.com/team-a/ package-a.whl

twine upload --repository-url https://pypi.yourdomain.com/team-b/ package-b.whl
```

## Integration Examples[​](#integration-examples "Direct link to Integration Examples")

### CI/CD Integration[​](#cicd-integration "Direct link to CI/CD Integration")

```
# GitHub Actions example

name: Deploy Package

on:

  push:

    tags:

      - 'v*'



jobs:

  deploy:

    runs-on: ubuntu-latest

    steps:

      - uses: actions/checkout@v3



      - name: Build package

        run: |

          python setup.py sdist bdist_wheel



      - name: Upload to PyPI Server

        run: |

          pip install twine

          twine upload --repository-url ${{ secrets.PYPI_URL }} \

            --username ${{ secrets.PYPI_USERNAME }} \

            --password ${{ secrets.PYPI_PASSWORD }} \

            dist/*
```

### Docker Integration[​](#docker-integration "Direct link to Docker Integration")

```
# Dockerfile example

FROM python:3.9-slim



# Install from private PyPI server

RUN pip install --index-url https://pypi.yourdomain.com/simple/ \

    --trusted-host pypi.yourdomain.com \

    your-private-package



# Continue with your application

COPY . /app

WORKDIR /app

CMD ["python", "app.py"]
```

### Kubernetes Job Example[​](#kubernetes-job-example "Direct link to Kubernetes Job Example")

```
# job-example.yaml

apiVersion: batch/v1

kind: Job

metadata:

  name: package-upload-job

spec:

  template:

    spec:

      containers:

      - name: upload

        image: python:3.9-slim

        command:

        - /bin/sh

        - -c

        - |

          pip install twine

          twine upload --repository-url https://pypi.yourdomain.com \

            --username $PYPI_USERNAME \

            --password $PYPI_PASSWORD \

            /packages/*.whl

        env:

        - name: PYPI_USERNAME

          valueFrom:

            secretKeyRef:

              name: pypi-credentials

              key: username

        - name: PYPI_PASSWORD

          valueFrom:

            secretKeyRef:

              name: pypi-credentials

              key: password

        volumeMounts:

        - name: packages

          mountPath: /packages

      volumes:

      - name: packages

        persistentVolumeClaim:

          claimName: packages-pvc

      restartPolicy: Never
```

## Monitoring and Health Checks[​](#monitoring-and-health-checks "Direct link to Monitoring and Health Checks")

### Health Endpoint[​](#health-endpoint "Direct link to Health Endpoint")

PyPI Server provides a health endpoint:

```
# Check health

curl http://localhost:8080/health



# Expected response: {"status": "healthy"}
```

### Metrics[​](#metrics "Direct link to Metrics")

Enable Prometheus metrics:

```
podAnnotations:

  prometheus.io/scrape: "true"

  prometheus.io/port: "8080"

  prometheus.io/path: "/metrics"
```

### Logs[​](#logs "Direct link to Logs")

```
# View logs

kubectl logs -f deployment/pypi -n pypi



# Check specific pod logs

kubectl logs -f pod/pypi-xxxxx -n pypi
```

## Scaling and Performance[​](#scaling-and-performance "Direct link to Scaling and Performance")

### Horizontal Scaling[​](#horizontal-scaling "Direct link to Horizontal Scaling")

```
# Scale to multiple replicas

replicaCount: 3



# Use shared storage

volumes:

  - name: packages

    persistentVolumeClaim:

      claimName: pypi-packages-pvc

      # Use ReadWriteMany storage class



volumeMounts:

  - name: packages

    mountPath: "/data/packages"
```

### Resource Optimization[​](#resource-optimization "Direct link to Resource Optimization")

```
# Optimize for performance

resources:

  limits:

    cpu: 2000m

    memory: 8Gi

  requests:

    cpu: 1000m

    memory: 4Gi



podArgs:

  - "run"

  - "--server"

  - "gunicorn"

  - "--workers"

  - "8"

  - "--worker-connections"

  - "2000"
```

## Security Considerations[​](#security-considerations "Direct link to Security Considerations")

### Network Security[​](#network-security "Direct link to Network Security")

```
# Restrict network access

service:

  type: ClusterIP  # Internal access only



# Use ingress for external access

ingress:

  enabled: true

  annotations:

    nginx.ingress.kubernetes.io/whitelist-source-range: "10.0.0.0/8,172.16.0.0/12"
```

### Authentication[​](#authentication-1 "Direct link to Authentication")

```
# Require authentication for all packages

podArgs:

  - "run"

  - "-a"

  - "."

  - "-P"

  - "/data/.htpasswd"

  - "--overwrite"
```

### TLS/SSL[​](#tlsssl "Direct link to TLS/SSL")

```
# Enable HTTPS

ingress:

  enabled: true

  tls:

    - secretName: pypi-tls

      hosts:

        - pypi.yourdomain.com
```

## Next Steps[​](#next-steps "Direct link to Next Steps")

* Learn about [configuration](/docs/charts/pypiserver/configuration.md) options and customization
* Set up [storage](/docs/charts/pypiserver/storage.md) for persistent package storage
* Explore [advanced configuration](/docs/charts/pypiserver/advanced-configuration.md) for production deployments
* Check [troubleshooting](/docs/charts/pypiserver/troubleshooting.md) for common issues and solutions


---

# Getting Started with GitHub Community Charts

Welcome to **GitHub Community Charts**, your source for community-maintained Helm charts that simplify deploying open-source tools on Kubernetes. Our charts support projects like [MLflow](https://mlflow.org), [n8n](https://n8n.io), [Actual Budget](https://actualbudget.org), and more, ensuring reliable and up-to-date deployments for tools that may lack official Helm chart support.

info

**Community-Driven:** These charts are maintained by the community to fill gaps where official Helm charts may not exist or may not be actively maintained.

This guide walks you through setting up our Helm repository and exploring our chart offerings, so you can quickly deploy your favorite open-source applications.

tip

**Quick Start:** Follow this guide step-by-step to get your first application running on Kubernetes in minutes.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

warning

**Requirements:** Ensure you have all prerequisites installed and configured before proceeding with chart installations.

Before you begin, ensure you have the following:

* A Kubernetes cluster (version >= 1.16.0)
* [Helm 3](https://helm.sh/docs/intro/install/) installed on your local machine
* `kubectl` configured to access your cluster

danger

**Cluster Compatibility:** Verify your Kubernetes cluster version meets the minimum requirements to avoid deployment issues.

tip

**Development Setup:** For local development, consider using tools like Minikube, Docker Desktop, or Kind to create a local Kubernetes cluster.

## Step 1: Add the Community Charts Helm Repository[​](#step-1-add-the-community-charts-helm-repository "Direct link to Step 1: Add the Community Charts Helm Repository")

info

**Repository Setup:** Adding our Helm repository gives you access to all community-maintained charts in one place.

To use our charts, add the GitHub Community Charts Helm repository to your Helm client:

```
helm repo add community-charts https://community-charts.github.io/helm-charts

helm repo update
```

* The `helm repo add` command registers our repository under the name `community-charts`.
* The `helm repo update` command ensures you have the latest chart versions.

tip

**Repository Management:** Always run `helm repo update` after adding a new repository to get the latest chart information.

Verify the repository was added:

```
helm repo list
```

You should see `community-charts` with the URL `https://community-charts.github.io/helm-charts`.

## Step 2: Explore Available Charts[​](#step-2-explore-available-charts "Direct link to Step 2: Explore Available Charts")

info

**Chart Discovery:** Browse our available charts to find the tools that best fit your needs and use cases.

Browse our available charts to find the tools you need:

```
helm search repo community-charts
```

This lists all charts in our repository, including:

* **MLflow**: Manage machine learning workflows with experiment tracking and model deployment.
* **n8n**: Automate tasks with a no-code/low-code workflow platform.
* **Actual Budget**: Track personal finances in a secure, self-hosted environment.
* **Outline**: Build collaborative knowledge bases with a modern wiki.
* **Cloudflared**: Create secure tunnels to your Kubernetes services using Cloudflare.
* **Drone**: Run continuous integration and deployment pipelines.
* **Pypiserver**: Host your own Python package repository.

tip

**Chart Selection:** To see all available versions of a chart, use `helm search repo community-charts -l`. For example, `helm search repo community-charts/mlflow -l` lists all MLflow chart versions.

For detailed descriptions and installation guides, visit the [Charts documentation](/docs/category/charts.md).

## Step 3: Install a Chart[​](#step-3-install-a-chart "Direct link to Step 3: Install a Chart")

warning

**Installation Planning:** Choose appropriate namespaces and release names for your deployments to maintain organization and avoid conflicts.

To install a chart, use the `helm install` command. Below is an example for installing the MLflow chart with default settings:

```
helm install my-mlflow community-charts/mlflow -n <your-namespace>
```

Replace `my-mlflow` with your preferred release name and `<your-namespace>` with the target namespace (e.g., `default`). If the namespace doesn't exist, create it first:

```
kubectl create namespace <your-namespace>
```

tip

**Namespace Organization:** Use dedicated namespaces for different applications to keep your cluster organized and simplify management.

danger

**Release Names:** Choose unique release names to avoid conflicts. Release names must be unique within a namespace.

For customized installations (e.g., using PostgreSQL or AWS S3), refer to the chart's specific documentation. For MLflow, see [Basic Installation with SQLite](/docs/charts/mlflow/basic-installation.md), [PostgreSQL Backend Installation](/docs/charts/mlflow/postgresql-backend-installation.md), and [AWS S3 Integration](/docs/charts/mlflow/aws-s3-integration.md).

## Step 4: Verify the Installation[​](#step-4-verify-the-installation "Direct link to Step 4: Verify the Installation")

info

**Verification Process:** Always verify your installations to ensure applications are running correctly before proceeding with configuration.

Check the status of your deployment:

```
kubectl get pods -n <your-namespace>
```

Look for pods associated with your release (e.g., `my-mlflow-XXXXX`) in a `Running` state.

warning

**Pod Status:** If pods are not in `Running` state, check the logs with `kubectl logs <pod-name> -n <namespace>` to diagnose issues.

Access the application using the instructions in the chart's documentation. For example, MLflow typically exposes a web UI at port 5000, which you can access via port-forwarding:

```
kubectl port-forward svc/my-mlflow -n <your-namespace> 5000:5000
```

Then, open `http://localhost:5000` in your browser.

tip

**Port Forwarding:** Port forwarding is suitable for development and testing. For production, configure ingress or load balancers for external access.

## Our Chart Offerings[​](#our-chart-offerings "Direct link to Our Chart Offerings")

info

**Chart Overview:** Each chart is designed for specific use cases and includes comprehensive documentation for various deployment scenarios.

Here's a quick overview of our current charts and their use cases:

| Chart         | Description                                                                                                      | Documentation Link                                        |
| ------------- | ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| MLflow        | Platform for managing the machine learning lifecycle                                                             | [mlflow chart docs](/docs/category/mlflow.md)             |
| n8n           | Workflow automation tool with **unique npm package installation** and **exclusive external task runner support** | [n8n chart docs](/docs/category/n8n.md)                   |
| Actual Budget | Self-hosted personal finance tracker                                                                             | [actualbudget chart docs](/docs/category/actualbudget.md) |
| Outline       | Modern wiki for collaborative knowledge management                                                               | [outline chart docs](/docs/category/outline.md)           |
| Cloudflared   | Secure tunneling with Cloudflare for Kubernetes services                                                         | [cloudflared chart docs](/docs/category/cloudflared.md)   |
| Drone         | Continuous integration and deployment system                                                                     | [drone chart docs](/docs/category/drone.md)               |
| PyPI server   | Private minimal Python package repository                                                                        | [pypiserver chart docs](/docs/category/pypiserver.md)     |

tip

**Unique Features:** Our n8n chart offers exclusive features not available in other Helm charts, including advanced npm package management and external task runner support.

Explore the [Charts section](/docs/category/charts.md) for detailed installation guides and configuration options.

## Production Considerations[​](#production-considerations "Direct link to Production Considerations")

warning

**Production Readiness:** These charts are designed for production use, but always review security, backup, and monitoring requirements for your specific environment.

### Security Best Practices[​](#security-best-practices "Direct link to Security Best Practices")

* Use dedicated namespaces for different applications
* Configure RBAC (Role-Based Access Control) appropriately
* Use Kubernetes secrets for sensitive data
* Enable TLS/SSL for external access
* Regularly update chart versions for security patches

danger

**Security Configuration:** Never use default passwords or credentials in production environments. Always configure proper authentication and authorization.

### Backup and Monitoring[​](#backup-and-monitoring "Direct link to Backup and Monitoring")

* Set up regular backups for databases and persistent data
* Configure monitoring and alerting for your applications
* Use health checks and readiness probes
* Monitor resource usage and set appropriate limits

tip

**Monitoring Setup:** Most charts include ServiceMonitor configurations for Prometheus integration and comprehensive monitoring.

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

info

**Common Issues:** This section covers frequently encountered problems and their solutions.

### Installation Issues[​](#installation-issues "Direct link to Installation Issues")

1. **Chart not found**: Ensure the repository is added and updated
2. **Namespace issues**: Verify the namespace exists and you have permissions
3. **Resource constraints**: Check cluster capacity and resource limits
4. **Image pull errors**: Verify image repositories and credentials

### Debug Commands[​](#debug-commands "Direct link to Debug Commands")

```
# Check Helm repository status

helm repo list

helm repo update



# Verify chart availability

helm search repo community-charts



# Check installation status

helm list -n <namespace>

kubectl get pods -n <namespace>



# View application logs

kubectl logs <pod-name> -n <namespace>



# Check events

kubectl get events -n <namespace> --sort-by='.lastTimestamp'
```

tip

**Debug Process:** Start with basic connectivity and permissions, then move to application-specific configuration issues.

## Next Steps[​](#next-steps "Direct link to Next Steps")

tip

**Getting Started:** Follow these recommended next steps to build on your initial deployment.

Now that you've set up our Helm repository, try these next steps:

* Deploy a chart like MLflow with a [basic SQLite setup](/docs/charts/mlflow/basic-installation.md) for testing.
* Configure a production-ready deployment with [PostgreSQL](/docs/charts/mlflow/postgresql-backend-installation.md) or [AWS S3](/docs/charts/mlflow/aws-s3-integration.md).
* Contribute to our charts by submitting pull requests or suggesting new charts in our [GitHub repository](https://github.com/community-charts/helm-charts).
* Report issues or request features via [GitHub issues](https://github.com/community-charts/helm-charts/issues).
* Stay updated by following our [blog](/blog.md) for tutorials and announcements.

info

**Community Contribution:** We welcome contributions from the community! Whether it's improving documentation, adding new features, or reporting issues, every contribution helps make these charts better.

We're excited to have you as part of the GitHub Community Charts community. Let's make deploying open-source tools on Kubernetes easier, together!


---