We already use the /_admin/server/availability HTTP endpoint as the healthcheck for ArangoDB containers in our deployment.

As part of migrating our microservices platform towards Kubernetes, we need to implement readiness checks for our microservices. Some of those services which make use of Arango need to consider Arango availability as part of the service readiness checks (not liveness checks).
See also spring-projects/spring-boot#23282

As such, it would be useful to be able to target the /_admin/server/availability HTTP endpoint - or have some other way of checking availability of Arango - through the driver Java interface.

In the absence of this I'm considering trying something like ArangoDatabase.getVersion() to determine availability, but that is clearly rather hacky. (If there's an alternative approach already available that you'd recommend, I'd welcome hearing about it.)