Helm
Go from chart to deployment seamlessly. Kaja lets you deploy and manage Helm charts (databases, APIs, internal services) from the dashboard. Pick a chart, set your values, and deploy—no context switching, no fragmented scripts. This page is about what you do and what you get.
What is a Helm app in Kaja?
A Helm app is one Helm chart deployment inside an environment. You choose the chart (e.g. PostgreSQL, Redis, nginx), the version, and the values. Kaja installs and upgrades it in the right cluster and environment. You see status, pods, and services in the dashboard—same place as your container apps. So: one place for all your deployments, whether they're container images or Helm charts.
Creating a Helm app
- In Kaja, open a cluster and an environment.
- Go to the environment's Helm apps (or Apps) and create a new one.
- Set the chart (e.g.
nginx,bitnami/postgresql) and, if needed, the repository URL and version. - Add values (the settings you'd normally pass to Helm)—key-value, or paste YAML. You can also pull values from config or secrets in the cluster.
- Submit. Kaja deploys the chart. You see status and can open logs from the same dashboard.
No need to run helm install yourself. Same workflow for every chart, in every environment.
Chart, repository, and version
- Chart — The name of the chart (e.g.
nginx). If the chart comes from a specific repo, you add the repository URL once; Kaja uses it for that app. - Version — Pin a version for repeatable deploys, or leave it blank to use the latest.
- Values — The overrides for the chart. Simple key-value in the UI, or paste a YAML block. You can also reference config maps or secrets so sensitive or shared config stays out of the UI.
Exposing a Helm app to other environments
Sometimes one environment needs to use a service from another (e.g. a shared database). You can expose a Helm app so that other environments you allow can reach it. On the environment you set which envs can send traffic in; on the Helm app you turn on "expose to other environments" and optionally limit which envs can access it. So you get shared services without opening everything up.
Details depend on your setup; the dashboard guides you through the options.
Updating and reapplying
Change the chart version or values in the dashboard and save—Kaja upgrades the release in place. If something went wrong or you want to force a fresh apply, use Reapply in the UI. You stay in one place; no hopping to the cluster to run helm upgrade.
Status, pods, and logs
The dashboard shows whether the release is deployed, pending, or failed. You see the pods and services the chart created, and you can open Logs for that Helm app just like for a container app. So debugging and observability stay in Kaja.
Summary
| What | What you get |
|---|---|
| Helm app | One Helm chart deployment in an environment. Deploy, update, and reapply from the dashboard. |
| Values | Set chart options in the UI (key-value or YAML) or from config/secrets. |
| Expose | Let other environments use this app's services (e.g. shared DB) when you need it. |
Zero-friction deployments. One place for multi-chart management. That's the value.
Next steps
- Environments — Where Helm apps run; spin up and pause envs.
- Apps — Container and Helm app features in depth.
- Logs & metrics — View logs and metrics for your apps.
- Connecting clusters — Add clusters so you can deploy to them.