Skip to content

Commit db4b6a1

Browse files
authored
Update configure-liveness-readiness-startup-probes.md
1 parent 45cba61 commit db4b6a1

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -397,10 +397,11 @@ liveness and readiness checks:
397397

398398
* `initialDelaySeconds`: Number of seconds after the container has started before startup,
399399
liveness or readiness probes are initiated. If a startup probe is defined, liveness and
400-
readiness probe delays do not begin until the startup probe has succeeded. Older versions
401-
of Kubernetes might have ignored initialDelaySeconds if periodSeconds was larger. However,
402-
in current versions, initialDelaySeconds is always honored and the probe will not start
403-
until after this initial delay. Defaults to 0 seconds. Minimum value is 0.
400+
readiness probe delays do not begin until the startup probe has succeeded. In some older
401+
Kubernetes versions, the initialDelaySeconds might be ignored if periodSeconds was set to
402+
a value higher than initialDelaySeconds. However, in current versions, initialDelaySeconds
403+
is always honored and the probe will not start until after this initial delay. Defaults to
404+
0 seconds. Minimum value is 0.
404405
* `periodSeconds`: How often (in seconds) to perform the probe. Default to 10 seconds.
405406
The minimum value is 1.
406407
While a container is not Ready, the `ReadinessProbe` may be executed at times other than

0 commit comments

Comments
 (0)