The issue tracks the implementation of the /ready API in TiKV.

This API will be used to check the server's readiness after startup, similar to Kubernetes' readyz API. It will assist control plane services during rolling upgrades by making it easier to determine if an instance is fully ready to serve and whether the upgrade process can proceed to the next instance.

Having a unified readiness check interface across all TiDB components (TiKV, PD, TiDB) will simplify the process for control plane services, improving consistency and efficiency.

Note: PD has already implemented a similar API in #8749.