packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
A wolfi-based image tailored for Confluent Kafka, incorporating the required bouncycastle FIPS modules (bcfips) to facilitate operation in FIPS mode.
Both OpenJDK and Confluent Kafka have been configured to harness the BouncyCastle FIPS API at their core. The included bcfips module meets FIPS 140-2 compliance requirements and is accredited under: FIPS certificate 4616.
Configuring Confluent Kafka to operate in FIPS mode is complex. This document attempts to condense the instructions for demonstration purposes, and should not be treated as replacements for official documentation:
This image sets the CLASSPATH environment variable to point towards the bcfips libraries:
If you override the CLASSPATH, you will need to ensure to include this path.
Confluent Kafka supports both KRaft and Zookeeper for operation. Howevever the project is moving away from Zookeeper, and recommends using KRaft. For that reason, as well as to simplify the configuration steps, this document assumes the use of KRaft.
If you opt to use Zookeeper, refer to the upstream documentation for additional steps and instructions required.
Running Confluent Kafka in FIPS mode, requires the use of a FIPS compliant BCKFS keystores. These needs to be created separately to launching the Confluent Kafka container image(s).
The BCKFS keystores needs to be generated on a separate image which do NOT
have BCFIPS JDK running in strict mode - this is due to the keytool
application being hardcoded to pass a new SecureRandom(), which will not
be permitted in strict mode.
Example using a wolfi-base container to generate a bckfs keystore:
After generating the necessary keystores and truststores, launch Confluent Kafka and mount these:
Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at ChainguardThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs