This chart deploys the frontend, backend, data quality tool, and PostgreSQL for DataCatalog.
- Kubernetes cluster
- Helm 3
- A namespace where the release will run
For local MicroK8s usage:
sudo snap install microk8s --classic
microk8s enable dns ingress helm3 storageThe chart now takes its namespace from the Helm release, not from values.yaml.
Update values.yaml or provide overrides for:
cluster.managed:falsefor microk8s/local storage,truefor managed-cluster storage classesimages.repositoryandimages.tag: image location and release tagglobal.publicHost: bare public hostname used by the frontend ingress and backend auth callback URLdatacatalogDb.image: PostgreSQL image, currentlypostgres:18.3backend.authentication: enable or disable Keycloak-backed authentication in the backendcluster.storageClasses.managedif your managed cluster uses a different default storage classfrontend.ingress.tlsSecretName: override the default TLS secret name
The chart expects a secret named datacatalog-secrets with:
db.userdb.passwordkeycloak.client-idkeycloak.client-secret
Example:
kubectl -n default create secret generic datacatalog-secrets \
--from-literal=db.user=postgres \
--from-literal=db.password=test \
--from-literal=keycloak.client-id=datacatalog \
--from-literal=keycloak.client-secret=change-meFrom the kubernetes/ directory:
helm upgrade --install datacatalog . -n default --create-namespaceWith MicroK8s:
microk8s helm3 upgrade --install datacatalog . -n default --create-namespace- The frontend is exposed through ingress when
global.publicHostis set. - Frontend and backend services are internal
ClusterIPservices in both managed and microk8s deployments. cluster.managedonly controls storage-class selection and whether the microk8s localStorageClassis rendered.
The database uses a PVC and mounts storage at /var/lib/postgresql.