datahub-ingestion-fips

packaged by Chainguard

Chainguard Container for datahub-ingestion-fips

DataHub metadata ingestion CLI and SDK for extracting, transforming, and loading metadata from data sources into DataHub (FIPS-enabled).

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-ingestion-fips:latest

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

Overview

This image contains the DataHub metadata ingestion CLI and SDK with FIPS-validated cryptography enabled. It is a drop-in replacement for the upstream acryldata/datahub-ingestion image for environments requiring FIPS 140-2/140-3 compliance.

The datahub CLI is the entrypoint. It supports extracting metadata from a wide range of data sources (MySQL, PostgreSQL, Snowflake, BigQuery, Redshift, Kafka, and more) and loading it into a DataHub instance.

All TLS and cryptographic operations use the FIPS-validated OpenSSL provider via openssl-config-fipshardened and py3-cryptography.

Usage

Run a basic ingestion recipe

docker run --rm \
  -v /path/to/recipe.yaml:/recipe.yaml:ro \
  cgr.dev/ORGANIZATION/datahub-ingestion-fips:latest \
  ingest -c /recipe.yaml

Check available plugins

docker run --rm cgr.dev/ORGANIZATION/datahub-ingestion-fips:latest check plugins

Deploy with Helm

This image can be used with the official DataHub Helm chart:

helm repo add datahub https://helm.datahubproject.io
helm install datahub datahub/datahub \
  --set datahub-ingestion-cron.image.repository=cgr.dev/ORGANIZATION/datahub-ingestion-fips \
  --set datahub-ingestion-cron.image.tag=latest

Compatibility Notes

• PyNaCl excluded: The pynacl library (a transitive dependency via paramiko) is excluded from this image because it depends on libsodium, which is not FIPS-validated. SSH-tunneled ingestion sources that rely on paramiko's NaCl-based key exchange will not work. Standard SSH key types (RSA, ECDSA) and non-SSH data sources are unaffected.

Ingestion recipes

A recipe file defines a source (where to read metadata from) and a sink (where to write it). Here is a minimal example that ingests from MySQL and sends metadata to a DataHub instance:

source:
  type: mysql
  config:
    host_port: "mysql-host:3306"
    database: my_database
    username: datahub
    password: datahub

sink:
  type: datahub-rest
  config:
    server: "http://datahub-gms:8080"

For the full recipe format, all available source connectors, and advanced configuration options, see the DataHub Recipe Overview.

Documentation

• DataHub Ingestion Guide
• Source Connector Recipes
• Recipe Overview

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.