Chainguard Container for kafka

Minimal image for Apache Kafka, a distributed event streaming 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/kafka: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 Kafka image is comparable to the apache/kafka image on Dockerhub, and is also compatible with the Bitnami Kafka helm chart.

Like most other Chainguard Images, the Kafka image has few-to-zero CVEs and does not run as the root user.

Getting Started

Create a values.yaml, specifying the Chainguard image:

# Save as values.yaml
contour:
  image:
    registry: "cgr.dev"
    repository: "ORGANIZATION/kafka"
    tag: "latest"
global:
  security:
    allowInsecureImages: true

Deploy using helm:

helm install etcd oci://registry-1.docker.io/bitnamicharts/kafka -f values.yaml

Chainguard Kafka images include the server scripts which can be used to start up or configure Kafka or its dependencies. You can find the full list of available scripts in the container's /usr/lib/kafka/bin/ directory:

% docker run -it --entrypoint=sh cgr.dev/ORGANIZATION/kafka
/ #
/ # ls /usr/lib/kafka/bin/
connect-distributed.sh          	kafka-console-consumer.sh       	kafka-get-offsets.sh            	kafka-replica-verification.sh   	kafka-verifiable-producer.sh
connect-mirror-maker.sh         	kafka-console-producer.sh       	kafka-jmx.sh                    	kafka-run-class.sh              	trogdor.sh
connect-plugin-path.sh          	kafka-consumer-groups.sh        	kafka-leader-election.sh        	kafka-server-start.sh           	windows
connect-standalone.sh           	kafka-consumer-perf-test.sh     	kafka-log-dirs.sh               	kafka-server-stop.sh            	zookeeper-security-migration.sh
kafka-acls.sh                   	kafka-delegation-tokens.sh      	kafka-metadata-quorum.sh        	kafka-storage.sh                	zookeeper-server-start.sh
kafka-broker-api-versions.sh    	kafka-delete-records.sh         	kafka-metadata-shell.sh         	kafka-streams-application-reset.sh  zookeeper-server-stop.sh
kafka-client-metrics.sh         	kafka-dump-log.sh               	kafka-mirror-maker.sh           	kafka-topics.sh                 	zookeeper-shell.sh
kafka-cluster.sh                	kafka-e2e-latency.sh            	kafka-producer-perf-test.sh     	kafka-transactions.sh
kafka-configs.sh                	kafka-features.sh               	kafka-reassign-partitions.sh    	kafka-verifiable-consumer.sh

Chainguard uses the following Helm values to test the Kafka image:

• fsGroup: part of a podSecurityContext object, the fsGroup field specifies the group ID under which all processes of the pod are part of.
• runAsUser: part of a containerSecurityContext object, this value specifies the user ID under which all processes in the container run under.
• mountPath: part of a logPersistence object, this defines the location where a log volume will be mounted.

Logs

You can retrieve the logs for the Kafka container with the docker logs command. The following example assumes that you're running a Kafka container named kafka-container:

docker logs kafka-container

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.