Skip to content

Commit 9e15d65

Browse files
committed
[zh-cn]sync liveness-readiness-startup-probes.md
Signed-off-by: xin.li <xin.li@daocloud.io>
1 parent 1a3ad75 commit 9e15d65

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

content/zh-cn/docs/concepts/configuration/liveness-readiness-startup-probes.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -51,12 +51,14 @@ Liveness probes do not wait for readiness probes to succeed. If you want to wait
5151
<!--
5252
## Readiness probe
5353
54-
Readiness probes determine when a container is ready to start accepting traffic. This is useful when waiting for an application to perform time-consuming initial tasks, such as establishing network connections, loading files, and warming caches.
54+
Readiness probes determine when a container is ready to accept traffic. This is useful when waiting for an application to perform time-consuming initial tasks that depend on its backing services; for example: establishing network connections, loading files, and warming caches. Readiness probes can also be useful later in the container’s lifecycle, for example, when recovering from temporary faults or overloads.
5555
-->
5656
## 就绪探针 {#readiness-probe}
5757

58-
就绪探针决定何时容器准备好开始接受流量。
59-
这种探针在等待应用执行耗时的初始任务时非常有用,例如建立网络连接、加载文件和预热缓存。
58+
就绪探针决定容器何时准备好接受流量。
59+
这种探针在等待应用执行耗时的初始任务时非常有用;
60+
例如:建立网络连接、加载文件和预热缓存。在容器的生命周期后期,
61+
就绪探针也很有用,例如,从临时故障或过载中恢复时。
6062

6163
<!--
6264
If the readiness probe returns a failed state, Kubernetes removes the pod from all matching service endpoints.

0 commit comments

Comments
 (0)