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.
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
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Lets not forget that the health checks can be more complicated, returning a
200is ok I guess but it can be so much better.Also, I think the first
deployment.ymlcode should point to/healtzThe 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! :)
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