Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion en/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@
* [Elestio](https://elest.io/open-source/flowiseai)
* [GCP](configuration/deployment/gcp.md)
* [Hugging Face](configuration/deployment/hugging-face.md)
* [Kubernetes using Helm](https://artifacthub.io/packages/helm/cowboysysop/flowise)
* [Kubernetes using Helm](configuration/deployment/kubernetes.md)
* [Northflank](https://northflank.com/stacks/deploy-flowiseai)
* [Railway](configuration/deployment/railway.md)
* [Render](configuration/deployment/render.md)
Expand Down
2 changes: 1 addition & 1 deletion en/configuration/deployment/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,4 +38,4 @@ This complexity, however, also grants greater flexibility and control over your
* [Azure](azure.md)
* [DigitalOcean](digital-ocean.md)
* [GCP](gcp.md)
* [Kubernetes using Helm](https://artifacthub.io/packages/helm/cowboysysop/flowise)
* [Kubernetes using Helm](kubernetes.md)
92 changes: 92 additions & 0 deletions en/configuration/deployment/kubernetes.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,92 @@
---
description: Learn how to deploy Flowise on Kubernetes using Helm
---

# Kubernetes

***

Deploy Flowise on Kubernetes using community-maintained Helm charts.

## HelmForge Chart

[HelmForge](https://helmforge.dev) provides a Helm chart that supports both standalone and queue deployment modes.

* Chart source: [github.com/helmforgedev/charts](https://github.com/helmforgedev/charts/tree/main/charts/flowise)
* ArtifactHub: [artifacthub.io/packages/helm/helmforge/flowise](https://artifacthub.io/packages/helm/helmforge/flowise)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better readability and clarity, consider using more descriptive link texts instead of repeating parts of the URLs. This helps users understand the destination of the link at a glance.

Suggested change
* Chart source: [github.com/helmforgedev/charts](https://github.com/helmforgedev/charts/tree/main/charts/flowise)
* ArtifactHub: [artifacthub.io/packages/helm/helmforge/flowise](https://artifacthub.io/packages/helm/helmforge/flowise)
* Chart source: [HelmForge Charts on GitHub](https://github.com/helmforgedev/charts/tree/main/charts/flowise)
* ArtifactHub: [Flowise chart on ArtifactHub](https://artifacthub.io/packages/helm/helmforge/flowise)


### Prerequisites

* A running Kubernetes cluster (v1.26+)
* [Helm](https://helm.sh/docs/intro/install/) v3 installed

### Install

```bash
helm repo add helmforge https://repo.helmforge.dev
helm repo update
helm install flowise helmforge/flowise
```

Or install directly from the OCI registry:

```bash
helm install flowise oci://ghcr.io/helmforgedev/helm/flowise
```

### Standalone Mode (default)

The default installation runs Flowise as a single Deployment with SQLite and local storage. This is suitable for evaluation and small workloads.

### Queue Mode

For scalable production deployments, enable queue mode with separate main and worker pods backed by Redis and PostgreSQL:

```bash
helm install flowise helmforge/flowise \
--set architecture=queue \
--set postgresql.enabled=true \
--set redis.enabled=true
```

Queue mode deploys:

* **Main pod** — serves the web UI and API
* **Worker pods** — process AI execution tasks from the Redis queue
* **PostgreSQL** — persistent database (bundled subchart or external)
* **Redis** — message queue (bundled subchart or external)

### Ingress

Enable ingress to expose the Flowise UI:

```yaml
# values.yaml
ingress:
enabled: true
ingressClassName: nginx
hosts:
- host: flowise.example.com
paths:
- path: /
pathType: Prefix
tls:
- secretName: flowise-tls
hosts:
- flowise.example.com
```

```bash
helm install flowise helmforge/flowise -f values.yaml
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The helm install command will fail if a release named flowise already exists (e.g., from following the initial installation steps). Using helm upgrade --install is more robust as it will either install a new release or upgrade an existing one, preventing potential errors for users.

Suggested change
helm install flowise helmforge/flowise -f values.yaml
helm upgrade --install flowise helmforge/flowise -f values.yaml

```

For full configuration options and architecture details, see the [chart documentation](https://helmforge.dev/docs/charts/flowise).

## Cowboysysop Chart

An alternative community chart is available from [cowboysysop](https://artifacthub.io/packages/helm/cowboysysop/flowise).

```bash
helm repo add cowboysysop https://cowboysysop.github.io/charts/
helm install flowise cowboysysop/flowise
```