Conversation
Hello benzekrimaha,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
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
5964658 to
8d6260f
Compare
| runs-on: ubuntu-24.04 | ||
| strategy: | ||
| fail-fast: false | ||
| matrix: |
There was a problem hiding this comment.
no need for multiple mongodb builds : we have multiple zenko branches, and just one mongodb per zenko branch
| - 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" |
There was a problem hiding this comment.
- this is redundant with deps.yaml
- just "version"
| context: solution-base/images/mongodb-sharded/8.0/debian-12 | ||
| image: scality/zenko/mongodb-sharded | ||
| semver_tag: "8.0.13" | ||
| minor_tag: "8.0" |
There was a problem hiding this comment.
this can be computed from semvar_tag
| run: ./deploy-metadata.sh | ||
| working-directory: ./.github/scripts/end2end | ||
| if: ${{ inputs.deploy_metadata == 'true' }} | ||
| - name: '[DEBUG] Dump MongoDB pod status and logs' |
There was a problem hiding this comment.
for testing, you must use codespace (or a lab) instead of CI : it will be much more efficient and allow easily inspecting.
| matrix: | ||
| include: | ||
| - name: mongodb-sharded-8.0 | ||
| context: solution-base/images/mongodb-sharded/8.0/debian-12 |
There was a problem hiding this comment.
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)
No description provided.