whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

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

Proposal regarding [issue 11587](https://github.com/kubernetes/website/issues/11587)

* ✏️ corrected typo

* ✏️ corrected sentence

* Update configure-liveness-readiness-probes.md
This commit is contained in:
Baptiste Gauduchon
2019-01-03 16:10:35 +01:00
committed by Kubernetes Prow Robot
parent ffa36a9251
commit 8f00655971
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
+6 -1
View File
@@ -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.