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

Use Exited instead of Failed (#8038)

Browse Source 
* 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
This commit is contained in:
Karol Gołąb
2018-04-19 10:00:00 +02:00
committed by k8s-ci-robot
parent 41f311db5b
commit 28d673b949
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/workloads/pods/pod-lifecycle.md
+1 -1
View File
@@ -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, A PodSpec has a `restartPolicy` field with possible values Always, OnFailure,
and Never. The default value is Always. and Never. The default value is Always.
`restartPolicy` applies to all Containers in the Pod. `restartPolicy` only `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 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 back-off delay (10s, 20s, 40s ...) capped at five minutes, and is reset after ten
minutes of successful execution. As discussed in the minutes of successful execution. As discussed in the