From 1e12dc29bacf51faf5a4c6980e05d72ab4b7ae38 Mon Sep 17 00:00:00 2001 From: Qiming Teng Date: Thu, 19 Oct 2017 14:57:16 +0800 Subject: [PATCH] Clarification of failureThreshold of probes --- .../configure-liveness-readiness-probes.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md b/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md index 0d8f60dd1afed..7d8f2ba001b9b 100644 --- a/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md +++ b/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md @@ -260,8 +260,9 @@ to 1 second. Minimum value is 1. * `successThreshold`: Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1. -* `failureThreshold`: Minimum consecutive failures for the probe to be -considered failed after having succeeded. Defaults to 3. Minimum value is 1. +* `failureThreshold`: When a Pod starts and the probe fails, Kubernetes will +try `failureThreshold` times before giving up and restarts the Pod. +Defaults to 3. Minimum value is 1. [HTTP probes](/docs/api-reference/{{page.version}}/#httpgetaction-v1-core) have additional fields that can be set on `httpGet`: