fix: route MongoDB PBM dataprotection through syncer#3110
Draft
gnolong wants to merge 12 commits into
Draft
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-1.1 #3110 +/- ##
===========================================
Coverage 0.00% 0.00%
===========================================
Files 73 73
Lines 9383 9383
===========================================
Misses 9383 9383 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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 draft wires MongoDB PBM physical backup, physical restore, and PITR addon flows through the syncer dataprotection API for both sharding and replicaset topologies.
Changes include:
syncerwith thepbm-agentworkload type, while keeping PBM agent MongoDB connections local to each podmongosundersyncerwith themongosworkload type so it can participate in sharded restore coordinationsyncerctlinto the data volume so ActionSet jobs can call the target pod syncer service remotelysyncerctl backup,syncerctl restore, andsyncerctl pitrcallsLocal Validation
bash -nfor updated MongoDB dataprotection scriptsgit diff --checkhelm lint addons/mongodbhelm template kb-addon-mongodb addons/mongodb --namespace kb-systemSYNCER_TEST_TOPOLOGY=sharding SYNCER_TEST_RUN_E2E=true go test ./test/e2e/mongodb -run TestShardingFullBackupRestore -count=1 -v -timeout 45mSYNCER_TEST_TOPOLOGY=sharding SYNCER_TEST_RUN_E2E=true go test ./test/e2e/mongodb -run TestShardingPITR -count=1 -v -timeout 45mSYNCER_TEST_TOPOLOGY=replicaset SYNCER_TEST_RUN_E2E=true go test ./test/e2e/mongodb -run TestReplicaSetFullBackupRestore -count=1 -v -timeout 45mSYNCER_TEST_TOPOLOGY=replicaset SYNCER_TEST_RUN_E2E=true go test ./test/e2e/mongodb -run TestReplicaSetPITR -count=1 -v -timeout 45m