From b90ccdbe76dd6ad573ee325d248d61fec7b040bf Mon Sep 17 00:00:00 2001 From: Drew Johnston Date: Fri, 3 Oct 2025 09:05:55 -0600 Subject: [PATCH 1/3] Update bitnami kafka --- README.md | 2 +- docker-compose-kafka.yml | 2 +- docs/Release_notes.md | 1 + 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 19df946..04a6483 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ Where the `COMPOSE_PROFILES` variable in you're `.env` file are as follows: ## 3. Kafka -The [Bitnami Kafka](https://hub.docker.com/r/bitnami/kafka) is being used as a hybrid controller and broker in the [docker-compose-kafka](docker-compose-kafka.yml) file. To use a different `kafka_init.sh` script, pass in the relative path of the new script by overriding the `KAFKA_INIT_SCRIPT_RELATIVE_PATH` environmental variable. This can help in initializing new topics at startup. +The [Bitnami Legacy Kafka](https://hub.docker.com/r/bitnamilegacy/kafka) is being used as a hybrid controller and broker in the [docker-compose-kafka](docker-compose-kafka.yml) file. To use a different `kafka_init.sh` script, pass in the relative path of the new script by overriding the `KAFKA_INIT_SCRIPT_RELATIVE_PATH` environmental variable. This can help in initializing new topics at startup. An optional `kafka-init`, `schema-registry`, and `kafka-ui` instance can be deployed by configuring the `COMPOSE_PROFILES` as follows: diff --git a/docker-compose-kafka.yml b/docker-compose-kafka.yml index 986f968..4427092 100644 --- a/docker-compose-kafka.yml +++ b/docker-compose-kafka.yml @@ -5,7 +5,7 @@ services: - kafka_connect_standalone - kafka_full - kafka - image: bitnami/kafka:3.8.0 + image: bitnamilegacy/kafka:3.8.0 hostname: kafka restart: ${RESTART_POLICY:-on-failure:3} healthcheck: diff --git a/docs/Release_notes.md b/docs/Release_notes.md index cceca60..4e1774f 100644 --- a/docs/Release_notes.md +++ b/docs/Release_notes.md @@ -16,6 +16,7 @@ Enhancements in this release: - [CDOT PR 35](https://github.com/CDOT-CV/jpo-utils/pull/35): RTCM Topics - [CDOT PR 36](https://github.com/CDOT-CV/jpo-utils/pull/36): Remove raw encoded collections and connectors - [CDOT PR 37](https://github.com/CDOT-CV/jpo-utils/pull/37): Adding OdeBsmJson index and additionalIndexes generator +- [CDOT PR 40](https://github.com/CDOT-CV/jpo-utils/pull/40): Update Bitnami Kafka to Bitnami Legacy Kafka ## Version 2.1.3 ---------------------------------------- From 6db719a998e8d90b947f28772637b9fe8b2cc1c2 Mon Sep 17 00:00:00 2001 From: Drew Johnston Date: Fri, 3 Oct 2025 09:07:20 -0600 Subject: [PATCH 2/3] Update release notes to be accurate with PR number --- docs/Release_notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Release_notes.md b/docs/Release_notes.md index 4e1774f..f46c393 100644 --- a/docs/Release_notes.md +++ b/docs/Release_notes.md @@ -16,7 +16,7 @@ Enhancements in this release: - [CDOT PR 35](https://github.com/CDOT-CV/jpo-utils/pull/35): RTCM Topics - [CDOT PR 36](https://github.com/CDOT-CV/jpo-utils/pull/36): Remove raw encoded collections and connectors - [CDOT PR 37](https://github.com/CDOT-CV/jpo-utils/pull/37): Adding OdeBsmJson index and additionalIndexes generator -- [CDOT PR 40](https://github.com/CDOT-CV/jpo-utils/pull/40): Update Bitnami Kafka to Bitnami Legacy Kafka +- [CDOT PR 42](https://github.com/CDOT-CV/jpo-utils/pull/40): Update Bitnami Kafka to Bitnami Legacy Kafka ## Version 2.1.3 ---------------------------------------- From 7fbc4f811f32441ac685779a7cc4289abee8c727 Mon Sep 17 00:00:00 2001 From: Drew Johnston Date: Fri, 3 Oct 2025 10:38:04 -0600 Subject: [PATCH 3/3] Add note regarding intention to switch to official kafka image --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 04a6483..b291f63 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ Where the `COMPOSE_PROFILES` variable in you're `.env` file are as follows: ## 3. Kafka -The [Bitnami Legacy Kafka](https://hub.docker.com/r/bitnamilegacy/kafka) is being used as a hybrid controller and broker in the [docker-compose-kafka](docker-compose-kafka.yml) file. To use a different `kafka_init.sh` script, pass in the relative path of the new script by overriding the `KAFKA_INIT_SCRIPT_RELATIVE_PATH` environmental variable. This can help in initializing new topics at startup. +The [Bitnami Legacy Kafka](https://hub.docker.com/r/bitnamilegacy/kafka) is being used as a hybrid controller and broker in the [docker-compose-kafka](docker-compose-kafka.yml) file. To use a different `kafka_init.sh` script, pass in the relative path of the new script by overriding the `KAFKA_INIT_SCRIPT_RELATIVE_PATH` environmental variable. This can help in initializing new topics at startup. Note: the intention for the future is to switch this to use the official Apache Kafka image since Bitnami is no longer a reliable image provider. An optional `kafka-init`, `schema-registry`, and `kafka-ui` instance can be deployed by configuring the `COMPOSE_PROFILES` as follows: