Helm Chart History¶
Release notes for each Helm chart utilised by Boards
Important
As of January 2023 we have moved our image hosting. Please follow this guide to configure your Kubernetes with access to our images hosted in Quay.io.
For Component Pack¶
huddo-boards-cp¶
Danger
As of huddo-boards-cp-2.0.0.tgz we have migrated from ingress-nginx to Traefik. Please follow our migration guide.
Tip
As of huddo-boards-cp-2.1.0.tgz we have added SeaweedFS S3 storage with a migration path from MinIO. We recommend this as a replacement for MinIO. See SeaweedFS migration guide.
| Version | Description | Breaking Changes |
|---|---|---|
| 1.0.0 | Initial release (Huddo) | No |
| 1.1.0 | CNX 8 fix for Mongo 5 | No |
| 1.1.1 | Support custom storageClassName instead of PV |
No |
| 1.2.0 | Added readiness probes on each service | No |
| 1.2.1 | Fix ingress session cookie SameSite setting (polling in a CORS frame, e.g. Teams) |
No |
| 1.3.0 | Support CNX 8 Mongo 7 (use ConfigMap mongo-name instead of mongo5-rs-members-hosts) with images after 2025-02-13 |
No |
| 1.3.1 | Change ingress.pathType to ImplementationSpecific to allow regex rewrites |
Potentially – may affect ingress matching behaviour |
| 1.4.0 | Support CNX 8 CR13 cache rename - new environment variables in ConfigMap and Secret references | No |
| 2.0.0 | Move from ingress-nginx to traefik | Yes – migration required |
| 2.1.0 | Add SeaweedFS S3 storage with migration path from MinIO | Optional – migration only if adopting SeaweedFS |
| 2.2.0 | Merge activity-migration as optional component (migration.enabled, default false) |
No – uninstall the standalone activity-migration release before enabling |
| 2.3.0 | Auto-create secrets: CA bundle mount (global.internalCa), extraObjects, and imageCredentials (image pull secret) |
No |
| 2.3.1 | Drop legacy support for removed v1beta1 APIs (Deployment, Ingress, PodSecurityPolicy) |
No |
| 2.3.2 | Drop deprecated Traefik StripPrefix forceSlash option (clears the ForceSlash deprecation warning in Traefik logs; no behaviour change) |
No |
| 2.3.3 | SeaweedFS migration Job now verifies the sync and prints a report (totals, missing, size mismatch, orphans) to its logs (s3.migration.verify, default true); completed Job kept for 1h so the report stays readable |
No |
| 2.3.4 | Pod annotations for service mesh injection: global.podAnnotations applies to every pod, per-component podAnnotations merge on top, and s3.jobPodAnnotations lets the S3 Job pods opt out of the mesh |
No – defaults render unchanged |
| 2.3.5 | SeaweedFS now runs as user 1000 instead of root (matches MinIO; fixes startup permission denied on NFS exports with root_squash). The data directory is chowned automatically on start (s3.persistence.fixOwnership). The SeaweedFS Deployment now uses the Recreate strategy, so S3 is briefly unavailable while it restarts during an upgrade. New s3.persistence.nfs.mountOptions for extra NFS mount options on the PV |
No – unless you set s3.persistence.fixOwnership: false |
| 2.3.6 | s3.volumeMax and s3.volumeSizeLimitMB set the SeaweedFS storage ceiling. The SeaweedFS defaults cap an instance at about 240 GB; installs with a larger dataset must raise s3.volumeMax. See capacity planning |
No – defaults unchanged |
Note
As of huddo-boards-cp-2.3.5.tgz the SeaweedFS pod runs as user 1000 instead of root (the same as the MinIO pods since 1.0.0).
Existing SeaweedFS data is owned by root, and Kubernetes does not apply fsGroup ownership to NFS volumes, so the chart runs a short init container that chowns the data directory to 1000:1000 before SeaweedFS starts. No manual step is required.
If your cluster's Pod Security admission forbids a root container, set s3.persistence.fixOwnership: false and chown the directory yourself on the NFS server instead:
cd /pv-connections/huddo-boards-s3/
chown 1000:1000 -R .
Alternatively set s3.securityContext.enabled: false to keep running as root.
Note
The SeaweedFS pod also moves to the Recreate deployment strategy in 2.3.5. SeaweedFS holds a lock on its storage volume, so the old pod must stop before the new one starts — expect a short gap in S3 availability (and therefore file uploads and downloads) while it restarts during the upgrade.
Upgrade command¶
helm upgrade huddo-boards-cp https://docs.huddo.com/assets/config/kubernetes/huddo-boards-cp-2.3.6.tgz -i -f ./boards-cp.yaml --namespace connections
Also available on Quay.io (OCI)
The chart is also published to our Quay.io registry as an OCI artifact. Log in first with the same Quay.io credentials you use for our images (see the image access guide):
helm registry login quay.io
helm upgrade huddo-boards-cp oci://quay.io/huddo/huddo-boards-cp --version 2.3.6 -i -f ./boards-cp.yaml --namespace connections
Note
Boards images are date-tagged, so each release changes the global env and pods are recreated automatically on upgrade.
huddo-boards-cp-activity-migration (DEPRECATED)¶
Note
This chart is deprecated as it has been merged into huddo-boards-cp chart as of v2.2.0 as an optional component. Set migration.enabled: true in your values file to enable it.
Before enabling, uninstall any existing standalone release — both create the same PersistentVolume (connections-shared-drive), PersistentVolumeClaim (connections-shared-drive-claim) and Service (boards-activity-migration):
helm uninstall huddo-boards-cp-activity-migration --namespace connections
| Version | Description | Breaking Changes |
|---|---|---|
| 1.0.0 | Initial release (Huddo) | No |
| 1.1.0 | CNX 8 fix for Mongo 5 | No |
| 1.2.0 | Fix resource limits | No |
| 1.3.0 | Support CNX 8 Mongo 7 | No |
| 1.4.0 | Support CNX 8 CR13 cache rename - new env variables in ConfigMap and Secret references | No |
Standalone Kubernetes¶
Danger
As of huddo-boards-2.0.0.tgz we have migrated from ingress-nginx to Traefik. Please follow our migration guide.
huddo-boards¶
| Version | Description | Breaking Changes |
|---|---|---|
| 1.0.0 | Initial release (Huddo) | No |
| 1.1.0 | Allow additionalPaths on huddo-app ingress | No |
| 1.1.1 | Fix ingress session cookie SameSite setting (polling in a CORS frame, e.g. Teams) |
No |
| 2.0.0 | Move from ingress-nginx to traefik | Yes – migration required |
| 2.1.0 | Auto-create secrets: CA bundle mount (global.internalCa), extraObjects, and imageCredentials (image pull secret) |
No |
| 2.1.1 | Drop legacy support for removed v1beta1 APIs (Deployment, Ingress) |
No |
| 2.1.2 | Drop deprecated Traefik StripPrefix forceSlash option (clears the ForceSlash deprecation warning in Traefik logs; no behaviour change) |
No |
| 2.1.3 | Pod annotations for service mesh injection: global.podAnnotations applies to every pod, per-component podAnnotations merge on top |
No – defaults render unchanged |
Upgrade command¶
helm upgrade huddo-boards https://docs.huddo.com/assets/config/kubernetes/huddo-boards-2.1.3.tgz -i -f ./boards.yaml --namespace boards
Also available on Quay.io (OCI)
The chart is also published to our Quay.io registry as an OCI artifact. Log in first with the same Quay.io credentials you use for our images (see the image access guide):
helm registry login quay.io
helm upgrade huddo-boards oci://quay.io/huddo/huddo-boards --version 2.1.3 -i -f ./boards.yaml --namespace boards
Note
Boards images are date-tagged, so each release changes the global env and pods are recreated automatically on upgrade.
huddo-boards-activity-migration¶
| Version | Description | Breaking Changes |
|---|---|---|
| 1.0.0 | Initial release (Huddo) | No |
| 1.2.0 | Fix resource limits | No |
| 1.2.1 | Drop legacy support for removed v1beta1 Deployment API |
No |
Info
The previous chart information has moved here