For the complete documentation index, see llms.txt. This page is also available as Markdown.

Self-Hosted Chart

Helm values for the self-hosted Pipekit chart.

The Self-Hosted Pipekit Helm chart (pipekit/pipekit) installs the entire stack (UI, API, ID service, Postgres, Pipekit Agent) into a single Kubernetes namespace.

This page links to the canonical values reference and covers the most commonly tuned values. For the install procedure, see Self-Hosting > Deploy > Helm Install. For a 30-minute trial install on a local cluster, see Self-Hosting > Evaluate Self-Hosted.

Discovering values

The Pipekit values file is commented in-place. Every value's purpose is documented next to it. To dump the values for the version you have installed:

helm show values pipekit/pipekit --version <version>

For your current install's values:

helm get values pipekit -n pipekit

Required values

Value
Type
Purpose

license.key

string

Your Pipekit license key. Required for any non-dev install.

global.deployType

enum

dev for local evaluation; ci for CI; prod for production. Controls resource defaults.

imagePullSecrets[].name

string[]

Name of the regcred Secret with credentials for the pipekitprivate Docker Hub repository.

Common production tunings

Value
Purpose

<service>.replicas

Replica count per service. Defaults are sized for dev; bump for prod.

<service>.resources.requests

CPU and memory requests per service. The dev defaults are small; production deployments typically scale these 4-10x.

<service>.hpa.enabled

Enable the Horizontal Pod Autoscaler for a service.

<service>.hpa.{min,max}Replicas

HPA replica bounds.

<service>.pdb.enabled

Enable a Pod Disruption Budget. Strongly recommended for prod.

gitProviders.{github,gitlab,bitbucket,azureDevOps}.enabled

Enable a Git provider. See Configure > Git Provider.

gatewayAPI.enabled

Use Gateway API resources instead of Ingress. Pair with gatewayAPI.httpRoute.

postgres.external.enabled

Point Pipekit at a managed Postgres instead of the in-cluster bundled instance. Required for production HA.

Where each service's values live

Each Pipekit service has its own block in the chart's values.yaml. The blocks all follow the same shape: image, resources, replicas, hpa, pdb, livenessProbe, readinessProbe.

Service
Block prefix
Notes

UI

ui.*

Web app; usually behind an ingress or Gateway HTTPRoute.

Users API

users.*

Main API for Pipes/Runs/Workflows.

ID

id.*

Authn (SSO, MFA, user creation).

Events Handler

eventsHandler.*

Webhook receiver for Git providers; only enabled if you wire up GitHub/GitLab/Bitbucket/Azure DevOps.

Messenger

messenger.*

Redis-backed queue + log broker between Users and Pipekit Agent.

Notifications

notifications.*

Email / Slack / Teams alert dispatch.

Pipekit Agent

pipekitAgent.*

In-cluster component. Often configured separately via the agent's own Helm chart.

Metrics Operator

metricsOperator.*

OTel-based workflow metrics. Optional.

Postgres

postgres.*

Embedded for dev; external for prod.

For the full annotated reference, see Self-Hosting > Deploy > Helm Install, which embeds the chart's values.yaml with every parameter documented inline.

  • Agent Chart Values: values reference for the pipekit-agent chart used in BYOC / Pipekit Cloud deployments.

  • Self-Hosting > Configure: post-install configuration (initial login, SSO, Git providers, agent options).

Last updated