From 1b9f126ede40343597c66dfc408c6997413873fd Mon Sep 17 00:00:00 2001
From: majiayu000 <1835304752@qq.com>
Date: Fri, 26 Dec 2025 17:44:50 +0800
Subject: [PATCH] docs: document healthcheck timeout termination behavior

Document that when a health check command exceeds its configured
timeout, the process is forcibly terminated. This clarifies the
behavior for users who need predictable handling of hung health
check commands.

Fixes #45927

Signed-off-by: majiayu000 <1835304752@qq.com>
---
 api/swagger.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/api/swagger.yaml b/api/swagger.yaml
index 610dc778d8..16363f6762 100644
--- a/api/swagger.yaml
+++ b/api/swagger.yaml
@@ -862,6 +862,10 @@ definitions:
         description: |
           The time to wait before considering the check to have hung. It should
           be 0 or at least 1000000 (1 ms). 0 means inherit.
+
+          If the health check command does not complete within this timeout,
+          the check is considered failed and the health check process is
+          forcibly terminated.
         type: "integer"
         format: "int64"
       Retries: