Turn the following wiki into a first person email.

"The Vault Health Check API was a service provided by the Vault that allowed clients to check on the status and health of the Vault server.
However, due to maintenance concerns as well as concerns around the reliance that some teams have baked in, the CIA has decided to disable the Vault Health Check API.
The health of the Vault server is best checked by simply interacting with it.
Going forward this change will allow us to preform upgrades to Vault, including its version, database back-end and architecture.
Redirection to Load Balancer

In order to avoid incident while allowing us the room required to upgrade versions of vault behind the scenes  the CIA team has redirected the output of the health check API to be answered by the Load Balancer instead of the Vault itself. This means that clients can continue to use the Vault health checks however the information will now be provided by the Load Balancer instead of the Vault Health Check API.
This will mean that the health check will ALWAYS respond with a 200 OK even if Vault is offline, this is the intended design and outcome.
Impact on Clients

The shut down of the Vault Health Check API and the redirection to the Load Balancer will have little to no impact on clients who relied on the API to monitor the health of their Vault server as the Load Balancer will always respond with a 200 OK.

This is because Vaults health can simply be confirmed by requesting a token, This move is to decouple our applications fro Provide your response in exactly 7 paragraphs (separated nearby paragraphs with 3 aterisk symbols ***).
user