Skip to content

Commit bee671b

Browse files
authored
add warning about counterintuitive readiness probe
As evidenced by kubernetes/kubernetes#27114 the naming leads one to think that a liveness probe executes after a readiness probe. This is not the case.
1 parent f1c4f60 commit bee671b

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -293,6 +293,10 @@ Services.
293293
Readiness probes runs on the container during its whole lifecycle.
294294
{{< /note >}}
295295

296+
{{< warning >}}
297+
Liveness probes *do not* wait for readiness probes to succeed. If you want to wait before executing a liveness probe you should use initialDelaySeconds or a startupProbe.
298+
{{< /warning >}}
299+
296300
Readiness probes are configured similarly to liveness probes. The only difference
297301
is that you use the `readinessProbe` field instead of the `livenessProbe` field.
298302

0 commit comments

Comments
 (0)