DEV Community

Liveness and Readiness Probes with Laravel

Pietro Bongiovanni on April 08, 2018

This post was first published on my blog, to see my posts when I first publish them, check it out! Liveness and readiness probes are two of the st...
Collapse
 
eduardort profile image
Eduardo Reyes

Lets not forget that the health checks can be more complicated, returning a 200 is ok I guess but it can be so much better.

Also, I think the first deployment.yml code should point to /healtz

Collapse
 
pgoodjohn profile image
Pietro Bongiovanni

The health check can definitely be more complicated, but the requirement is that it returns a Status Code which is 200 < status code < 400 so I went for the most basic one!

Also, good catch, my copy-pasting skills are getting rusty.

Have a great day! :)

Collapse
 
marco_siciliano profile image
Marco Siciliano • Edited

Hi,
i have a laravel websocket deployment running in a pod and a service listening on port 7676 for incoming websocket connections.
My problem now is that i have to configure liveness- /readiness probes to get my ingress running (otherwise my backend service - laravel websockets - remain UNHEALTHY)
How can i add liveness/readiness probes probe to my laravel websocket server?
Any idea?

Do i need to put an nginx in fron of my container running the laravel websocket?

Greetings
Marco