-
Notifications
You must be signed in to change notification settings - Fork 85
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
Fix: Show current status of daemonset in karmor install #450
base: main
Are you sure you want to change the base?
Conversation
Thanks for the quick PR. There's no point of having the Verifiying logic run if the pod is in CrashLoopBackOff. We should skip that check if the Pod is not running |
The output should be something like in following order |
Resolved! |
@daemon1024 Please review |
@daemon1024 @Aryan-sharma11 Please review! |
@Aryan-sharma11 @daemon1024 Is this PR still relevant? |
Yes this is still relevant. |
Sorry, I am not sure how the earlier pings got missed |
No issues, we can restart the work! |
Let me try it locally, the changes look mostly great. Can you squash the commits meanwhile? |
Sorry for this, as this was very old PR, cleaning this PR |
Please don't apologise, our fault for not reviewing it for long. |
Signed-off-by: Manik2708 <[email protected]>
Thanks for your time, have cleaned this PR. Please see if it is ready to merge. To test it you might have to create a situation where pods are in some error or waiting state (probably by increasing the load and reducing the available resources for the pods) |
Fixes: #443
This change will now show the status of pods. The only doubt is what to do in
Pending
state of pod? Currently it will wait for the pod to beRunning
orFailed
. If Pod is running but container is not (due toCrashLoopBackOff
or something else) it will mark pod as not running and show the reason and break the loop! Please see this for reference: