Skip to content

Helm deployment order

Domino Workspace components have dependencies on each other and on a few external services. Deploying them out of order leaves a component unable to authenticate or start correctly. This topic describes the order to follow.

External services to provision first

These are not part of the Domino Workspace Helm charts and must already be reachable before deploying the components that need them:

  • MongoDB — required by Huddo Boards and Chat and Meetings. Minimum version 7.
  • PostgreSQL — required by HCL Forms, and by Domino Traveler. Minimum version 17.
  • Mail Gateway — required to protect inbound/outbound email traffic; Proxmox Mail Gateway (PMG) is recommended if no existing solution is in place.

Step 1: ClamAV (if antivirus scanning is used)

HCL Domino connects directly to a ClamAV service for file-attachment scanning (files servers) and inbound mail scanning (mail servers); Chat and Meetings also connects directly to it (clamdServiceHost) for attachment scanning. Deploy ClamAV first if antivirus scanning is required — Domino's initial bootstrap (One-Touch Setup) is not blocked by its absence, but scanning will not work until ClamAV is reachable.

Step 2: HCL Domino

Deploy HCL Domino and wait for the admin server (dom-admin01a) to complete its initial bootstrap (One-Touch Setup). This is a mandatory prerequisite for every other component below — Domino provides:

  • The OIDC identity provider (auth.<domain>) used by DW Homepage, Huddo Boards, Chat and Meetings, Forms, and HCL DX Search.
  • The LDAP directory used by Huddo Boards, Chat and Meetings, and Forms.

Step 3: Components that authenticate against Domino

Once Domino's admin server is up, deploy, in any order:

  • DW Homepage — uses Domino's OIDC provider.
  • Huddo Boards — uses Domino's OIDC provider and LDAP directory; also needs MongoDB.
  • Chat and Meetings — uses Domino's OIDC provider and LDAP directory; also needs MongoDB and (if antivirus scanning is enabled) ClamAV.
  • HCL Forms — uses Domino's OIDC provider and LDAP directory; also needs PostgreSQL.
  • HCL DX Search — uses Domino's OIDC provider.

No dependency — deploy any time

  • DW Navbar — no dependency on Domino, MongoDB, PostgreSQL, or LDAP.
  • Collabora Online — self-contained; no dependency on the other components.