You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Situation:
When trying to deploy Laravel Reverb on GKE cluster with native GCE Ingress it requires HTTP(s) health check to succeed before sending traffic through Load Balancer, as there is no such endpoint a workaround is required with using Nginx Ingress within cluster that will be a proxy and answering with the health checks, or similar workarounds
Proposed Solution:
Add health check endpoint that will be responding with HTTP 200 code when Reverb server is running
The text was updated successfully, but these errors were encountered:
Current Situation:
When trying to deploy Laravel Reverb on GKE cluster with native GCE Ingress it requires HTTP(s) health check to succeed before sending traffic through Load Balancer, as there is no such endpoint a workaround is required with using Nginx Ingress within cluster that will be a proxy and answering with the health checks, or similar workarounds
Proposed Solution:
Add health check endpoint that will be responding with HTTP 200 code when Reverb server is running
The text was updated successfully, but these errors were encountered: