From a2a28968652496dc3147d0f97b8d2ac234fc44c8 Mon Sep 17 00:00:00 2001 From: Prakher Singhal Date: Thu, 12 Nov 2020 14:51:23 +0530 Subject: [PATCH] Update pod-lifecycle.md Default for periodSeconds field of startupProbe resource is 10 seconds. $ kubectl explain pod.spec.containers.startupProbe.periodSeconds KIND: Pod VERSION: v1 FIELD: periodSeconds DESCRIPTION: How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 0905523fe2..8cbf9190a6 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -325,7 +325,7 @@ a time longer than the liveness interval would allow. If your container usually starts in more than `initialDelaySeconds + failureThreshold × periodSeconds`, you should specify a startup probe that checks the same endpoint as the liveness probe. The default for -`periodSeconds` is 30s. You should then set its `failureThreshold` high enough to +`periodSeconds` is 10s. You should then set its `failureThreshold` high enough to allow the container to start, without changing the default values of the liveness probe. This helps to protect against deadlocks.