the K8s API doesn't update container ready state within a terminating
pod, as such you will find some pods which are terminating (maybe some
containers stopped) which katalog-sync is still dutifully trying to
sync. This check simply considers the pod not-ready if it has been
terminated.
the K8s API doesn't update container ready state within a terminating pod, as such you will find some pods which are terminating (maybe some containers stopped) which katalog-sync is still dutifully trying to sync. This check simply considers the pod not-ready if it has been terminated.