Helm Chart History¶
Release notes for each Helm chart used by Huddo.
Info
The charts are in our Quay.io registry, with the same access as our images — follow this guide. Log in with helm registry login quay.io before you install or upgrade.
For Component Pack¶
huddo-cp¶
Deploys Huddo into an existing HCL Connections Component Pack cluster. Install guide.
| Version | Description | Breaking Changes |
|---|---|---|
| 2.2.1 | First early access release. See What gets deployed and Configuration | — |
Upgrade command¶
helm registry login quay.io
helm upgrade huddo-cp oci://quay.io/huddo/huddo-cp --version 2.2.1 \
-i -f ./huddo-cp.yaml --namespace connections
The release name must be huddo-cp
The chart's default SOCKET_CLUSTER_HOST is huddo-cp-socketcluster-worker, derived from the release name. Use a different release name only if you also override global.env.SOCKET_CLUSTER_HOST.
Note
Images are date-tagged, so changing global.imageTag recreates the pods automatically on upgrade. If you deploy a floating tag instead, restart the deployments:
kubectl rollout restart deployment -n connections -l release=huddo-cp
Standalone Kubernetes¶
huddo¶
Deploys Huddo into a Kubernetes cluster with an external MongoDB and S3 endpoint. Install guide.
| Version | Description | Breaking Changes |
|---|---|---|
| 2.3.1 | First early access release. See What gets deployed and Configuration | — |
Upgrade command¶
helm registry login quay.io
helm upgrade huddo oci://quay.io/huddo/huddo --version 2.3.1 \
-i -f ./huddo.yaml --namespace huddo
The release name must be huddo
The chart's default SOCKET_CLUSTER_HOST is huddo-socketcluster-worker, derived from the release name. Use a different release name only if you also override global.env.SOCKET_CLUSTER_HOST.