fix: use bitnamilegacy images temporarily - #41176
Conversation
WalkthroughUpdated Helm chart version to 3.6.4 and repointed MongoDB/PostgreSQL images to bitnamilegacy repositories in values.yaml, removing the redundant mongodb.image block. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Poem
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
deploy/helm/tests/__snapshot__/defaults_snapshot_test.yaml.snapis excluded by!**/*.snap
📒 Files selected for processing (2)
deploy/helm/Chart.yaml(1 hunks)deploy/helm/values.yaml(2 hunks)
🔇 Additional comments (1)
deploy/helm/Chart.yaml (1)
14-14: Patch version bump looks correct for values-only changesNo concerns from me on this bump. Please ensure a brief CHANGELOG/Release note mentions the temporary switch to bitnamilegacy images.
| image: | ||
| registry: docker.io | ||
| repository: bitnami/mongodb | ||
| repository: bitnamilegacy/mongodb | ||
| tag: 6.0.13 | ||
| arbiter: |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
MongoDB: repository switched to bitnamilegacy — verify image/tag availability
Change aligns with the PR goal. Recommend verifying the tag exists in Docker Hub and that there are no remaining bitnami/mongodb references elsewhere.
Run these checks:
Optional hardening: consider pinning by digest to prevent unexpected base image changes:
- Example tag-to-digest: docker pull and record sha256, then use tag@sha256:.
If you keep the commented initContainer examples, consider updating those to bitnamilegacy to avoid confusion in future edits.
---
🏁 Script executed:
```shell
#!/usr/bin/env bash
set -euo pipefail
# 1) Ensure no lingering bitnami image references remain in values
rg -n 'bitnami/(mongodb|postgresql)' deploy/helm/values.yaml || true
# 2) Verify docker.io/bitnamilegacy/mongodb:6.0.13 exists (anonymous token + manifest check)
get_token() {
repo="$1"
curl -s "https://auth.docker.io/token?service=registry.docker.io&scope=repository:${repo}:pull" | jq -r .token
}
check_manifest() {
repo="$1"
tag="$2"
token="$(get_token "$repo")"
curl -fsSL -H "Authorization: Bearer ${token}" -H "Accept: application/vnd.docker.distribution.manifest.v2+json" \
"https://registry-1.docker.io/v2/${repo}/manifests/${tag}" >/dev/null && echo "OK: ${repo}:${tag}" || echo "MISSING: ${repo}:${tag}"
}
check_manifest "bitnamilegacy/mongodb" "6.0.13"
Length of output: 6093
MongoDB image tag verified; update commented examples
- ✔️ docker.io/bitnamilegacy/mongodb:6.0.13 manifest exists on Docker Hub
⚠️ Commented initContainer examples still reference bitnami images (deploy/helm/values.yaml lines 122 & 124)
• Update those to use bitnamilegacy (or remove) to avoid confusion- No other
bitnami/(mongodb|postgresql)references found
Optional: pin the image with a sha256 digest to guard against unexpected upstream updates.
🤖 Prompt for AI Agents
In deploy/helm/values.yaml around lines 35-39 (and refer to the commented
examples at lines ~122 and ~124), the main image is correctly set to
docker.io/bitnamilegacy/mongodb:6.0.13 but the commented initContainer examples
still reference bitnami images; update those commented example lines to use
bitnamilegacy/mongodb (or remove the outdated comments) so the docs/examples
match the configured image, and optionally replace the tag with a pinned sha256
digest to prevent unexpected upstream changes.
| image: | ||
| registry: docker.io | ||
| repository: bitnami/postgresql | ||
| repository: bitnamilegacy/postgresql | ||
| tag: 14.12.0 | ||
| primary: |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
PostgreSQL: repository switched to bitnamilegacy — verify image/tag availability
Looks good and consistent with MongoDB. Suggest verifying tag presence and ensuring no stray bitnami/postgresql refs.
Run:
Optional: pin by digest for reproducibility as above.
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
# Search for stray bitnami/postgresql references
rg -n 'bitnami/postgresql' deploy/helm/values.yaml || true
# Verify docker.io/bitnamilegacy/postgresql:14.12.0 exists
get_token() {
repo="$1"
curl -s "https://auth.docker.io/token?service=registry.docker.io&scope=repository:${repo}:pull" | jq -r .token
}
token="$(get_token 'bitnamilegacy/postgresql')"
curl -fsSL -H "Authorization: Bearer ${token}" -H "Accept: application/vnd.docker.distribution.manifest.v2+json" \
"https://registry-1.docker.io/v2/bitnamilegacy/postgresql/manifests/14.12.0" >/dev/null && echo "OK" || echo "MISSING"Length of output: 5888
PostgreSQL image/tag validated; remove stray reference
- Verified that docker.io/bitnamilegacy/postgresql:14.12.0 exists in the Docker registry.
- deploy/helm/values.yaml, line 124: there’s still a commented-out reference to
docker.io/bitnami/postgresql:14.5.0-debian-11-r21—please remove or update it to avoid confusion.
Optional: pin the image by digest for reproducibility.
🤖 Prompt for AI Agents
In deploy/helm/values.yaml around lines 56-60 and remove the stray commented
reference at line 124, the file currently references
docker.io/bitnamilegacy/postgresql:14.12.0 but also contains a commented-out
docker.io/bitnami/postgresql:14.5.0-debian-11-r21; delete or update that
commented line to match the validated image, or replace both with a
digest-pinned reference (e.g., repository@sha256:...) if you want reproducible
pinning.
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
deploy/helm/Chart.yaml (1)
14-14: Version bump acknowledged; add release notes entry for traceability.Please update CHANGELOG/release notes to mention the temporary switch to bitnamilegacy images so operators understand the rationale and rollback plan.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
deploy/helm/tests/__snapshot__/defaults_snapshot_test.yaml.snapis excluded by!**/*.snap
📒 Files selected for processing (2)
deploy/helm/Chart.yaml(1 hunks)deploy/helm/values.yaml(2 hunks)
| image: | ||
| registry: docker.io | ||
| repository: bitnami/mongodb | ||
| repository: bitnamilegacy/mongodb |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Temporary switch to bitnamilegacy/mongodb looks fine; add a TODO and verify tag availability.
Add a short TODO with the upstream issue link and planned reversion criteria. Also verify the tag exists on Docker Hub to avoid pull-time surprises.
Proposed inline comment:
image:
registry: docker.io
- repository: bitnamilegacy/mongodb
+ # TODO(appsmith#35256): Temporary switch due to Bitnami image deprecation. Revert to bitnami/mongodb once upstream is resolved and MongoDB is upgraded.
+ repository: bitnamilegacy/mongodb
tag: 6.0.13Script to verify the tag exists:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Checking bitnamilegacy/mongodb:6.0.13..."
curl -fsSL 'https://hub.docker.com/v2/repositories/bitnamilegacy/mongodb/tags?page_size=1&name=6.0.13' | jq '.count, .results[].name'
echo "Expected: count >= 1 and name == 6.0.13"Length of output: 360
Adjust MongoDB image tag to an existing tag and add TODO
The 6.0.13 tag isn’t available on Docker Hub—only 6.0.13-debian-11-r9 exists—so we need to update the tag in values.yaml and include the TODO for reverting upstream.
Locations to update:
- deploy/helm/values.yaml: around line 37
Proposed diff:
image:
registry: docker.io
- # TODO(appsmith#35256): Temporary switch due to Bitnami image deprecation. Revert to bitnami/mongodb once upstream is resolved and MongoDB is upgraded.
- repository: bitnamilegacy/mongodb
- tag: 6.0.13
+ # TODO(appsmith#35256): Temporary switch due to Bitnami image deprecation. Revert to bitnami/mongodb once upstream is resolved and MongoDB is upgraded.
+ repository: bitnamilegacy/mongodb
+ tag: 6.0.13-debian-11-r9Updated verification script:
#!/bin/bash
set -euo pipefail
echo "Verifying bitnamilegacy/mongodb:6.0.13-debian-11-r9..."
curl -fsSL 'https://hub.docker.com/v2/repositories/bitnamilegacy/mongodb/tags?page_size=1&name=6.0.13-debian-11-r9' \
| jq '.count, .results[].name'
# Expect: count >= 1 and name == "6.0.13-debian-11-r9"🤖 Prompt for AI Agents
deploy/helm/values.yaml around line 37: the image tag currently references a
non-existent tag (6.0.13); change it to the existing tag "6.0.13-debian-11-r9"
in values.yaml and add a single-line TODO comment noting to revert to the
upstream "6.0.13" tag if/when it becomes available; ensure the repository/name
remains "bitnamilegacy/mongodb" and keep the TODO concise and searchable (e.g.,
TODO: revert image tag when upstream publishes 6.0.13).
There was a problem hiding this comment.
🤔 this worked on a test deploy. I'll have to double-check it.
There was a problem hiding this comment.
docker pull bitnamilegacy/mongodb:6.0.13
6.0.13: Pulling from bitnamilegacy/mongodb
45f335159959: Download complete
Digest: sha256:98fca2a5dc569ec1588a0819c1778bf453b39ded1d8e9c42c15104a3e0f44d4a
Status: Downloaded newer image for bitnamilegacy/mongodb:6.0.13
docker.io/bitnamilegacy/mongodb:6.0.13
There was a problem hiding this comment.
@wyattwalter Thanks for verifying that! You're absolutely right - the 6.0.13 tag does exist and work for bitnamilegacy/mongodb. My earlier API check was incorrect.
Since the current configuration works as-is, no tag change is needed. However, I'd still recommend adding a brief TODO comment to document that this is a temporary switch:
image:
registry: docker.io
# TODO: Temporary switch due to Bitnami image deprecation (ref: bitnami/charts#35256)
repository: bitnamilegacy/mongodb
tag: 6.0.13This will help future maintainers understand the context and know to revert once the upstream issue is resolved.
There was a problem hiding this comment.
@wyattwalter Thanks for verifying that! You're absolutely right - the 6.0.13 tag does exist and work for bitnamilegacy/mongodb. My earlier API check was incorrect.
Since the current configuration works as-is, no tag change is needed. However, I'd still recommend adding a brief TODO comment to document that this is a temporary switch:
image:
registry: docker.io
# TODO: Temporary switch due to Bitnami image deprecation (ref: bitnami/charts#35256)
repository: bitnamilegacy/mongodb
tag: 6.0.13This will help future maintainers understand the context and know to revert once the upstream issue is resolved.
✏️ Learnings added
Learnt from: wyattwalter
PR: appsmithorg/appsmith#41176
File: deploy/helm/values.yaml:37-37
Timestamp: 2025-08-12T14:17:36.367Z
Learning: The bitnamilegacy/mongodb:6.0.13 Docker image tag exists and is functional, despite Docker Hub API queries suggesting otherwise. Direct docker pull commands are more reliable than API metadata for verifying image availability.
Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.
| image: | ||
| registry: docker.io | ||
| repository: bitnami/postgresql | ||
| repository: bitnamilegacy/postgresql |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
PostgreSQL image moved to bitnamilegacy; mirror the same TODO and validate the tag.
Document the temporary nature and check the tag’s availability to prevent deployment failures.
Proposed inline comment:
image:
registry: docker.io
- repository: bitnamilegacy/postgresql
+ # TODO(appsmith#35256): Temporary switch due to Bitnami image deprecation. Revert to bitnami/postgresql after upstream resolution/upgrade.
+ repository: bitnamilegacy/postgresql
tag: 14.12.0Script to verify the tag exists:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Checking bitnamilegacy/postgresql:14.12.0..."
curl -fsSL 'https://hub.docker.com/v2/repositories/bitnamilegacy/postgresql/tags?page_size=1&name=14.12.0' | jq '.count, .results[].name'
echo "Expected: count >= 1 and name == 14.12.0"Length of output: 375
Fix image tag and add TODO
The tag 14.12.0 isn’t published under bitnamilegacy/postgresql (only 14.12.0-debian-12-r9 is available). Update the tag and document this as a temporary workaround.
File: deploy/helm/values.yaml (line ~58)
image:
registry: docker.io
- repository: bitnamilegacy/postgresql
- tag: 14.12.0
+ # TODO(appsmith#35256): Temporary switch due to Bitnami image deprecation.
+ # Revert to bitnami/postgresql and tag `14.12.0` once upstream is restored.
+ repository: bitnamilegacy/postgresql
+ tag: 14.12.0-debian-12-r9- Confirm availability of the selected tag to avoid deployment failures.
- Remove the TODO and switch back to the official Bitnami image when possible.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| repository: bitnamilegacy/postgresql | |
| image: | |
| registry: docker.io | |
| # TODO(appsmith#35256): Temporary switch due to Bitnami image deprecation. | |
| # Revert to bitnami/postgresql and tag `14.12.0` once upstream is restored. | |
| repository: bitnamilegacy/postgresql | |
| tag: 14.12.0-debian-12-r9 |
🤖 Prompt for AI Agents
In deploy/helm/values.yaml around line 58, the image tag `14.12.0` under
repository bitnamilegacy/postgresql is not published; update the tag to the
available `14.12.0-debian-12-r9` and add a single-line TODO comment next to this
value indicating it's a temporary workaround and should be reverted to the
official Bitnami image when the canonical tag is published; after changing,
verify the tag exists in the registry to avoid deployment failures and ensure
the TODO is removed once you switch back.
2 participants
Description
Bitnami has deprecated the images we rely on by default in the chart. We need to figure out how we adjust to this situation (and upgrade MongoDB as well to get off the EOL version here). For now, use the bitnamilegacy images.
see: bitnami/charts#35256
Fixes #
Issue Numberor
Fixes
Issue URLWarning
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.
Automation
/ok-to-test tags=""
🔍 Cypress test results
Caution
If you modify the content in this section, you are likely to disrupt the CI result for your PR.
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit