datahub-gms

packaged by Chainguard

Chainguard Container for datahub-gms

DataHub GMS (Generalized Metadata Service) stores, indexes, and serves metadata for the DataHub platform.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/datahub-gms:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard datahub-gms image is comparable to the upstream acryldata/datahub-gms image. Application dependencies, including Hazelcast's shaded Jackson libraries, are rebuilt or updated for security fixes.

The upstream acryldata/datahub-gms:latest tag is not kept up to date with current DataHub releases. Chainguard builds from upstream release source rather than that image; our :latest tag tracks the latest DataHub release packaged by Chainguard.

Application and configuration files are root-owned instead of application-owned. Mount custom configuration readable by the runtime user. Auth plugins that write under /etc/datahub/plugins/auth/resources need a writable mount there; /tmp must also be writable for logs and WAR extraction.

The image does not include upstream's /tmp/kafka.client.truststore.jks. For the upstream Kafka TLS configuration, use SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_LOCATION=/etc/ssl/certs/java/cacerts, SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_TYPE=JKS, and SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_PASSWORD=changeit. Mount a custom truststore if your broker uses a private CA.

Prerequisites

Use an existing, initialized DataHub deployment with MySQL (or MariaDB), Kafka, and OpenSearch. Follow the upstream Kubernetes deployment guide for infrastructure and schema initialization. This image contains GMS only, not the frontend, ingestion workers, or upgrade jobs.

The example assumes an initialized Helm release named datahub in namespace datahub, its complete deployment configuration in values.yaml, Helm, and kubectl. Use a Chainguard GMS tag matching your deployment's DataHub release, and retain its schema-upgrade and system-update workflow.

Configure Kubernetes authentication to the Chainguard Registry before upgrading. Retain any required pull secrets and security settings in your deployment's values.yaml; the override below changes only the GMS image.

Getting Started

Add the chart repository and replace the version placeholders with your installed chart version and matching DataHub release (without the v prefix):

helm repo add datahub https://helm.datahubproject.io
helm repo update datahub
CHART_VERSION=x.y.z
DATAHUB_VERSION=x.y.z

Replace ORGANIZATION with your Chainguard organization and confirm the matching GMS tag is available before applying the image override:

cat > gms-values.yaml <<EOF
datahub-gms:
  image:
    registry: cgr.dev
    repository: ORGANIZATION/datahub-gms
    tag: "${DATAHUB_VERSION}"
EOF

helm upgrade datahub datahub/datahub \
  --namespace datahub \
  --version "${CHART_VERSION}" \
  --values values.yaml \
  --values gms-values.yaml \
  --wait --timeout 15m

Confirm GMS is ready and query its health endpoint:

kubectl --namespace datahub rollout status deployment/datahub-datahub-gms --timeout=300s
kubectl --namespace datahub exec deployment/datahub-datahub-gms -- curl -fsS http://localhost:8080/health

If your release overrides component names, changes the base path, or enables GMS HTTPS, use its deployment name and configured health endpoint instead.

Documentation and Resources

• DataHub documentation
• DataHub Helm charts
• GMS application configuration
• DataHub metadata service source and API examples

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.