Skip to main content
This guide walks you through deploying Activepieces on Kubernetes using the official Helm chart.

Prerequisites

  • Kubernetes cluster (v1.19+)
  • Helm 3.x installed
  • kubectl configured to access your cluster

Using External PostgreSQL and Redis

The Helm chart supports using external PostgreSQL and Redis services instead of deploying the Bitnami subcharts.

Using External PostgreSQL

To use an external PostgreSQL instance:
Alternatively, you can use a connection URL:

Using External Redis

To use an external Redis instance:
Alternatively, you can use a connection URL:

External Secret References

For better security, you can reference passwords from existing Kubernetes secrets (useful with External Secrets Operator or Sealed Secrets):

Quick Start

1. Clone the Repository

2. Install Dependencies

3. Create a Values File

Create a my-values.yaml file with your configuration. You can use the example values file as a reference. The Helm chart has sensible defaults for required values while leaving the optional ones empty, but you should customize these core values for production. Include these so you can activate a license key later:
Set both, and set each variable in one place only. activepiecesConfig writes plain values into the pod, while activepiecesEnvVariables pulls the same names from Kubernetes secrets you create yourself and renders after it, so a secret that holds the key wins. The chart lists AP_EDITION and AP_EXECUTION_MODE under activepieces-config-secrets by default, so either remove them from there or set them in that secret instead of here.AP_EDITION=ee with the default execution mode is rejected at startup and the app will not boot.

4. Install Activepieces

5. Verify Installation

Production Checklist

  • Set frontendUrl to your actual domain
  • Set strong passwords for PostgreSQL and Redis (or keep auto-generated)
  • Configure proper ingress with TLS
  • Set appropriate resource limits
  • Configure persistent storage
  • Choose appropriate execution mode for your security requirements
  • Review environment variables for advanced configuration
  • Consider using a separate workers setup for better availability and security

Upgrading

Troubleshooting

Common Issues

  1. Pod won’t start: Check logs with kubectl logs deployment/activepieces
  2. Database connection: Verify PostgreSQL credentials and connectivity
  3. Frontend URL: Ensure frontendUrl is accessible from external sources
  4. Webhooks not working: Check ingress configuration and DNS resolution

Useful Commands

Environment Variables

For a complete list of configuration options, see the Environment Variables documentation. Most environment variables can be configured through the Helm values file, either as plain values under activepiecesConfig or injected from your own secrets under activepiecesEnvVariables.

Execution Modes

Understanding execution modes is crucial for security and performance. See the Sandboxing guide to choose the right mode for your deployment.

Uninstalling