[Improvement] Liveness check and health check

[youngyjd]

What would you like to be improved?

In an ideal environment, we should have 2 type of checks:

1. Liveness check: to determine if a container has started or not
2. Readiness check: to determine if the container is ready to accept network traffic.

A real example - if db has not been init yet while we deploy the service, the liveness check should pass while the readiness check should fail.

Currently Gravitino has the api/version endpoint that is more suitable for liveness check. Is there an endpoint for readiness check?

How should we improve?

No response

[jerqi]

You can also use API /configs. The API won't need authentication.

[tengqm]

As stated in the issue description, readiness check is expected to indicate that the service can serve requests. So I don't think /configs is a proper endpoint for this purpose. If needed, we may add a /readyz endpoint for this purpose.

[jerqi]

As stated in the issue description, readiness check is expected to indicate that the service can serve requests. So I don't think /configs is a proper endpoint for this purpose. If needed, we may add a /readyz endpoint for this purpose.

Sorry for my confusing words. I want to say that configs can be used for liveness check.

[mchades]

How about using the testConnection endpoint: https://gravitino.apache.org/docs/0.8.0-incubating/api/rest/test-connection