Specifically zooming in on how Kubernetes liveness and readiness checks work, it will make sense to rethink how we mark an application healthy.
My current idea is that all critical dependencies must be checked and report healthy at least once at app startup time for the application to be marked healthy initially.
That way, we could mark an app live when it starts, and then we could mark an app ready only once it's dependencies are ready.
Specifically zooming in on how Kubernetes liveness and readiness checks work, it will make sense to rethink how we mark an application healthy.
My current idea is that all critical dependencies must be checked and report healthy at least once at app startup time for the application to be marked healthy initially.
That way, we could mark an app live when it starts, and then we could mark an app ready only once it's dependencies are ready.