File tree Expand file tree Collapse file tree 1 file changed +2
-0
lines changed
content/zh-cn/docs/tasks/configure-pod-container Expand file tree Collapse file tree 1 file changed +2
-0
lines changed Original file line number Diff line number Diff line change @@ -660,6 +660,7 @@ liveness and readiness checks:
660
660
<!--
661
661
* `failureThreshold`: After a probe fails `failureThreshold` times in a row, Kubernetes
662
662
considers that the overall check has failed : the container is _not_ ready/healthy/live.
663
+ Defaults to 3. Minimum value is 1.
663
664
For the case of a startup or liveness probe, if at least `failureThreshold` probes have
664
665
failed, Kubernetes treats the container as unhealthy and triggers a restart for that
665
666
specific container. The kubelet honors the setting of `terminationGracePeriodSeconds`
@@ -671,6 +672,7 @@ liveness and readiness checks:
671
672
-->
672
673
* `failureThreshold`:探针连续失败了 `failureThreshold` 次之后,
673
674
Kubernetes 认为总体上检查已失败:容器状态未就绪、不健康、不活跃。
675
+ 默认值为 3,最小值为 1。
674
676
对于启动探针或存活探针而言,如果至少有 `failureThreshold` 个探针已失败,
675
677
Kubernetes 会将容器视为不健康并为这个特定的容器触发重启操作。
676
678
kubelet 遵循该容器的 `terminationGracePeriodSeconds` 设置。
You can’t perform that action at this time.
0 commit comments