pinot-fips

packaged by Chainguard

Chainguard Container for pinot-fips

A real-time distributed OLAP datastore - (FIPS)

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/pinot-fips: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 pinot-fips container image is comparable to the upstream Apache Pinot distribution, with improved security, few-to-zero CVEs, and FIPS 140-3 compliance.

FIPS Support

The pinot-fips Chainguard Container ships with a validated redistribution of the OpenSSL FIPS provider module. It relies on the BouncyCastle FIPS (BCFIPS) Java security provider for cryptographic operations. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Keystore and Truststore Requirements

The BCFKS (BouncyCastle FIPS Keystore) format is required for keystores and truststores when TLS is enabled. The following formats are rejected:

• JKS — does not use FIPS-approved algorithms
• PKCS12 — certificate parsing requires patches to force RFC9879 KDF and PBMAC algorithms

TLS Requirements

• TLS 1.2 or TLS 1.3 are required. TLS 1.1 and below are rejected.
• Only cipher suites using FIPS 140-3 approved algorithms are permitted.
• Certificates and keys must use FIPS 140-3 compatible algorithms. Non-approved curves (e.g., secp256k1, ed25519), invalid key sizes, and legacy signature algorithms are not supported.

Usage

Running Pinot Components

Pinot consists of several components that can be started individually. When using pinot-fips, the BCFIPS provider is automatically configured via JAVA_TOOL_OPTIONS.

Controller:

docker run --rm -p 9000:9000 \
  cgr.dev/ORGANIZATION/pinot-fips:latest \
  StartController -zkAddress localhost:2181

Broker:

docker run --rm -p 8099:8099 \
  cgr.dev/ORGANIZATION/pinot-fips:latest \
  StartBroker -zkAddress localhost:2181

Server:

docker run --rm -p 8098:8098 \
  cgr.dev/ORGANIZATION/pinot-fips:latest \
  StartServer -zkAddress localhost:2181

BCFKS Keystore Configuration

Generate BCFKS keystores and convert system CA certificates using keytool, which is included in the image:

mkdir -p certs

docker run --rm -v $(pwd)/certs:/certs --entrypoint sh \
  cgr.dev/ORGANIZATION/pinot-fips:latest -c '
    # Generate server keystore
    keytool -genkeypair -alias pinot -keyalg RSA -keysize 2048 -validity 365 \
      -dname "CN=localhost" \
      -keystore /certs/keystore.bcfks -storetype BCFKS \
      -storepass changeit -keypass changeit \
      -providername BCFIPS

    # Export server certificate
    keytool -exportcert -alias pinot \
      -keystore /certs/keystore.bcfks -storetype BCFKS \
      -storepass changeit -providername BCFIPS \
      -rfc -file /certs/server.crt

    # Create truststore
    keytool -importcert -alias pinot -file /certs/server.crt -noprompt \
      -keystore /certs/truststore.bcfks -storetype BCFKS \
      -storepass changeit -providername BCFIPS

    # Convert system CA certificates from JKS to BCFKS format
    keytool -importkeystore \
      -srckeystore $JAVA_HOME/lib/security/cacerts -srcstoretype JKS -srcstorepass changeit \
      -destkeystore /certs/cacerts.bcfks -deststoretype BCFKS -deststorepass changeit \
      -providername BCFIPS -noprompt
  '

Deploying with Kubernetes

Use the official Apache Pinot Helm chart with the FIPS image:

helm repo add pinot https://raw.githubusercontent.com/apache/pinot/master/helm
helm install pinot pinot/pinot \
  --set image.repository=cgr.dev/ORGANIZATION/pinot-fips \
  --set image.tag=latest

Documentation and Resources

• Apache Pinot Official Documentation
• Apache Pinot GitHub Repository
• Pinot Getting Started Guide
• BouncyCastle FIPS Documentation

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.