werf/kubedog

Fallback tracker for unsupported resources kinds

distorhead opened this issue · 2 comments

Fallback tracker should work similarly to kubectl wait --for condition=Ready. Maybe import kubectl wait code as a first step.

Seems like there is no common conditions. Each resource kind have own set of conditions. Need more research which conditions is suitable for kubedog rollout tracker for each resource kind.

Done in #255