From 61ceae64a07b6ec5ae5a715065ec516deb131cb9 Mon Sep 17 00:00:00 2001 From: Andreas Karis Date: Wed, 14 Aug 2024 23:51:03 +0200 Subject: [PATCH] Correct statement about Pod Ready condition in probe config section Signed-off-by: Andreas Karis Reported-at: https://github.com/kubernetes/website/issues/47503 --- .../configure-liveness-readiness-startup-probes.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) 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 e1101538ddd63..577c560dc1ca6 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 @@ -21,9 +21,12 @@ as for readiness probes, but with a higher failureThreshold. This ensures that t is observed as not-ready for some period of time before it is hard killed. The kubelet uses readiness probes to know when a container is ready to start -accepting traffic. A Pod is considered ready when all of its containers are ready. -One use of this signal is to control which Pods are used as backends for Services. -When a Pod is not ready, it is removed from Service load balancers. +accepting traffic. One use of this signal is to control which Pods are used as +backends for Services. A Pod is considered ready when its `Ready` [condition](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions) +is true. When a Pod is not ready, it is removed from Service load balancers. +A Pod's `Ready` condition is false when its Node's `Ready` condition is not true, +when one of the Pod's `readinessGates` is false, or when at least one of its containers +is not ready. The kubelet uses startup probes to know when a container application has started. If such a probe is configured, liveness and readiness probes do not start until