Configuration
How Harthelm is configured: one values file, rendered before every change, and where each topic lives.
Everything an operator configures is a value of the Helm chart. There is no settings page for the platform and no configuration in the database: change the values, render them, and upgrade the release. The chart values reference lists every key with its type, default and meaning.
Change a value
Edit your values file
Keep one file (my-values.yaml in these pages) with only the keys you change, in version control.
Render it
The schema is strict: an unknown key, an empty host, database.mode: external without a DSN Secret, or an OIDC issuer
without its Secret fail the render.
helm template harthelm oci://<your registry>/charts/harthelm --version <version> \
-n harthelm-system -f my-values.yaml > /dev/nullApply it
helm upgrade harthelm oci://<your registry>/charts/harthelm --version <version> \
-n harthelm-system -f my-values.yamlThe preflight Job checks the cluster against the new values first. A change of core's settings restarts core, which does not stop running workspaces. Under Argo CD, commit the file instead.
Where each topic lives
| Topic | Page | Main values |
|---|---|---|
| Sign-in and cluster admins | Sign-in | oidc, auth.breakGlass |
| Hosts, certificates, in-cluster TLS | DNS and TLS | platform, routing, internal.tls, trustedProxies |
| Workspace volumes | Storage | storage, security.defaultUid |
| Plans, base images, sleep, scheduling | Workspaces | plans, baseImages, workspaces, wake, scheduling |
| Git repositories | Git providers | git.providers |
| Invitation mails | mail | |
| Teams' own domains | Custom domains | customDomains |
| Your own PostgreSQL | External database | database |
| Databases for users | Managed services | marketplace |
| Isolation and egress | Network policies | networkPolicy, teams.network |
| Organizations, teams, quotas | Team administration | tenancy, teams.quota |
| Backups | Backups and restore | backup |
| Upgrades | Upgrades | core.updateStrategy, workspaces.upgradePolicy |
Sizes
Memory and storage values take what the console and hart take: a number in the key's unit (a plain quota number is
bytes, as in Kubernetes) or a string such as 2Gi, 2GiB, 2048Mi or 2048MiB. Storage must be whole GiB; decimal
units such as 2GB are refused.