Skip to content

mongodb: bump mongodb-sharded chart to 9.4.14#2424

Merged
bert-e merged 4 commits into
development/2.15from
improvement/ZENKO-5276/bump-mongodb-sharded-9.4.14
May 29, 2026
Merged

mongodb: bump mongodb-sharded chart to 9.4.14#2424
bert-e merged 4 commits into
development/2.15from
improvement/ZENKO-5276/bump-mongodb-sharded-9.4.14

Conversation

@delthas
Copy link
Copy Markdown
Contributor

@delthas delthas commented May 28, 2026

Summary

Bump the vendored mongodb-sharded chart from 9.4.49.4.14 to pick up the upstream pgrep -x liveness-probe fix (bitnami/charts#36488) — the chart-side fix for the mongos/configsvr startup race we hit in production.

Why

The mongos livenessProbe ran pgrep mongos, which substring-matches mongosh. During simultaneous StatefulSet startup, the bitnami entrypoint runs mongosh --host configsvr to 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 real mongos never gets execd, the probe stays green (matching the hung mongosh), 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 (mongod on shard-data, shard-arbiter, config-server).

What changes

  • solution-base/mongodb/MakefileCHART_VERSION: 9.4.4 → 9.4.14. Also incidentally fixes a latent Makefile bug from ZENKO-5281: git subtree split/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. The bug was hidden during ZENKO-5281 because the original subtree was bootstrapped via manual git commands at the repo root, not via make vendor-sync.
  • solution-base/mongodb/charts/mongodb-sharded/git subtree merge --squash of upstream mongodb-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:
    Squashed 'solution-base/mongodb/charts/mongodb-sharded/' changes from d2eb70018d..cd87843fdd
    git-subtree-split: cd87843fdd50168708d5acb661e1ab3ce7672a54
    
  • solution-base/mongodb/charts/mongodb-sharded/charts/common/helm dependency build resolved a newer bitnami/common (2.31.0 → 2.31.4). Minor refinements only.

Verification

  • pgrep -x is now in all four probe files (mongos, shard-data, shard-arbiter, config-server).
  • Chart.yaml: version: 9.4.14, appVersion: 8.0.13.
  • Local mods preserved (custom mongos entrypoint via configmap, configServer.serviceName helper, redirect-logs, etc.).
  • helm template renders 20 manifests; helm lint passes.

What does NOT change

  • solution-base/deps.yaml — image refs point at ghcr.io/scality/zenko/* from ZENKO-5110, independent of the chart's annotations.images. The image bump (8.0.12 → 8.0.13) in upstream's annotations.images doesn't propagate here; Zenko's deployed images are governed by deps.yaml separately.
  • solution-base/build.sh — untouched; the charts/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

delthas added 4 commits May 28, 2026 17:10
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
`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
@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented May 28, 2026

Hello delthas,

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
Copy link
Copy Markdown
Contributor

bert-e commented May 28, 2026

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

@delthas delthas requested review from a team, francoisferrand and maeldonn May 28, 2026 15:31
@delthas
Copy link
Copy Markdown
Contributor Author

delthas commented May 29, 2026

/approve

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented May 29, 2026

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.15

The following branches have NOT changed:

  • development/2.10
  • development/2.11
  • development/2.12
  • development/2.13
  • development/2.14
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue ZENKO-5276.

Goodbye delthas.

The following options are set: approve

@bert-e bert-e merged commit 1ff3dcb into development/2.15 May 29, 2026
35 of 38 checks passed
@bert-e bert-e deleted the improvement/ZENKO-5276/bump-mongodb-sharded-9.4.14 branch May 29, 2026 13:19
@delthas delthas mentioned this pull request May 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants