knative-kafka-broker-dispatcher-loom-fips

packaged by Chainguard

Chainguard Container for knative-kafka-broker-dispatcher-loom-fips

Knative Kafka Broker is a native Apache Kafka implementation of the Knative Broker API, providing high-performance event routing for Knative Eventing with Kafka as the event transport layer.

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/knative-kafka-broker-dispatcher-loom-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 Knative Kafka Broker FIPS images are compatible with the upstream Knative Kafka Broker images. The Chainguard images contain only the minimum set of tools and dependencies needed to function.

Knative Kafka Broker FIPS is comprised of multiple images:

• cgr.dev/ORGANIZATION/knative-kafka-broker-controller-fips
• cgr.dev/ORGANIZATION/knative-kafka-broker-receiver-loom-fips
• cgr.dev/ORGANIZATION/knative-kafka-broker-dispatcher-loom-fips

FIPS Support

The controller image ships with OpenSSL's validated FIPS provider module. The receiver-loom and dispatcher-loom images use BouncyCastle FIPS (BCFIPS) for all cryptographic operations, including TLS. For more on FIPS support in Chainguard Images, consult the FIPS-enabled Chainguard Images guide on Chainguard Academy.

FIPS Runtime Configuration

The receiver-loom and dispatcher-loom images require a BCFKS-format truststore at runtime. BCFIPS's TrustManagerFactory cannot load JKS or PKCS12 stores and throws KeyStoreException if the standard JVM cacerts are used unchanged.

Both components need the following wired into their Kubernetes manifests:

1. A Kubernetes Secret containing a BCFKS truststore (generate with keytool -storetype BCFKS -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider).
2. A volume mount exposing the secret into the container.
3. JAVA_TOOL_OPTIONS configured to point at the truststore:

--module-path=/usr/share/java/bouncycastle-fips
-Djavax.net.ssl.trustStore=<mount-path>/truststore.bcfks
-Djavax.net.ssl.trustStoreType=BCFKS
-Djavax.net.ssl.trustStorePassword=<password>
-Djavax.net.ssl.trustStoreProvider=BCFIPS

Note: The images already set --module-path=/usr/share/java/bouncycastle-fips as the default JAVA_TOOL_OPTIONS. If you override this value via a kustomize patch or pod spec, you must include --module-path in your override — a strategic merge patch replaces the entire env var value, so omitting it removes the module path and BCFIPS will fail to initialize.

Getting Started

Knative Kafka Broker FIPS requires a running Kafka cluster and Knative Eventing core. Use kustomize to deploy the upstream manifests with Chainguard's FIPS images substituted in.

Prerequisites

• A Kubernetes cluster with Knative Eventing installed
• A running Apache Kafka cluster accessible from within the cluster
• kubectl with kustomize

Deployment

Create a kustomization.yaml that replaces the upstream images with Chainguard's FIPS images:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
  - https://github.com/knative-extensions/eventing-kafka-broker/releases/download/knative-v<VERSION>/eventing-kafka-controller.yaml
  - https://github.com/knative-extensions/eventing-kafka-broker/releases/download/knative-v<VERSION>/eventing-kafka-broker.yaml

images:
  - name: gcr.io/knative-releases/knative.dev/eventing-kafka-broker/control-plane/cmd/kafka-controller
    newName: cgr.dev/ORGANIZATION/knative-kafka-broker-controller-fips
    newTag: latest
  - name: gcr.io/knative-releases/knative-kafka-broker-receiver-loom
    newName: cgr.dev/ORGANIZATION/knative-kafka-broker-receiver-loom-fips
    newTag: latest
  - name: gcr.io/knative-releases/knative-kafka-broker-dispatcher-loom
    newName: cgr.dev/ORGANIZATION/knative-kafka-broker-dispatcher-loom-fips
    newTag: latest

Apply the kustomization:

kubectl apply -k <path-to-kustomization>

Create a KafkaBroker

Once deployed, create a KafkaBroker to start routing CloudEvents through Kafka:

apiVersion: eventing.knative.dev/v1
kind: Broker
metadata:
  name: my-broker
  annotations:
    eventing.knative.dev/broker.class: Kafka
spec:
  config:
    apiVersion: v1
    kind: ConfigMap
    name: kafka-broker-config
    namespace: knative-eventing

Documentation and Resources

• Knative Kafka Broker documentation
• Upstream eventing-kafka-broker releases
• Knative Eventing concepts
• FIPS-enabled Chainguard Images

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.