Closed itsmurugappan closed 1 week ago
Hi, thanks for the PR.
Google cloud doesnt support "z" urls - https://stackoverflow.com/questions/43380939/where-does-the-convention-of-using-healthz-for-application-health-checks-come-f
Where does it say that? I couldn't find any reference to it. Do you have any documentation we can reference?
Regarding the change, unfortunately, it isn't good (and doesn't work) for two main reasons:
To properly perform this change you will have to:
openapi.yaml
you can run go generate ./...
to generate some stubs and boilerplate.Also, don't call the endpoint /hasura/healthz
. If the issue is that the endpoint is called healthz
we can just add a second one called /health
(without the z)
Where does it say that? I couldn't find any reference to it. Do you have any documentation we can reference?
Workloads in Google Cloud cannot have URL paths with /healthz
. here is are some references from stackoverflow
here is the proof (hasrua hosted in google Cloud Run)
When hasura-auth
container starts, it use this code to check if hasura
is UP and healthy. without this check pass, hasura-auth
in GCP will not start at all.
I think there is some misunderstanding here:
@itsmurugappan is asking to use Hasura's second health endpoint /hasura/healthz
instead of /healthz
[!IMPORTANT]
Hasura include both health-check endpoints in all deployment environments. we don't have to do anything for hasura.
I think this change will not have any side-effect
hasura docs
yes, you are completely right. I totally misinterpreted the change. Thanks for the clarification.
However, if you need this change because you are hosting hasura in GCP, wouldn't you also need an alternative /health endpoint for hasura-auth?
since hasura auth health check end point is not called through the loadbalancer by any client we dint need it.
yes, you are completely right. I totally misinterpreted the change. Thanks for the clarification.
However, if you need this change because you are hosting hasura in GCP, wouldn't you also need an alternative /health endpoint for hasura-auth?
Would be nice to have alternative health-check endpoints for all nhost services that won't conflict with GCP. But as minimum viable solution, this PR is good enough making it work in GCP.
Google cloud doesnt support "z" urls - https://stackoverflow.com/questions/43380939/where-does-the-convention-of-using-healthz-for-application-health-checks-come-f
And hasura provides an alternate end point for this https://hasura.io/docs/2.0/api-reference/health/ .
Checklist