-
Notifications
You must be signed in to change notification settings - Fork 917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wait for search multiClusterCache ReadinessCheck success #5846
Wait for search multiClusterCache ReadinessCheck success #5846
Conversation
02f9e98
to
e001898
Compare
Signed-off-by: changzhen <[email protected]>
e001898
to
d841142
Compare
Signed-off-by: changzhen <[email protected]>
d841142
to
9367ca9
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5846 +/- ##
==========================================
+ Coverage 46.03% 46.31% +0.28%
==========================================
Files 660 661 +1
Lines 53987 54364 +377
==========================================
+ Hits 24851 25177 +326
- Misses 27519 27562 +43
- Partials 1617 1625 +8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
/kind feature
What this PR does / why we need it:
To adapt to new features of the Kubernetes community: Resilient Watchcache Initialization, we also need to modify the Karmada-search component because we also use the same cache.
After the Karmada-search component is started, PostStartHook is added to wait for the cache to be ready. In addition, related ut is modified.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: