What would you like to share?
Hi,
I noticed that the .env file defines KAFKA_IMAGE=bitnamilegacy/kafka:3.5.1.
The Problem
Using the bitnamilegacy repository is risky. As the name implies, these images are deprecated and no longer receive updates (including security patches). Furthermore, reliance on legacy Bitnami artifacts often leads to stability issues as distribution methods change.
Proposed Solution
I suggest switching to soldevelo/kafka:3.5.1.
This image is a free, actively maintained drop-in replacement that preserves the Bitnami directory structure and environment variable logic. This ensures that OpenIM will continue to function correctly (keeping all volume mounts and init scripts working) without the risks associated with using a legacy image.
Suggested Change in .env:
# Old
KAFKA_IMAGE=bitnamilegacy/kafka:3.5.1
# New
KAFKA_IMAGE=soldevelo/kafka:3.5.1
I can submit a Pull Request to update this variable. Would you be open to that?
Additional information
No response
What would you like to share?
Hi,
I noticed that the
.envfile definesKAFKA_IMAGE=bitnamilegacy/kafka:3.5.1.The Problem
Using the
bitnamilegacyrepository is risky. As the name implies, these images are deprecated and no longer receive updates (including security patches). Furthermore, reliance on legacy Bitnami artifacts often leads to stability issues as distribution methods change.Proposed Solution
I suggest switching to
soldevelo/kafka:3.5.1.This image is a free, actively maintained drop-in replacement that preserves the Bitnami directory structure and environment variable logic. This ensures that OpenIM will continue to function correctly (keeping all volume mounts and init scripts working) without the risks associated with using a legacy image.
Suggested Change in
.env:I can submit a Pull Request to update this variable. Would you be open to that?
Additional information
No response