Skip to content
KHoist

Install the controller

Use a cluster you are authorised to change. You need Helm, kubectl, access to the container registry and permission to install the DataProduct CRD and controller RBAC. The chart’s kubeVersion declares its supported Kubernetes versions.

Select and verify a release

Section titled “Select and verify a release”

Choose a published version from GitHub releases. The chart and controller image use the data-product-controller package name.

The commands below contain placeholders. Replace <version> with the chart version and <verified-image-digest> with the complete controller digest verified for that release, including its sha256: prefix.

Terminal window
helm show chart oci://ghcr.io/devantler-tech/charts/data-product-controller \
  --version '<version>'

Use the released artifact verification procedure before selecting an image digest. Controller images and charts have different signing identities; verifying one does not verify the other.

Install without public routing

Section titled “Install without public routing”
Terminal window
helm upgrade --install data-product-controller \
  oci://ghcr.io/devantler-tech/charts/data-product-controller \
  --version '<version>' \
  --namespace data-product-system --create-namespace \
  --set-string image.digest='<verified-image-digest>' \
  --wait --timeout 5m

The registry is available by default. Optional observation and discovery capabilities remain off unless you explicitly enable them. See configuration.

Open the registry locally

Section titled “Open the registry locally”
Terminal window
kubectl --namespace data-product-system port-forward \
  service/data-product-controller 8081:80

Open http://127.0.0.1:8081. A successful port-forward and page response establish that you can reach the registry; they do not establish the health of any product API. Stop the port-forward with Ctrl+C.

Public routing is optional. If you enable route.enabled, configure its Gateway listener, hostname, authentication and access policy through your platform. KHoist’s registry is cluster-wide and is not a tenant-filtered catalogue.

Plan upgrades and removal

Section titled “Plan upgrades and removal”

Read upgrade an installation before changing versions: Helm does not upgrade an existing CRD from a chart’s crds/ directory. Uninstalling the release removes its chart-owned workloads. Helm retains the CRD; deleting that CRD yourself also deletes its stored custom resources.