Does the OAuth 2.0 Auth Middleware provide health endpoints?

Both the HTTP JSON API service and the Trigger Service expose health endpoints, which makes it easy to manage containerized instances of the services with Kubernetes and similar orchestration systems.

Is this also available for the OAuth 2.0 Auth Middleware? I cannot see it documented neither as part of the Middleware API nor for its OAuth 2.0 implementation.

As of Daml 2.3.2, the OAuth 2.0 Auth Middleware provides a basic /livez endpoint but no /readyz endpoint. Neither is documented. The shortcoming is tracked as part of Add or document livelihood/readiness endpoints for the OAuth 2.0 Auth Middleware · Issue #14649 · digital-asset/daml · GitHub.