fix(mongodb): route PBM dataprotection through syncer - #3241
Draft
gnolong wants to merge 2 commits into
Draft
Conversation
Port the MongoDB PBM dataprotection changes from release-1.1 PR #3110 onto the current main chart while preserving main-only storage path-style handling, runtime volume guards, ParametersDefinition resources, and the syncer image version.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3241 +/- ##
=====================================
Coverage 0.00% 0.00%
=====================================
Files 152 153 +1
Lines 23792 23837 +45
=====================================
- Misses 23792 23837 +45 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Jul 28, 2026
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
This is the
main-target port of the MongoDB PBM dataprotection work in #3110. It applies that PR's MongoDB addon diff without mergingrelease-1.1history intomain./tools/syncer -- /tools/pbm-agentsyncerctlMain adaptation
The source and target branches have diverged substantially, so this is a net-diff port rather than a merge or commit-by-commit cherry-pick. It preserves current
mainbehavior, including:1.2.0-alpha.0and syncer image tag0.7.7force_path_styleparsing and normalization from datasafed configurationParametersDefinitionand toggle-balancer resourcesThe storage-path tests were adapted to the new PVC-backed PBM config writer because the old direct
sync_pbm_storage_configpath is removed by this change.Validation
bash -non all added or modified MongoDB shell scripts andreplicaset-setup.tplhelm dependency build addons/mongodbhelm lint addons/mongodblogCollector.enabled=trueHelm renders1.1.0-beta.8for all 15 modified Helm templatesgit diff --checkshell-check, fullshellspec-test, generated-file checks, and all four Helm release checks passedThe complete local ShellSpec directory also contains two existing Ruby-backed spec files. Their 9 examples could not execute locally because
rubyis not installed; the 10 tests covering this port passed, and GitHub's Ruby-capable full ShellSpec job passed. Runtime volume rendering was also checked independently in both enabled and disabled modes.A full-chart server-side dry-run against
1.1.0-beta.8reaches the unchangedmainParametersDefinitionresources and fails because that beta.8 CRD does not recognize the newer main fields. Every template changed by this PR passes an isolated server-side dry-run.E2E status
The backup/restore/PITR compatibility evidence for the source change is recorded in #3110.
Follow-up hscale validation after upgrading KubeBlocks to
1.1.0-beta.8found an unresolved controller/lifecycle boundary: the MongoDB4.4.29active-backup hscale case failed because HorizontalScaling reachedSucceed 2/2while the target PBM backup was active, after which the Backup remained Running until timeout because its target pod had been deleted. The independent MongoDB8.0.17run was interrupted before a terminal test result and is not reported as pass or fail.This remains a draft until the main-target backup/restore/PITR checks and the beta.8 hscale lifecycle behavior are resolved or explicitly scoped.