From 558bd9c0142bf15cac600689b059fa8856fa908a Mon Sep 17 00:00:00 2001 From: Akanksha kumari Date: Sat, 16 Jul 2022 16:54:39 +0530 Subject: [PATCH] Update configure-liveness-readiness-startup-probes.md --- .../configure-liveness-readiness-startup-probes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md index 3f4c1c8dcd..b6c2efe585 100644 --- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md +++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md @@ -97,7 +97,7 @@ kubectl describe pod liveness-exec ``` At the bottom of the output, there are messages indicating that the liveness -probes have failed, and the containers have been killed and recreated. +probes have failed, and the failed containers have been killed and recreated. ``` Type Reason Age From Message @@ -117,7 +117,7 @@ Wait another 30 seconds, and verify that the container has been restarted: kubectl get pod liveness-exec ``` -The output shows that `RESTARTS` has been incremented: +The output shows that `RESTARTS` has been incremented. Note that the `RESTARTS` counter increments as soon as a failed container in a restarts : ``` NAME READY STATUS RESTARTS AGE