Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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 client-registry-jempi/package-metadata.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
],
"environmentVariables": {
"KAFKA_HOSTS": "kafka-01:9092",
"JEMPI_POSTGRESQL_IMAGE": "bitnami/postgresql-repmgr:15.2.0",
"JEMPI_POSTGRESQL_IMAGE": "bitnamilegacy/postgresql-repmgr:15.2.0",
"JEMPI_ZERO_IMAGE": "dgraph/dgraph:v23.1.1",
"JEMPI_RATEL_IMAGE": "dgraph/ratel:v21.03.2",
"JEMPI_ZERO_MEMORY_LIMIT": "3G",
Expand Down
2 changes: 1 addition & 1 deletion client-registry-santempi/package-metadata.json
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
"SANTEMPI_REPMGR_PARTNER_NODES": "santempi-psql-1",
"SANTEMPI_IMAGE": "santesuite/santedb-mpi:2.2.3",
"SANTEDB_WWW_IMAGE": "santesuite/santedb-www:2.2.1.10",
"SANTEMPI_PSQL_IMAGE": "bitnami/postgresql-repmgr:14",
"SANTEMPI_PSQL_IMAGE": "bitnamilegacy/postgresql-repmgr:14",
"PSQL_1_PLACEMENT": "node-1",
"PSQL_2_PLACEMENT": "node-2",
"PSQL_3_PLACEMENT": "node-3",
Expand Down
4 changes: 2 additions & 2 deletions database-postgres/package-metadata.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,11 @@
"REPMGR_PRIMARY_HOST": "postgres-1",
"REPMGR_PARTNER_NODES": "postgres-1",
"REPMGR_PASSWORD": "instant101",
"POSTGRES_IMAGE": "bitnami/postgresql-repmgr:14@sha256:bdf1e4903710c4e0b465664b886d4556897e1b18c07d7c513a4fc1ceba929e02",
"POSTGRES_IMAGE": "bitnamilegacy/postgresql-repmgr:14@sha256:bdf1e4903710c4e0b465664b886d4556897e1b18c07d7c513a4fc1ceba929e02",
"POSTGRES_1_PLACEMENT": "node-1",
"POSTGRES_2_PLACEMENT": "node-2",
"POSTGRES_3_PLACEMENT": "node-3",
"PG_POOL_IMAGE": "bitnami/pgpool:4.4.3",
"PG_POOL_IMAGE": "bitnamilegacy/pgpool:4.4.3",
"PGPOOL_1_PLACEMENT": "node-1",
"PGPOOL_2_PLACEMENT": "node-2",
"PGPOOL_3_PLACEMENT": "node-3",
Expand Down
2 changes: 1 addition & 1 deletion identity-access-manager-keycloak/package-metadata.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"version": "0.0.1",
"dependencies": ["database-postgres"],
"environmentVariables": {
"POSTGRES_IMAGE": "bitnami/postgresql-repmgr:14",
"POSTGRES_IMAGE": "bitnamilegacy/postgresql-repmgr:14",
"KEYCLOAK_POSTGRES_1": "node-1",
"KEYCLOAK_POSTGRES_2": "node-2",
"KEYCLOAK_POSTGRES_3": "node-3",
Expand Down
2 changes: 1 addition & 1 deletion message-bus-kafka/package-metadata.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"type": "infrastructure",
"dependencies": [],
"environmentVariables": {
"KAFKA_IMAGE": "bitnami/kafka:3.4.0",
"KAFKA_IMAGE": "bitnamilegacy/kafka:3.4.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

bitnamilegacy kafka Docker Hub image maintenance

💡 Result:

bitnamilegacy/kafka on Docker Hub is not maintained: it’s a legacy backup of older Bitnami Kafka images that will receive no further updates or support and is intended only for temporary migration; it may also be removed in the future, so you should mirror any tags you still depend on into your own registry. [1]

For ongoing maintenance/security updates, Bitnami directs users to move to Bitnami Secure Images, e.g. bitnami/kafka. [1][2]


🌐 Web query:

bitnamilegacy Docker repository security updates

💡 Result:

docker.io/bitnamilegacy/* images do not receive security updates.

  • Bitnami’s own announcement for the 2025 catalog change says the Legacy repository (“docker.io/bitnamilegacy”) contains archived images that “will no longer receive updates, fixes, or support” and is intended only as a temporary fallback during migration. [1]
  • Individual Docker Hub pages for bitnamilegacy/* (example: bitnamilegacy/nginx) explicitly warn: “This repository is no longer updated… will receive no further updates or support” and note it may be removed in the future. [2]

If you need ongoing security patching, Bitnami directs users to Bitnami Secure Images (paid) rather than bitnamilegacy. [1]

Sources: [1] [2]


🌐 Web query:

bitnamilegacy/kafka:3.4.0 Docker image

💡 Result:

  • bitnamilegacy/kafka is Bitnami’s frozen/unsupported “legacy” repo: it receives no further updates/support and may be removed in the future (Bitnami recommends mirroring any tags you still depend on). [1]
  • For Kafka 3.4.0, the Bitnami (non-legacy) image tag exists as bitnami/kafka:3.4.0 (APP_VERSION=3.4.0; Debian 11–based). Pull: docker pull bitnami/kafka:3.4.0. [2]
  • If you were looking for an official ASF Kafka Docker image, note that apache/kafka images are available starting at Kafka 3.7.0 (so there is no apache/kafka:3.4.0). [3]

Sources: [1] Docker Hub: bitnamilegacy/kafka overview (legacy/no longer updated) • [2] Tag details for bitnami/kafka:3.4.0 • [3] Apache Kafka Docker docs (availability from 3.7.0)


Do not use bitnamilegacy/kafka:3.4.0—this image receives no security updates and may be removed without notice.

The bitnamilegacy repository contains frozen, unmaintained images with explicit warnings that they will receive no further updates or support and are intended only as a temporary fallback during migration. Use bitnami/kafka:3.4.0 from the maintained repository instead, or update to a newer supported version. If you must retain this legacy image, mirror it to your own registry as Bitnami explicitly recommends.

🤖 Prompt for AI Agents
In `@message-bus-kafka/package-metadata.json` at line 9, The KAFKA_IMAGE metadata
entry currently points to the unmaintained legacy image
"bitnamilegacy/kafka:3.4.0"; update the value of the KAFKA_IMAGE key to use the
supported Bitnami image (e.g., "bitnami/kafka:3.4.0" or a newer supported tag)
or, if you must keep that exact legacy image, document and replace it with a
mirrored image in your own registry; edit the package-metadata.json KAFKA_IMAGE
entry to one of these supported options and ensure any deployment manifests
referencing KAFKA_IMAGE use the new value.

"KAFDROP_IMAGE": "obsidiandynamics/kafdrop:3.27.0",
"KAFKA_MINION": "quay.io/cloudhut/kminion:master",
"KAFKA_01_PLACEMENT": "node-1",
Expand Down
1 change: 1 addition & 0 deletions monitoring/docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,7 @@ services:
command: -config.file=/etc/loki/loki-config.yml -config.expand-env=true
networks:
minio:
default:
deploy:
labels:
- prometheus-job-service=loki
Expand Down
Loading