Permalink
Browse files

Update proposal for configure-liveness-readiness-probes.md (#11613)

* Update proposal for configure-liveness-readiness-probes.md

Proposal regarding [issue 11587](#11587)

* ✏️ corrected typo

* ✏️ corrected sentence

* Update configure-liveness-readiness-probes.md
  • Loading branch information...
bgauduch authored and k8s-ci-robot committed Jan 3, 2019
1 parent ffa36a9 commit 8f0065597141c1618efa63ca8c464427640a8ebc
@@ -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.

0 comments on commit 8f00655

Please sign in to comment.