From 28d673b94970e2c2a3bc2697e0ed4b02ccdc0788 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Karol=20Go=C5=82=C4=85b?= Date: Thu, 19 Apr 2018 10:00:00 +0200 Subject: [PATCH] Use Exited instead of Failed (#8038) * Use Terminated instead of Failed Containers that terminate successfully (exit code 0) can also be restarted and it's the default behaviour is restartPolicy is not specified. * Use Exited instead of Failed --- docs/concepts/workloads/pods/pod-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/pods/pod-lifecycle.md b/docs/concepts/workloads/pods/pod-lifecycle.md index 43ca6112a8..75dc84ff8b 100644 --- a/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/docs/concepts/workloads/pods/pod-lifecycle.md @@ -144,7 +144,7 @@ Note that the information reported as Pod status depends on the current A PodSpec has a `restartPolicy` field with possible values Always, OnFailure, and Never. The default value is Always. `restartPolicy` applies to all Containers in the Pod. `restartPolicy` only -refers to restarts of the Containers by the kubelet on the same node. Failed +refers to restarts of the Containers by the kubelet on the same node. Exited Containers that are restarted by the kubelet are restarted with an exponential back-off delay (10s, 20s, 40s ...) capped at five minutes, and is reset after ten minutes of successful execution. As discussed in the