[bitnami/kafka] Release 3.3.2-debian-11-r9 (#24256)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 16:23:14 +01:00 committed by GitHub
parent 57660b0ee4
commit 64e64f5cba
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 21 additions and 21 deletions

View File

@ -3,11 +3,11 @@ FROM docker.io/bitnami/minideb:bullseye
ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-17T14:56:02Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="3.3.2-debian-11-r8" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/kafka" \
org.opencontainers.image.ref.name="3.3.2-debian-11-r9" \
org.opencontainers.image.title="kafka" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="3.3.2"
@ -23,11 +23,11 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl procps zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"java-11.0.18-10-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"wait-for-port-1.0.6-0-linux-${OS_ARCH}-debian-11" \
"render-template-1.0.5-0-linux-${OS_ARCH}-debian-11" \
"kafka-3.3.2-0-linux-${OS_ARCH}-debian-11" \
"java-11.0.18-10-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
"wait-for-port-1.0.6-1-linux-${OS_ARCH}-debian-11" \
"render-template-1.0.5-1-linux-${OS_ARCH}-debian-11" \
"kafka-3.3.2-1-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

View File

@ -1,37 +1,37 @@
{
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"java": {
"arch": "amd64",
"digest": "f8c3013925073f94edc495584b76f0b08c867ba35c524e2b262e47e815a443b9",
"digest": "cd40a6df619d734d300324ad671f34323152e84682bc998da1330f1a7f0acfa6",
"distro": "debian-11",
"type": "NAMI",
"version": "11.0.18-10-0"
"version": "11.0.18-10-1"
},
"kafka": {
"arch": "amd64",
"digest": "115254ae869b36b9ebeec37e6886f3b5d46fb2e4d2c0bddc2322e18ccf20ad8a",
"digest": "6ee947706fc87625bf0bb50da90e89f047a0e46912f10296ad0fdc35df54b98c",
"distro": "debian-11",
"type": "NAMI",
"version": "3.3.2-0"
"version": "3.3.2-1"
},
"render-template": {
"arch": "amd64",
"digest": "57c1d857acbb187fcb98f4ba26d138af9d866f59ad38dd443a75c0a6422de994",
"digest": "185e277977366ec222d2bde1a395ffa138ce1a9d3bdf1df20c3e49e8b8f9c68b",
"distro": "debian-11",
"type": "NAMI",
"version": "1.0.5-0"
"version": "1.0.5-1"
},
"wait-for-port": {
"arch": "amd64",
"digest": "f9199cd66b92fef328ecfbc5ffbc8f14be33257a4e34b8c6ba35a730c5a2f59d",
"digest": "be7c393d598ddf16d1c3c008a67b87879e48aca62071a208583390f2b41e6744",
"distro": "debian-11",
"type": "NAMI",
"version": "1.0.6-0"
"version": "1.0.6-1"
}
}

View File

@ -142,7 +142,7 @@ docker run -it --rm \
bitnami/kafka:latest kafka-topics.sh --list --bootstrap-server kafka-server:9092
```
### Using Docker Compose
### Using a Docker Compose file
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the Apache Kafka server from your own custom application image which is identified in the following snippet by the service name `myapp`.
@ -389,7 +389,7 @@ Keep in mind the following notes:
* When prompted to enter a password, use the same one for all.
* Set the Common Name or FQDN values to your Apache Kafka container hostname, e.g. `kafka.example.com`. After entering this value, when prompted "What is your first and last name?", enter this value as well.
* As an alternative, you can disable host name verification setting the environment variable `KAFKA_CFG_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM` to an empty string.
* When setting up a Apache Kafka Cluster (check [this section](#setting-up-an-apache-kafka-cluster) for more information), each Apache Kafka broker and logical client needs its own keystore. You will have to repeat the process for each of the brokers in the cluster.
* When setting up a Apache Kafka Cluster (check the "Setting up an Apache Kafka Cluster") for more information), each Apache Kafka broker and logical client needs its own keystore. You will have to repeat the process for each of the brokers in the cluster.
The following docker-compose file is an example showing how to mount your JKS certificates protected by the password `certificatePassword123`. Additionally it is specifying the Apache Kafka container hostname and the credentials for the client and zookeeper users.