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

Update pod-lifecycle.md

Browse Source 
I think there is a typo, `readiness problem` needs to be `readiness probe`.
This commit is contained in:
Vijay
2021-07-23 17:09:19 +12:00
committed by GitHub
parent 0ef9001c5e
commit 626b101340
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+1 -1
View File
@@ -311,7 +311,7 @@ is different from the liveness probe.
If your app has a strict dependency on back-end services, you can implement both If your app has a strict dependency on back-end services, you can implement both
a liveness and a readiness probe. The liveness probe passes when the app itself a liveness and a readiness probe. The liveness probe passes when the app itself
is healthy, but the readiness problem additionally checks that each required is healthy, but the readiness probe additionally checks that each required
back-end service is available. This helps you avoid directing traffic to Pods back-end service is available. This helps you avoid directing traffic to Pods
that can only respond with error messages. that can only respond with error messages.