Generic Helm: any Helm chart¶
The Generic Helm template deploys any Helm chart, with its own values, to try out software before it has a dedicated template. It only appears in the catalogue when the GENERIC_HELM_ENABLED cluster setting is true, and it is reserved for namespace administrators.
Unlike the other templates, it wires no HTTPS route, certificate or authentication: the chart is installed as is.
Deploying a chart¶
| Field | Purpose |
|---|---|
| Chart reference | Chart name in its repository (nginx), or full OCI reference (oci://registry/path/chart). |
| Helm repository URL | Classic chart repository (https://charts.example.com). Ignored for an oci:// reference. |
| Chart version | Version to install; the latest one if empty. |
| Helm values (YAML) | Values passed to the chart, in a YAML editor. |
Once the reference (and optionally the version) is entered, Load the chart's default values fills the editor with the chart's values.yaml, comments included: then change only what needs changing. If values have already been entered, the Control Panel asks before replacing them. Show README displays the chart's documentation.
If the chart ships a values schema (values.schema.json, flagged by Values schema provided), Helm checks the values on deployment and rejects those that don't match it, with the chart's error message.
Upgrading the release¶
On the application card, Version, values and history opens the Helm release.
The Version and values tab shows the chart version and the values currently deployed. The labels and annotations the Control Panel sets to track the application are not shown: they are added back automatically on every upgrade.
- Check submits the upgrade to Helm without applying anything (
helm upgrade --dry-run): values schema, manifest rendering, version availability. - Upgrade applies the new chart version and the new values.
- Default values of this version and README show, next to the editor, those of the version entered, to compare before a version upgrade.
Application deployed before this feature
The chart source (reference and repository) was not recorded. The tab asks for it once; it is kept after the first upgrade.
History and rollback¶
The History tab lists the release's revisions, most recent first: status, chart and version, application version, date and Helm description. Values shows those of a revision.
Roll back to this revision (after confirmation) restores the chart version and values of that revision (helm rollback). The rollback creates a new revision: history is kept, and you can move forward again the same way.