Detailed instructions for deploying RudderStack on Kubernetes

You can deploy RudderStack on your Kubernetes cluster using the Helm package manager.

The repository for this Helm chart can be found here.

Quick Overview

helm install deploys to the Kubernetes cluster configured with kubectl

$ git clone [email protected]:rudderlabs/rudderstack-helm.git
$ cd rudderstack-helm/
$ helm install my-release ./ --set rudderWorkspaceToken="<workspace token from the dashboard>"


  • Kubectl installed and connected to your Kubernetes cluster

  • Helm installed

  • Workspace token from the RudderStack dashboard. Set up your account and copy your workspace token from the top of the home page.

Workspace Token

Why do I need this? RudderStack's dashboard (control plane) is where you can setup sources, destinations, and transformations. RudderStack hosts the control plane and is free for OSS users. You can also use our open-source config-generator if you don't want to use the hosted control plane (the config generator lacks certain features like Transformations and LiveDebugger.)

Installing the Chart

To install the chart with the release name my-release, from the root directory of this repository:

$ helm install my-release ./ --set rudderWorkspaceToken="<workspace token from the dashboard>"

The above command deploys RudderStack on your default Kubernetes cluster configured with kubectl. The configuration section lists the most significant parameters that can be configured during deployment.

Upgrading the Chart

To update configuration or version of the images used, change the configuration, and run the following command:

$ helm upgrade my-release ./ --set rudderWorkspaceToken="<workspace token from the dashboard>"

Uninstalling the Chart

To uninstall or delete the my-release deployment, run the following command:

$ helm uninstall my-release

This removes all the components created by this chart.


The following table lists the configurable parameters of the RudderStack chart and their default values:





Workspace token from the dashboard



Container image repository for the backend



Container image tag for the backend. Check the Available versions



Container image pull policy for the backend image



Container image repository for the transformer



Container image tag for the transformer. Check the Available versions



Container image pull policy for the transformer image



Extra environments variables to be used by the backend in the deployments

Refer values.yaml file

Each of these parameters can be changed in values.yaml. You can also specify each parameter using the --set key=value[,key=value] argument to helm install. For example:

$ helm install --name my-release \
--set backend.image.version=v0.1.6 \

Configuration specific to:

  • The backend can be edited in config.yaml.

  • PostgreSQL can be configured in pg_hba.conf, and postgresql.conf.


Installing this Helm chart will deploy the following pods and containers in the configured cluster:

POD - {Release name}-rudderstack-0 :

  • rudderstack-backend

  • rudderstack-telegraf-sidecar

POD - {Release name}-rudderstack-postgresql-0 :

  • {Release name}-rudderstack-postgresql

POD - {Release name}-rudderstack-transformer-xxxxxxxxxx-xxxxx:

  • transformer

Contact Us

If you come across any queries or issues while setting up your RudderStack installation on Kubernetes, please feel free to contact us. You can also start a conversation on our Slack channel.