From 626b1013403833374253db6e6a9c998bfb62f090 Mon Sep 17 00:00:00 2001 From: Vijay Date: Fri, 23 Jul 2021 17:09:19 +1200 Subject: [PATCH] Update pod-lifecycle.md I think there is a typo, `readiness problem` needs to be `readiness probe`. --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 166d81e424..8f9a423edf 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -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 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 that can only respond with error messages.