Skip to content

Commit

Permalink
Update proposal for configure-liveness-readiness-probes.md (#11613)
Browse files Browse the repository at this point in the history 
* 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 @k8s-ci-robot
bgauduch authored and k8s-ci-robot committed Jan 3, 2019
1 parent ffa36a9 commit 8f00655
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion ...nt/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

1 comment on commit 8f00655

@khiradeshubham
Copy link

@khiradeshubham khiradeshubham commented on 8f00655 May 13, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this info

Readiness probes runs on the container during its whole lifecycle.

Do we have a specific reason for that? we already have liveness probe to check the health of the container then why do we need readiness probe after the container startup. I am currently facing an issue where in my running container readiness probe fails, I was confused to see such events with a running container.
Any insights would be helpful.

Please sign in to comment.