From 8f0065597141c1618efa63ca8c464427640a8ebc Mon Sep 17 00:00:00 2001 From: Baptiste Gauduchon Date: Thu, 3 Jan 2019 16:10:35 +0100 Subject: [PATCH] Update proposal for configure-liveness-readiness-probes.md (#11613) * Update proposal for configure-liveness-readiness-probes.md Proposal regarding [issue 11587](https://github.com/kubernetes/website/issues/11587) * :pencil2: corrected typo * :pencil2: corrected sentence * Update configure-liveness-readiness-probes.md --- .../configure-liveness-readiness-probes.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md index 6750af2063c84..36c4f758ac070 100644 --- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md +++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md @@ -235,12 +235,17 @@ livenessProbe: Sometimes, applications are temporarily unable to serve traffic. For example, an application might need to load large data or configuration -files during startup. In such cases, you don't want to kill the application, +files during startup, or depend on external services after startup. +In such cases, you don't want to kill the application, but you don’t want to send it requests either. Kubernetes provides readiness probes to detect and mitigate these situations. A pod with containers reporting that they are not ready does not receive traffic through Kubernetes Services. +{{< note >}} +Readiness probes runs on the container during its whole lifecycle. +{{< /note >}} + Readiness probes are configured similarly to liveness probes. The only difference is that you use the `readinessProbe` field instead of the `livenessProbe` field.