-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Issue fix 4874 and 4752 #5319
Issue fix 4874 and 4752 #5319
Conversation
Signed-off-by: Lyndon-Li <[email protected]>
8ab8b51
to
409b6d5
Compare
409b6d5
to
d6c995a
Compare
Codecov Report
@@ Coverage Diff @@
## main #5319 +/- ##
==========================================
- Coverage 40.86% 40.84% -0.02%
==========================================
Files 233 233
Lines 20225 20241 +16
==========================================
+ Hits 8264 8267 +3
- Misses 11361 11375 +14
+ Partials 600 599 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
d6c995a
to
73c7244
Compare
Signed-off-by: Lyndon-Li <[email protected]>
73c7244
to
fbb2606
Compare
@Lyndon-Li thanks for the fix. Besides backup, I think it should be similar for restore error handling when restic pod can't be scheduled or running on the node. |
@jerry-jibu There is a separate issue for restore #5043, another PR will be submitted to fix it with a slightly different approach. |
Fix issue 4874 and 4752: check the daemonset pod is running in the node where the workload pod resides before running the PVB for the pod
Fixes #4874
Fixes #4752