fix(dataprotection): pass target metadata to post-ready jobs - #10838
Conversation
|
Auto Cherry-pick Instructions CLA Recheck Instructions |
|
/approve |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10838 +/- ##
==========================================
+ Coverage 65.69% 65.75% +0.06%
==========================================
Files 510 510
Lines 64800 64860 +60
==========================================
+ Hits 42568 42649 +81
+ Misses 18447 18435 -12
+ Partials 3785 3776 -9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
/approve |
|
/cherry-pick release-1.1 |
|
🤖 says: Error cherry-picking. |
|
🤖 says: |
|
The automatic release-1.1 cherry-pick conflict has been resolved manually in #10839. The release-1.1 restore tests, full DataProtection controller suite, and make lint pass locally. |
Fixes #10679
What
Pass the restore target topology and expected service version to postReady Jobs targeting KubeBlocks Pods:
Implementation
BuildPostReadyActionJobs resolves both values after selecting the target Pod. The Job builder removes duplicate caller or Pod values and appends the controller values once, after the existing Restore, ActionSet, BackupMethod, credential, and Pod environment merge.
The behavior is selected by the existing KubeBlocks cluster/component labels on the target Pod. A target without those labels keeps the existing behavior. This change does not add an internal Restore marker, identity protocol, owner-chain validation, uncached-reader plumbing, or a new API.
Validation
Backport check