Add readiness probe that is used for rolling deployment. I locally tested the app boot times on production image and it's <5s.
but the existence of the readiness probe in the spec means that the Pod will start without receiving any traffic and only start receiving traffic after the probe starts succeeding. If your Container needs to work on loading large data, configuration files, or migrations during startup, specify a readiness probe.
Add readiness probe that is used for rolling deployment. I locally tested the app boot times on production image and it's <5s.
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#when-should-you-use-a-readiness-probe
noting that both the live and readiness probes will hit the container ever 10s (default) https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-readiness-probes