You will find this documentation <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/> interesting as it advises how to implement and configure "readiness and startup" probes for your containers. The "liveness" probe can check a container or when an application has stalled and does not accept traffic. This approach can be customised to suit your requirements rather than relying on a general catch all signal. On Monday, April 5, 2021 at 5:42:20 AM UTC+2 luca...@icloud.com wrote:
> Hi There, > > I have a few Java microservices and when I redeploy them, one of them > needs like 40 seconds after starting up (it's a dropwizard application) to > load data and do some computation to actually be ready to serve requests. > This extra time makes so GCP thinks the service is ready and keeps > deploying other instances and when the service receives requests they fail. > > How does GCP determins that a Kubernetes app is ready to serve request? Is > there a way to prologue the deployment state or tell GCP that it's not > finished until say, an API returns a 200? > > Thanks > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7e4bf3e0-60b6-45eb-8428-5a977438ea7cn%40googlegroups.com.
