Chart values

Every value of the Harthelm Helm chart, grouped by topic. Each table lists the value's path, its type, its default and what it does. A long default (a list of plans, say) is printed as YAML under the table. Link to a single value with its path as the anchor, for example /reference/chart-values/platform-and-sign-in/#platform.host.

Set valuesCopy Anchor Link

Two values are required: platform.host and platform.workspaceDomain. Most installations also set up sign-in and give the licence in a Secret. Keep your values in one file under version control:

platform:
  host: console.example.com          # the console and the API
  workspaceDomain: example-apps.net  # workspace hosts: <ws>-<port>.example-apps.net, ide-<ws>.example-apps.net
oidc:
  issuer: https://sso.example.com
  existingSecret: harthelm-oidc      # a Secret with the client's id and secret
license:
  existingSecret: harthelm-license   # a Secret with the licence file

The workspace domain must be a different registrable domain from the console's, so workspace apps cannot read the console's cookies.

Install or upgrade with the file:

helm upgrade --install harthelm oci://<your registry>/charts/harthelm --version 1.1.0 \
  -n harthelm-system --create-namespace -f my-values.yaml

Check values before you apply themCopy Anchor Link

The chart ships a strict values.schema.json. Helm checks your values against it before it renders anything, and an unknown key or a value of the wrong type fails the install or upgrade with a message that names it. The schema also refuses combinations that cannot work, among them:

• an empty platform.host or platform.workspaceDomain;
• database.mode external without a secret that holds the DSN;
• routing.edge gatewayAPI without parentRefs;
• an oidc.issuer without oidc.existingSecret.

Render the chart locally to see these errors before anything reaches the cluster. This matters most with Argo CD, where an invalid value leaves the application Unknown instead of failing loudly:

helm template harthelm oci://<your registry>/charts/harthelm --version 1.1.0 -f my-values.yaml > /dev/null

When the values pass the schema, a preflight Job still runs before every install and upgrade. It checks that the cluster has what the values name (the Kubernetes version, the operators, Secrets and their keys, storage classes) and fails with a list of what is missing before anything of the release changes. See Hooks and extra objects to tune or turn it off.

Write sizesCopy Anchor Link

Memory and storage values, such as a plan's memoryMiB and storageGiB or a team quota, take a number in the unit their name says, or a string with a binary unit: 2Gi, 2GiB, 2048Mi, 2048MiB. Storage must be whole GiB. Decimal units such as 2GB are refused.

Find a valueCopy Anchor Link

For how to use the values for one task each, see Self-hosting › Configure.