refactor(controller): generalize Pod status synchronization - #939
Conversation
Signed-off-by: 少师 <zengyuwei.zyw@alibaba-inc.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #939 +/- ##
==========================================
- Coverage 83.09% 83.09% -0.01%
==========================================
Files 259 259
Lines 22545 22555 +10
==========================================
+ Hits 18734 18741 +7
- Misses 3090 3091 +1
- Partials 721 723 +2
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:
|
Signed-off-by: 少师 <zengyuwei.zyw@alibaba-inc.com>
8fa3b55 to
62aba48
Compare
Ⅰ. Describe what this PR does
Generalizes Pod status synchronization by replacing the Ready-only boolean with explicit synchronization options.
Ⅱ. Does this pull request fix one issue?
NONE
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
PendingReadyConditionandOwnsPendingReadyReasonprovide a generic extension point for backend-specific Pending failures without adding provider dependencies to the common controller.