Description
Use case: I delete a resource to force it to be re-created by an operator.
I want to use kube-health to wait until the resource is re-created and progresses to a healthy state.
Current behavior: kube-health -O with a non-existent resource name returns immediately.
When called immediately after kubectl delete it usually does not wait because the resource does not yet exist, as there is an unpredicatble delay until the operator re-creates it.
Desired behavior: with waiting flags (-W or -O) kube-health first waits for the resource to exist, then waits for it to progress.
Backwards compatibility: add --ignore-not-found flag to return immediately with no error if resource not found (current behavior).
This is consistent with the meaning of --ignore-not-found as used by kubectl.