⚓ Helm Registry
Where the charts live
Most services are a ⚓ Helm Chart developed in the public
datalayer/helm-charts GitHub
repository, checked out as a submodule at $PLANE_HOME/etc/helm.
The charts for Contents and the storage under it are not public. They are
in the Plane repository itself, at $PLANE_HOME/etc/helm-private, alongside
the other private charts:
| Chart | What it deploys |
|---|---|
datalayer-contents | The Contents control and data plane |
datalayer-shared-filesystem | The RWX claim every home folder lives on |
datalayer-ceph-operator, datalayer-ceph-cluster | Ceph, one of the three shared-filesystem backends |
datalayer-node-mounts | The node DaemonSet: the Local CSI driver and the Node Mount Gateway agent |
datalayer-datashim | Datashim, on its way out |
datalayer-data-server | The outbound query gateway for a customer network |
Both trees have the same shape, so a chart path is the only thing that differs:
$PLANE_HOME/etc/helm/charts/<name> or
$PLANE_HOME/etc/helm-private/charts/<name>. plane up knows which is which;
a helm command typed by hand does not, so check the path before assuming.
Datalayer OCI Registry
With access to the Plane repository, you can push the Helm charts to a OCI Registry where you have write access to.
First, login to the Helm Registry.
export DATALAYER_HELM_REGISTRY_HOST=<oci-registry> # Pick the registry of your choice.
export DATALAYER_HELM_REGISTRY=${DATALAYER_HELM_REGISTRY_HOST}/datalayer-charts
helm registry login ${DATALAYER_HELM_REGISTRY_HOST}
Then, build and push the Helm Charts to the Helm Registry.
- Plane
- Shell
plane helm-push
cd $PLANE_HOME/etc/helm
for HELM_CHART in iam jupyter operator
do
echo -----------------------------------------------
echo -e "Packaging Helm Chart [datalayer-$HELM_CHART]"
echo
rm *.tgz || true
helm package datalayer-$HELM_CHART
echo
echo -e "Pushing Helm Chart [datalayer-$HELM_CHART]"
helm push *.tgz oci://$DATALAYER_HELM_REGISTRY
rm *.tgz || true
echo
done