-
Notifications
You must be signed in to change notification settings - Fork 253
chore: expose more conditions in component status #10032
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
base: main
Are you sure you want to change the base?
Conversation
|
Auto Cherry-pick Instructions |
eae9b69 to
88b0496
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10032 +/- ##
==========================================
+ Coverage 51.26% 51.39% +0.12%
==========================================
Files 539 539
Lines 58727 58786 +59
==========================================
+ Hits 30108 30212 +104
+ Misses 25667 25629 -38
+ Partials 2952 2945 -7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| // TODO: replicas == 0, stopped, updating, abnormal? | ||
| WithPhases: pointer.String(string(appsv1.RunningComponentPhase)), | ||
| WithPhases: pointer.String(strings.Join( | ||
| []string{string(appsv1.RunningComponentPhase), string(appsv1.UpdatingComponentPhase)}, |
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.
Updating is added as a default available phase, because any pod fail (such as a node down) can cause the phase to become Updating
a001419 to
8038a82
Compare
The current component condition provides very little information about why the component is not healthy.