Skip to content

Helm charts

Work in progress

Helm chart support is under active development. Not all components have charts yet, and existing charts may change. This page will be updated as chart coverage is completed.

As an alternative to the GitOps-based deployment, individual platform components can be installed via Helm charts. This suits teams integrating dataLOFT components into an existing Kubernetes setup without adopting the full dataLOFT-gitops configuration.

Chart sources live in two consolidated repositories:

Available charts

Chart Repository Path
birds-eye-view dataLOFT-platform/helm birds-eye-view/
fed-cat dataLOFT-platform/helm fed-cat/
hst-did dataLOFT-platform/helm hst-did/
r-squared dataLOFT-platform/helm r-squared/
signature-auth-handler dataLOFT-platform/helm signature-auth-handler/
rdsp-s3 go-dataspace/helm rdsp-s3/
reference-authn-service go-dataspace/helm reference-authn-service/
reference-contract-service go-dataspace/helm reference-contract-service/
run-dsp go-dataspace/helm run-dsp/
run-dsp-stack go-dataspace/helm run-dsp-stack/

fed-cat and signature-auth-handler declare hst-did as an optional subchart dependency. run-dsp-stack is an umbrella chart that pulls in run-dsp, rdsp-s3, reference-authn-service, and reference-contract-service for a complete RUN-DSP deployment.

OCI distribution

Both repos publish charts as OCI artifacts on three channels each, under their respective registry namespaces — oci://codeberg.org/dataloft-platform/ and oci://codeberg.org/go-dataspace/:

Channel Versioning Source Purpose
helm/<chart> X.Y.Z (immutable) release tags production-grade releases
helm-main/<chart> 0.0.0-main.<N>.<sha7> every merge to main rolling builds, auto-deployable
helm-test/<chart> 0.0.0-test.<N>.<sha7> manual trigger on a PR branch ad-hoc validation builds

Install a release with:

# platform charts
helm install <name> oci://codeberg.org/dataloft-platform/helm/<chart> --version <X.Y.Z>

# connector charts
helm install <name> oci://codeberg.org/go-dataspace/helm/<chart> --version <X.Y.Z>

Release flow

Both repos follow the same trunk-based model: a single main branch with releases cut as git tags <chart>-v<X.Y.Z>. Every change to a chart requires a Chart.yaml version: bump; CI enforces this. After merge, the helm-main artifact is published automatically; an operator then cuts the release tag at the validated commit, which triggers publication to helm/<chart>:X.Y.Z.

Full contributor and operator details live in each repo's README and CI/CD runbook: