Skip to content

Commit e547434

Browse files
mcbenjemaaTim Bannister
authored andcommitted
ssue with k8s.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/ (#16285)
* change livenessprobe restart concept to container * Update content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md Co-Authored-By: Tim Bannister <[email protected]>
1 parent 2df5c5c commit e547434

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -286,7 +286,7 @@ to 1 second. Minimum value is 1.
286286
considered successful after having failed. Defaults to 1. Must be 1 for
287287
liveness. Minimum value is 1.
288288
* `failureThreshold`: When a Pod starts and the probe fails, Kubernetes will
289-
try `failureThreshold` times before giving up. Giving up in case of liveness probe means restarting the Pod. In case of readiness probe the Pod will be marked Unready.
289+
try `failureThreshold` times before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe the Pod will be marked Unready.
290290
Defaults to 3. Minimum value is 1.
291291
292292
[HTTP probes](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#httpgetaction-v1-core)

0 commit comments

Comments
 (0)