Fix: Show current status of daemonset in karmor install

[Manik2708]

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 be Running or Failed. If Pod is running but container is not (due to CrashLoopBackOff or something else) it will mark pod as not running and show the reason and break the loop! Please see this for reference:

[daemon1024]

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

[Manik2708]

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

Done!

[Aryan-sharma11]

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

Done!

The output should be something like in following order
if pod.status == runinng {
print(" verifying kubearmor functionality")
} else {
print(" failed to verify kubearmor functionality, kubearmor daemonset failed to start" , pod. status.reason)
}
cc: @daemon1024

[Manik2708]

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

Done!

The output should be something like in following order if pod.status == runinng { print(" verifying kubearmor functionality") } else { print(" failed to verify kubearmor functionality, kubearmor daemonset failed to start" , pod. status.reason) } cc: @daemon1024

Resolved!

[Manik2708]

@daemon1024 Please review

[Manik2708]

@daemon1024 @Aryan-sharma11 Please review!