Skip to content

Update bitnami kafka #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
drewjj merged 3 commits into from
Oct 3, 2025
Merged

Update bitnami kafka #42

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b90ccdb
Update bitnami kafka
drewjj Oct 3, 2025
6db719a
Update release notes to be accurate with PR number
drewjj Oct 3, 2025
7fbc4f8
Add note regarding intention to switch to official kafka image
drewjj Oct 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. 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:

Expand Down
2 changes: 1 addition & 1 deletion docker-compose-kafka.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
1 change: 1 addition & 0 deletions docs/Release_notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 42](https://github.com/CDOT-CV/jpo-utils/pull/40): Update Bitnami Kafka to Bitnami Legacy Kafka

## Version 2.1.3
----------------------------------------
Expand Down
Loading