kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #47236 from my-git9/pp-16101 

[zh-cn] sync configure-liveness-readiness-startup-probes.md
pull/47244/head
Kubernetes Prow Robot 2024-07-22 16:20:07 -07:00 committed by GitHub
parent dd49d8d4fb f5e95f691a
commit d4f7326a46
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/zh-cn/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
View File

@ -660,6 +660,7 @@ liveness and readiness checks:
<!--
* `failureThreshold`: After a probe fails `failureThreshold` times in a row, Kubernetes
considers that the overall check has failed: the container is _not_ ready/healthy/live.
Defaults to 3. Minimum value is 1.
For the case of a startup or liveness probe, if at least `failureThreshold` probes have
failed, Kubernetes treats the container as unhealthy and triggers a restart for that
specific container. The kubelet honors the setting of `terminationGracePeriodSeconds`
@ -671,6 +672,7 @@ liveness and readiness checks:
-->
* `failureThreshold`：探针连续失败了 `failureThreshold` 次之后，
Kubernetes 认为总体上检查已失败：容器状态未就绪、不健康、不活跃。
默认值为 3，最小值为 1。
对于启动探针或存活探针而言，如果至少有 `failureThreshold` 个探针已失败，
Kubernetes 会将容器视为不健康并为这个特定的容器触发重启操作。
kubelet 遵循该容器的 `terminationGracePeriodSeconds` 设置。