Harthelm Docs

Hooks and extra objects

Chart values: preflight, tests, extraObjects.

Generated from charts/harthelm/values.yaml at v1.5.0

preflight

The preflight Job: a Helm pre-install and pre-upgrade hook and an Argo CD PreSync hook, before the pre-migration dump. It checks what an install needs (Kubernetes version, the CRDs and API groups the values ask for, the Secrets the values name, the database's reachability once it exists, the storage class) and fails the sync with a list of what is missing, so nothing changes on a cluster that cannot run the release.

ValueTypeDefaultDescription
preflight.enabledbooleantrue
preflight.resources.requests.cpustring or number"20m"
preflight.resources.requests.memorystring or number"32Mi"
preflight.resources.limits.memorystring or number"128Mi"

tests

helm test <release>: a probe that NetworkPolicies are enforced, endPort ranges included; core shows the result on the admin Capabilities page and in hart admin doctor. Argo CD has no test phase: there a report-only copy runs as a PostSync hook after every sync; with plain Helm run helm test once after an install or a CNI change.

ValueTypeDefaultDescription
tests.networkPolicy.enabledbooleantrue
tests.resources.requests.cpustring or number"10m"
tests.resources.requests.memorystring or number"16Mi"
tests.resources.limits.memorystring or number"64Mi"

extraObjects

Extra objects rendered with the release (full manifests), for what the chart cannot know, for example a CiliumNetworkPolicy that lets the platform pods reach the API server.

ValueTypeDefaultDescription
extraObjectslist of object[]

On this page