Conduktor Console on Kubernetes — Helm deployment guide

Overview

Conduktor provides a Helm repository containing a chart that will deploy Conduktor Platform on your Kubernetes cluster. We don’t provide any relational database dependency, you will have to provide your own database. See the production requirements for details. For a full reference of our recommended Conduktor platform deployment architecture, see our sample GitHub repository . Check out the snippets section for more examples.

# Setup Helm repository
helm repo add conduktor https://helm.conduktor.io
helm repo update

export ADMIN_EMAIL="<your_admin_email>"
export ADMIN_PASSWORD="<your_admin_password>"
export ORG_NAME="<your_org_name>"
export NAMESPACE="<your_kubernetes_namespace>"

# Deploy Helm chart
helm install console conduktor/console \
  --create-namespace -n ${NAMESPACE} \
  --set config.organization.name="${ORG_NAME}" \
  --set config.admin.email="${ADMIN_EMAIL}" \
  --set config.admin.password="${ADMIN_PASSWORD}" \
  --set config.database.password="<your_postgres_password>" \
  --set config.database.username="<your_postgres_user>" \
  --set config.database.host="<your_postgres_host>" \
  --set config.database.port="5432" \
  --set config.license="${LICENSE}" # can be omitted if deploying the free tier
    
# Port forward to access Conduktor
kubectl port-forward deployment/console -n ${NAMESPACE} 8080:8080
open http://localhost:8080

Chart dependencies

All charts within this repository have one dependency which is bitnami-common. You can find the chart here: https://github.com/bitnami/charts/tree/main/bitnami/common

Compatibility matrix

Find out which versions of Conduktor Platform work on which version of our Conduktor Platform Helm chart.

We recommend you use the version of Platform that comes pre-configured with the Helm chart. You can adjust the version in your values property according to the supported Platform version, if required.

Notes column only lists chart-level changes. See release notes to determine whether there are breaking changes within the artifacts.

Helm chart compatibility

Breaking changes: 🟡 - Breaks additional services (e.g. Grafana dashboard changes) 🔴 - Breaks overall deployment of the product (e.g. renaming variables in .values, major product releases)

Chart version	Default App Version	Min App Version	Release date	Notes
console-1.31.1	1.46.1	1.25.1	2026-06-29
console-1.31.0	1.46.0	1.25.1	2026-06-16
console-1.30.2	1.45.1	1.25.1	2026-05-27
console-1.30.1	1.45.1	1.25.1	2026-05-14
console-1.30.0	1.45.0	1.25.1	2026-05-05
console-1.29.2	1.44.2	1.25.1	2026-06-04
console-1.29.1	1.44.1	1.25.1	2026-03-27
console-1.29.0	1.44.0	1.25.1	2026-03-18
console-1.28.3	1.43.3	1.25.1	2026-03-11
console-1.28.2	1.43.2	1.25.1	2026-02-27
console-1.28.1	1.43.1	1.25.1	2026-02-16
console-1.28.0	1.43.0	1.25.1	2026-02-11
console-1.27.1	1.42.0	1.25.1	2026-02-02
console-1.27.0	1.42.0	1.25.1	2026-01-29
console-1.26.1	1.41.0	1.25.1	2026-01-08
console-1.26.0	1.41.0	1.25.1	2025-12-12
console-1.25.0	1.40.0	1.25.1	2025-11-17
console-1.24.0	1.39.0	1.24.0	2025-10-27
console-1.23.0	1.38.0	1.24.0	2025-10-01
console-1.22.1	1.37.1	1.24.0	2025-09-19
console-1.22.0	1.37.0	1.24.0	2025-08-21
console-1.21.2	1.36.2	1.24.0	2025-08-05
console-1.21.1	1.36.1	1.24.0	2025-07-22
console-1.21.0	1.36.0	1.24.0	2025-07-18
console-1.20.3	1.35.2	1.24.0	2025-07-03
console-1.20.2	1.35.1	1.24.0	2025-06-26
console-1.20.1	1.35.0	1.24.0	2025-06-19
console-1.20.0	1.35.0	1.24.0	2025-06-19
console-1.19.1	1.34.2	1.24.0	2025-05-26
console-1.19.0	1.34.0	1.24.0	2025-05-14
console-1.18.0	1.33.0	1.24.0	2025-04-09
console-1.17.1	1.32.1	1.24.0	2025-03-25
console-1.17.0	1.32.0	1.24.0	2025-03-12
console-1.16.2	1.31.2	1.24.0	2025-03-04
console-1.16.1	1.31.1	1.24.0	2025-02-19
console-1.16.0	1.31.0	1.24.0	2025-02-06
console-1.15.1	1.30.0	1.24.0	2025-01-15
console-1.15.0	1.30.0	1.24.0	2024-12-16
console-1.14.2	1.29.2	1.24.0	2024-12-09
console-1.14.1	1.29.1	1.24.0	2024-11-28
console-1.14.0	1.29.0	1.24.0	2024-11-25
console-1.13.0	1.28.0	1.24.0	2024-10-15
console-1.12.1	1.27.1	1.24.0	2024-09-26
console-1.12.0	1.27.0	1.24.0	2024-09-13
console-1.11.0	1.26.0	1.24.0	2024-08-19
console-1.10.0	1.25.1	1.24.0	2024-07-24
console-1.9.1	1.24.1	1.24.0	2024-06-24
console-1.9.0	1.24.0	1.24.0	2024-06-19	🔴 Changed liveness and readiness probe path see here
console-1.8.1	1.23.0	1.22.0	2024-05-10
console-1.7.2	1.22.0	1.22.0	2024-04-03	🔴 Service Monitor endpoint changes, Grafana template changes see here
console-1.6.2	1.21.1	1.21.0	2024-03-18
console-1.6.1	1.21.1	1.21.0	2024-03-05
console-1.6.0	1.21.0	1.21.0	2024-02-26	🔴 Paths and folder changed see here
console-1.5.5	1.20.0	1.17.3	2024-01-23
console-1.5.4	1.20.0	1.17.3	2024-01-10	🟡 Updated Grafana template see here
console-1.5.3	1.20.0	1.17.3	2024-01-05	🟡 Updated Grafana template see here
console-1.5.2	1.20.0	1.17.3	2024-01-04	🟡 Updated Grafana template see here
console-1.5.1	1.20.0	1.17.3	2023-12-19
console-1.5.0	1.20.0	1.17.3	2023-12-18
console-1.4.2	1.19.2	1.17.3	2023-11-24
console-1.4.1	1.19.1	1.17.3	2023-11-15
console-1.4.0	1.19.0	1.17.3	2023-11-02
console-1.3.9	1.18.4	1.17.3	2023-11-02
console-1.3.8	1.18.4	1.17.3	2023-10-19
console-1.3.7	1.18.3	1.17.3	2023-10-10
console-1.3.6	1.18.2	1.17.3	2023-10-10
console-1.3.5	1.18.1	1.17.3	2023-10-03
console-1.3.4	1.18.1	1.17.3	2023-09-29
console-1.3.3	1.18.1	1.17.3	2023-09-27
console-1.3.2	1.18.0	1.17.3	2023-09-27
console-1.3.1	1.18.0	1.17.3	2023-09-27
console-1.3.0	1.18.0	1.17.3	2023-09-19
console-1.2.4	1.17.3	1.17.3	2023-09-08
console-1.2.3	1.17.3	1.17.3	2023-09-08
console-1.2.2	1.17.3	1.17.3	2023-09-08
console-1.2.1	1.17.3	1.17.3	2023-09-08
console-1.2.0	1.17.3	1.17.3	2023-09-08
console-1.1.4	1.17.3	1.17.3	2023-09-07	🔴 Fixed issue with license checksum see here
console-1.1.3	1.17.3	1.17.2	2023-09-07
console-1.1.2	1.17.3	1.17.2	2023-09-07
console-1.1.1	1.17.3	1.17.2	2023-09-06
console-1.1.0	1.17.3	1.17.2	2023-09-01
console-1.0.3	1.17.3	1.17.2	2023-08-30
console-1.0.2	1.17.3	1.17.2	2023-08-29
console-1.0.1	1.17.3	1.17.2	2023-08-21
console-1.0.0	1.17.2	1.17.2	2023-08-17

General requirements

Basic knowledge of Kubernetes
Kubernetes cluster 1.19+ (set up a local cluster )[^1]
Kubectl (install ) with proper kube context configured
Helm 3.1.0+ (install )

Production requirements

Mandatory for production environments:

set up an external PostgreSQL (13+) database with an appropriate backup policy
set up an external S3 Bucket
allow enough resources to run Conduktor with the recommended configuration

A note on TLS and URL forwarding

For production environments, we recommend to run with TLS enabled from your ingress controller and terminating on Platform. This creates a more secure connection, while also telling Platform that it should use TLS when forwarding on any URL requests (e.g. requests to SSO providers). Without TLS terminating on Platform itself, requests between the ingress controller and Platform will be in plain text, as will URL forwarding to your SSO provider which can lead to rejection of the request for not being secure.

1. Set up Helm repository

helm repo add conduktor https://helm.conduktor.io
helm repo update

2. Install the Console chart

Configure Console with the following values:

values.yaml

config:
  organization:
    name: "<your_org_name>"

  admin:
    email: "<your_admin_email>"
    password: "<your_admin_password>"

  database:
    host: '<postgres_host>'
    port: 5432
    name: '<postgres_database>'
    username: '<postgres_username>'
    password: '<postgres_password>'
    
  # HERE you can paste the console configuration (under the config key)

Install the chart on your cluster:

helm install console conduktor/console \
  --create-namespace -n conduktor \
  --values values.yaml \
  --set config.license="${LICENSE}" # can be omitted if deploying the free tier

Once deployed, you will be able to access Conduktor on localhost:8080 by using a port-forward. You can also configure an ingress to make Platform available externally, check out snippets.

kubectl port-forward deployment/console -n ${NAMESPACE} 8080:8080

3. Configure Console

Fresh install

You can configure Platform by inserting it into the config section of the values.yaml file.

Based on a Docker configuration

If you’re already using a config file within Docker,you can use it by giving it to the Helm chart with the following command:

values.yaml

config:
  organization:
    name: "<your_org_name>"

  admin:
    email: "<your_admin_email>"
    password: "<your_admin_password>"
    
  database:
    host: '<postgres_host>'
    port: 5432
    name: '<postgres_database>'
    username: '<postgres_username>'
    password: '<postgres_password>'
    
  # HERE you can paste the console configuration (under the config key)

Configure with an enterprise license

values.yaml

config:
  organization:
    name: "<your_org_name>"

  admin:
    email: "<your_admin_email>"
    password: "<your_admin_password>"
    
  database:
    host: '<postgres_host>'
    port: 5432
    name: '<postgres_database>'
    username: '<postgres_username>'
    password: '<postgres_password>'

  license: "<your_license>"

  # HERE you can paste the console configuration (under the config key)

Examples

Find sample code on our GitHub .

Deploy Console with a context path

Console v1.41.0 introduces the option to configure an ingress with a context path, such as mycompany.com/conduktor. To configure this, set the CDK_PLATFORM_EXTERNAL_URL environment variable or the config.platform.external.url property to include the full URL with the context path. Here’s an example using /conduktor as the context path with an nginx ingress controller:

values.yaml

config:
  platform:
    external:
      url: "https://conduktor.my-domain.com/conduktor"

ingress:
  enabled: true
  hostname: conduktor.my-domain.com
  ingressClassName: nginx
  tls: true
  path: /conduktor(/|$)(.*)
  pathType: ImplementationSpecific
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2

Check the requirements of your ingress controller - you may need to add specific annotations and patterns to the path. As shown in the example above, your ingress controller has to also remove the context path when redirecting requests to Console.

Secure metric endpoints with basic auth

Starting with Console v1.42.0, you can protect the metric scraping endpoints (/api/monitoring/metrics and /monitoring/metrics/) with basic auth credentials.

values.yaml

config:
  monitoring:
    basicauth:
      email: "metrics@example.com"
      password: "Hello123!"

When configured, your monitoring backend (Prometheus, Cortex, etc.) has to provide these credentials when scraping Console metrics. Learn more about configuring your monitoring backend.

Basic auth is optional in Console v1.42.0 and no configuration changes are required for existing deployments.

​Overview

​Chart dependencies

​Compatibility matrix

​Helm chart compatibility

​General requirements

​Production requirements

​A note on TLS and URL forwarding

​1. Set up Helm repository

​2. Install the Console chart

​3. Configure Console

​Fresh install

​Based on a Docker configuration

​Configure with an enterprise license

​Examples

​Deploy Console with a context path

​Secure metric endpoints with basic auth

​Related resources

Overview

Chart dependencies

Compatibility matrix

Helm chart compatibility

General requirements

Production requirements

A note on TLS and URL forwarding

1. Set up Helm repository

2. Install the Console chart

3. Configure Console

Fresh install

Based on a Docker configuration

Configure with an enterprise license

Examples

Deploy Console with a context path

Secure metric endpoints with basic auth

Related resources