As of now when a pod is synced but not ready katalog-sync will spin as fast as it can to recheck (no sleep). This adds a sleep in the event it wasn't ready to avoid burning all the CPU.
TODO: Another thing I noticed is the check here only ensures that the service was synced to consul not that the readiness has been synced -- which we probably want to check as well.
As of now when a pod is synced but not ready katalog-sync will spin as fast as it can to recheck (no sleep). This adds a sleep in the event it wasn't ready to avoid burning all the CPU.
TODO: Another thing I noticed is the check here only ensures that the service was synced to consul not that the readiness has been synced -- which we probably want to check as well.