[bitnami/kafka] Release 3.3.2-debian-12-r29 (#69739)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2024-07-24 07:12:43 +02:00 committed by GitHub
parent 2e57f53650
commit 1374c9c3db
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 5 additions and 9 deletions

View File

@ -8,11 +8,11 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2024-07-06T08:23:17Z" \
org.opencontainers.image.created="2024-07-24T04:24:55Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/kafka/README.md" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="3.3.2-debian-12-r28" \
org.opencontainers.image.ref.name="3.3.2-debian-12-r29" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/kafka" \
org.opencontainers.image.title="kafka" \
org.opencontainers.image.vendor="Broadcom, Inc." \
@ -31,7 +31,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \
"wait-for-port-1.0.8-2-linux-${OS_ARCH}-debian-12" \
"render-template-1.0.7-2-linux-${OS_ARCH}-debian-12" \
"java-17.0.11-12-0-linux-${OS_ARCH}-debian-12" \
"java-17.0.12-10-0-linux-${OS_ARCH}-debian-12" \
"kafka-3.3.2-5-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \

View File

@ -3,7 +3,7 @@
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "17.0.11-12-0"
"version": "17.0.12-10-0"
},
"kafka": {
"arch": "amd64",

View File

@ -422,10 +422,6 @@ kafka_validate() {
fi
# Check KRaft mode
if ! is_empty_value "${KAFKA_CFG_PROCESS_ROLES:-}"; then
# Raft
if [[ "$(kafka_get_version)" =~ ^3\.2\. ]]; then
warn "KRaft mode is not production-ready in Kafka 3.2, for production environments, we recommend upgrading "
fi
# Only allow Zookeeper configuration if migration mode is enabled
if ! is_empty_value "${KAFKA_CFG_ZOOKEEPER_CONNECT:-}" &&
{ is_empty_value "${KAFKA_CFG_ZOOKEEPER_METADATA_MIGRATION_ENABLE:-}" || ! is_boolean_yes "$KAFKA_CFG_ZOOKEEPER_METADATA_MIGRATION_ENABLE"; }; then
@ -843,7 +839,7 @@ kafka_kraft_storage_initialize() {
KAFKA_KRAFT_CLUSTER_ID="$("${KAFKA_HOME}/bin/kafka-storage.sh" random-uuid)"
info "Generated Kafka cluster ID '${KAFKA_KRAFT_CLUSTER_ID}'"
fi
args+=("--cluster-id" "$KAFKA_KRAFT_CLUSTER_ID")
args+=("--cluster-id=$KAFKA_KRAFT_CLUSTER_ID")
# SCRAM users are configured during the cluster bootstrapping process and can later be manually updated using kafka-config.sh
if is_boolean_yes "${KAFKA_KRAFT_BOOTSTRAP_SCRAM_USERS:-}"; then