From bee671b57957fde9b97a9c4030856fc8036ffc36 Mon Sep 17 00:00:00 2001
From: Caleb Collins-Parks <46505081+caleb15@users.noreply.github.com>
Date: Thu, 4 Feb 2021 10:37:31 -0800
Subject: [PATCH] add warning about counterintuitive readiness probe

As evidenced by https://github.com/kubernetes/kubernetes/issues/27114 the naming leads one to think that a liveness probe executes after a readiness probe. This is not the case.
---
 .../configure-liveness-readiness-startup-probes.md            | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index 45d56531f2..e12e2684a6 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -293,6 +293,10 @@ Services.
 Readiness probes runs on the container during its whole lifecycle.
 {{< /note >}}
 
+{{< warning >}}
+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.
+{{< /warning >}}
+
 Readiness probes are configured similarly to liveness probes. The only difference
 is that you use the `readinessProbe` field instead of the `livenessProbe` field.