Skip to content

Helm deployment prerequisites

Before deploying any Domino Workspace component with Helm, make sure the following are in place.

Common to every component

  • A running Kubernetes cluster, version 1.32 or later, with kubectl installed and configured to reach it. See RKE2 example if starting from scratch.
  • If the distribution ships with a bundled ingress controller enabled by default (RKE2, for example, includes one), disable it. Check the distribution's own documentation for the current default and how to disable it — APISIX handles that role instead.
  • Helm installed.
  • Credentials to the HCL container registry (hclcr.io), used before pulling any chart:
helm registry login hclcr.io --username <username> --password <password>

The same login is required for every helm pull / helm show values command shown in the Helm chart documentation.

  • A StorageClass — see storage setup.
  • A custom values file for the target environment (domain, resource sizing, credentials). Each component's chart documentation shows where to add it in the install command.
  • Several components use randomly-generated string secrets (session secrets, signing keys, and similar). Generate these as plain alphanumeric strings — upper and lower case letters and digits, no special characters — at least 32 characters long, e.g. openssl rand -hex 32.

Component-specific prerequisites

Some components need more than the above — for example, HCL Domino requires an APISIX gateway with the dom-router plugin, and ClamAV requires cert-manager. Check the "Prerequisites" section of the component's own chart documentation, listed on the Helm overview page, before deploying it.