Build our own mongodb image by benzekrimaha · Pull Request #2366 · scality/Zenko

benzekrimaha · 2026-03-26T06:50:12Z

No description provided.

bert-e · 2026-03-26T06:50:16Z

Hello benzekrimaha,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
`/after_pull_request`	Wait for the given pull request id to be merged before continuing with the current one.
`/bypass_author_approval`	Bypass the pull request author's approval	⭐
`/bypass_build_status`	Bypass the build and test status	⭐
`/bypass_commit_size`	Bypass the check on the size of the changeset `TBA`	⭐
`/bypass_incompatible_branch`	Bypass the check on the source branch prefix	⭐
`/bypass_jira_check`	Bypass the Jira issue check	⭐
`/bypass_peer_approval`	Bypass the pull request peers' approval	⭐
`/bypass_leader_approval`	Bypass the pull request leaders' approval	⭐
`/approve`	Instruct Bert-E that the author has approved the pull request.		✍️
`/create_pull_requests`	Allow the creation of integration pull requests.
`/create_integration_branches`	Allow the creation of integration branches.
`/no_octopus`	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
`/unanimity`	Change review acceptance criteria from `one reviewer at least` to `all reviewers`
`/wait`	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
`/help`	Print Bert-E's manual in the pull request.
`/status`	Print Bert-E's current status in the pull request `TBA`
`/clear`	Remove all comments from Bert-E from the history `TBA`
`/retry`	Re-start a fresh build `TBA`
`/build`	Re-start a fresh build `TBA`
`/force_reset`	Delete integration branches & pull requests, and restart merge process from the beginning.
`/reset`	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

bert-e · 2026-03-26T06:50:23Z

Incorrect fix version

The Fix Version/s in issue ZENKO-5110 contains:

2.13.3
2.14.0

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

2.13.10
2.14.2

Please check the Fix Version/s of ZENKO-5110, or the target
branch of this pull request.

bert-e · 2026-03-26T12:50:36Z

Incorrect fix version

The Fix Version/s in issue ZENKO-5110 contains:

2.13.3
2.14.2

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

2.13.10
2.14.2

Please check the Fix Version/s of ZENKO-5110, or the target
branch of this pull request.

Fork Bitnami mongodb-sharded Dockerfiles and vendored scripts into the Zenko repository (TAD Approach B). Build four container images: - mongodb-sharded 8.0.13 (mongod/mongos for the sharded cluster) - mongodb-sharded 8.2.6 (same layout, newer major) - mongodb-exporter 0.49.0 (Prometheus metrics sidecar) - os-shell 12 (init-container / utility image) MongoDB server binaries are downloaded directly from fastdl.mongodb.org (amd64 uses the debian12 tarball, arm64 uses ubuntu2204). Bitnami helper tools (yq, wait-for-port, render-template, mongodb-shell) are still fetched from downloads.bitnami.com. All vendored .sh scripts are made executable at build time via `RUN find /opt/bitnami/scripts -name "*.sh" -exec chmod a+x {} +` to prevent the "Permission denied" crash that occurs when the Helm chart configmap entrypoint calls `exec /entrypoint.sh`. issue:ZENKO-5110

Add a reusable workflow that builds and pushes the four mongodb-sharded images to ghcr.io/scality/zenko/ using Docker Buildx (linux/amd64). Each image is tagged with: - <version> (mutable, referenced by deps.yaml) - <version>-<hash> (immutable, for TAD audit trail) The hash is the first 8 characters of `git rev-parse HEAD:<context-dir>`, so it changes if and only if a file inside the build context changes. issue:ZENKO-5110

Point the mongodb-sharded, mongodb-exporter and os-shell image references to the newly built images under ghcr.io/scality/zenko/. This replaces the previous references to Bitnami-hosted images that required a paid subscription secret for pulls. issue:ZENKO-5110

Dump pod status, container logs (current + previous), init-container logs, events and binary checks for all mongodb-related pods. Runs with if: always() and continue-on-error: true so it never blocks the pipeline but captures crash details. Temporary — remove once mongodb image stability is confirmed. issue:ZENKO-5110

francoisferrand · 2026-03-27T09:46:05Z

.github/workflows/build-mongodb-images.yaml

+    runs-on: ubuntu-24.04
+    strategy:
+      fail-fast: false
+      matrix:


no need for multiple mongodb builds : we have multiple zenko branches, and just one mongodb per zenko branch

francoisferrand · 2026-03-27T09:46:36Z

.github/workflows/build-mongodb-images.yaml

+          - name: mongodb-sharded-8.0
+            context: solution-base/images/mongodb-sharded/8.0/debian-12
+            image: scality/zenko/mongodb-sharded
+            semver_tag: "8.0.13"


this is redundant with deps.yaml

just "version"

francoisferrand · 2026-03-27T09:46:46Z

.github/workflows/build-mongodb-images.yaml

+            context: solution-base/images/mongodb-sharded/8.0/debian-12
+            image: scality/zenko/mongodb-sharded
+            semver_tag: "8.0.13"
+            minor_tag: "8.0"


this can be computed from semvar_tag

francoisferrand · 2026-03-27T09:50:24Z

.github/actions/deploy/action.yaml

      run: ./deploy-metadata.sh
      working-directory: ./.github/scripts/end2end
      if: ${{ inputs.deploy_metadata == 'true' }}
+    - name: '[DEBUG] Dump MongoDB pod status and logs'


to be removed

for testing, you must use codespace (or a lab) instead of CI : it will be much more efficient and allow easily inspecting.

francoisferrand · 2026-03-27T09:58:54Z

.github/workflows/build-mongodb-images.yaml

+      matrix:
+        include:
+          - name: mongodb-sharded-8.0
+            context: solution-base/images/mongodb-sharded/8.0/debian-12


should be computed from deps.yaml : we need to build a few images. just go over the list in deps.yaml and derive the info we need (using matching path as needed)

Derive build matrix from deps.yaml using yq instead of hardcoding versions and context paths Remove redundant 8.2 build | Compute minor_tag from version instead of hardcoding it Remove temporary debug step from deploy action Issue:ZENKO-5110

The scubaclient postinstall step runs tsc --strict which fails when a newer @types/node (22+) is resolved transitively, introducing a URLPattern type conflict with TypeScript DOM types. Pin to ^20.17.0 to match the Node 20 runtime. Issue:ZENKO-5110

benzekrimaha changed the title ~~Improvement/zenko 5110 build our own bitnami image~~ Build our own mongodb image Mar 26, 2026

benzekrimaha added 4 commits March 26, 2026 17:49

benzekrimaha force-pushed the improvement/ZENKO-5110-build-our-own-bitnami-image branch from 5964658 to 8d6260f Compare March 26, 2026 16:49

francoisferrand reviewed Mar 27, 2026

View reviewed changes

benzekrimaha force-pushed the improvement/ZENKO-5110-build-our-own-bitnami-image branch from 692574c to b439d92 Compare March 29, 2026 17:04

benzekrimaha force-pushed the improvement/ZENKO-5110-build-our-own-bitnami-image branch from b439d92 to 67b7123 Compare March 30, 2026 13:23

benzekrimaha force-pushed the improvement/ZENKO-5110-build-our-own-bitnami-image branch from 69ce420 to d94b364 Compare March 30, 2026 14:21

fixup! pin @types/node to Node 20 line to fix scubaclient build

410c0d0

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Build our own mongodb image#2366

Build our own mongodb image#2366
benzekrimaha wants to merge 7 commits intodevelopment/2.13from
improvement/ZENKO-5110-build-our-own-bitnami-image

benzekrimaha commented Mar 26, 2026 •

edited

Loading

Uh oh!

bert-e commented Mar 26, 2026

Uh oh!

bert-e commented Mar 26, 2026

Uh oh!

bert-e commented Mar 26, 2026

Uh oh!

francoisferrand Mar 27, 2026

Uh oh!

francoisferrand Mar 27, 2026

Uh oh!

francoisferrand Mar 27, 2026

Uh oh!

francoisferrand Mar 27, 2026

Uh oh!

francoisferrand Mar 27, 2026

Uh oh!

francoisferrand Mar 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

benzekrimaha commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bert-e commented Mar 26, 2026

Hello benzekrimaha,

Uh oh!

bert-e commented Mar 26, 2026

Incorrect fix version

Uh oh!

bert-e commented Mar 26, 2026

Incorrect fix version

Uh oh!

francoisferrand Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

francoisferrand Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

francoisferrand Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

francoisferrand Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

francoisferrand Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

francoisferrand Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

benzekrimaha commented Mar 26, 2026 •

edited

Loading