mongodb: bump mongodb-sharded chart to 9.4.14#2424
Merged
bert-e merged 4 commits intoMay 29, 2026
Conversation
Picks up the upstream `pgrep -x` liveness-probe fix from bitnami/charts#36488, which uses exact process name matching across the four StatefulSet liveness probes (mongos, shard-data, shard-arbiter, config-server). The previous substring-based `pgrep mongos` matched `mongosh`, allowing the mongos pod to deadlock during startup when the bitnami entrypoint's `mongosh --host configsvr` hung — the probe stayed green and Kubernetes never restarted the container. Also includes a latent Makefile fix from ZENKO-5281: `git subtree split` and `git subtree merge` require running from the repository toplevel, but `make -C solution-base/mongodb` runs recipes with cwd at this directory. Resolved by adding `cd $(TOPLEVEL)` to the subtree commands. Bug went unnoticed because ZENKO-5281's vendor was bootstrapped via manual git commands at the repo root, not via `make vendor-sync`. The next commit is the `git subtree merge --squash` produced by `make -C solution-base/mongodb vendor-sync` against `bitnami/charts` tag `mongodb-sharded/9.4.14`. Issue: ZENKO-5276
… d2eb70018d..cd87843fdd cd87843fdd [bitnami/mongodb-sharded] fix(mongos): use exact match in liveness pr… (#36488) 7d2adf0b7e Remove TAC sentence present in some READMEs (#36381) 17a6d71b7d Change wording in Chart's READMEs (#36379) 8eb8d71628 [bitnami/*] Remove annotations.category (#36224) 96fc3b1105 [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#36167) e309f8bf79 [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#35990) 0a7d86ee32 [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#35819) c60c2fb713 [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#35704) 4de6d2e193 [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#35623) ac145a069c [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#35595) 0ce1c4b0e5 [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#35507) 7e3c9c9489 [bitnami/mongodb-sharded] ⚡ ⬆️ Update dependency references (#35367) d2268cc5ff [bitnami/*] docs: update BSI warning on charts' notes (#35340) git-subtree-dir: solution-base/mongodb/charts/mongodb-sharded git-subtree-split: cd87843fdd50168708d5acb661e1ab3ce7672a54
…ent/ZENKO-5276/bump-mongodb-sharded-9.4.14
`helm dependency build` (invoked by `make vendor-sync`) resolved a newer `bitnami/common` from OCI (2.31.0 → 2.31.4). Minor refinements, no breaking changes to the helpers/templates the parent chart uses. Issue: ZENKO-5276
Contributor
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Contributor
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
francoisferrand
approved these changes
May 29, 2026
maeldonn
approved these changes
May 29, 2026
Contributor
Author
|
/approve |
Contributor
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue ZENKO-5276. Goodbye delthas. The following options are set: approve |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump the vendored
mongodb-shardedchart from9.4.4→9.4.14to pick up the upstreampgrep -xliveness-probe fix (bitnami/charts#36488) — the chart-side fix for the mongos/configsvr startup race we hit in production.Why
The mongos
livenessProberanpgrep mongos, which substring-matchesmongosh. During simultaneous StatefulSet startup, the bitnami entrypoint runsmongosh --host configsvrto wait for the configsvr replica set; that call hangs indefinitely when the configsvr port is open but the replica set hasn't completed primary election. The realmongosnever getsexecd, the probe stays green (matching the hungmongosh), readiness fails correctly but Kubernetes never restarts the container — the cluster deadlocks.Upstream PR #36488 adds
-x(exact name match) to that probe and consistency-hardens the matching three other probes (mongodon shard-data, shard-arbiter, config-server).What changes
solution-base/mongodb/Makefile—CHART_VERSION: 9.4.4 → 9.4.14. Also incidentally fixes a latent Makefile bug from ZENKO-5281:git subtree split/mergerequire running from the repository toplevel, butmake -C solution-base/mongodbruns recipes with cwd at this directory. Resolved by addingcd $(TOPLEVEL)to the subtree commands. The bug was hidden during ZENKO-5281 because the original subtree was bootstrapped via manual git commands at the repo root, not viamake vendor-sync.solution-base/mongodb/charts/mongodb-sharded/—git subtree merge --squashof upstreammongodb-sharded/9.4.14. Clean three-way merge against our 11 local-modification commits (no conflicts — upstream's pgrep change is in a region disjoint from our local edits). The squash commit reads:solution-base/mongodb/charts/mongodb-sharded/charts/common/—helm dependency buildresolved a newerbitnami/common(2.31.0 → 2.31.4). Minor refinements only.Verification
pgrep -xis now in all four probe files (mongos, shard-data, shard-arbiter, config-server).Chart.yaml:version: 9.4.14,appVersion: 8.0.13.configServer.serviceNamehelper, redirect-logs, etc.).helm templaterenders 20 manifests;helm lintpasses.What does NOT change
solution-base/deps.yaml— image refs point atghcr.io/scality/zenko/*from ZENKO-5110, independent of the chart'sannotations.images. The image bump (8.0.12 → 8.0.13) in upstream'sannotations.imagesdoesn't propagate here; Zenko's deployed images are governed bydeps.yamlseparately.solution-base/build.sh— untouched; thecharts/common/directory layout it relies on is preserved.Follow-up
Unblocks ARTESCA-17516 (revert the installer-side workaround) once a Zenko build incorporating this lands.
Issue: ZENKO-5276