f6c402a2bd
Sometimes, as it happened to me, a Pod's `restartPolicy` is mistakenly taken as the corresponding Job's restart policy. That was concluded before, here: https://github.com/kubernetes/community/pull/583/files The confusion happened here: https://github.com/kubernetes/kubernetes/issues/30243 https://github.com/kubernetes/kubernetes/issues/43964 And here: https://github.com/jaegertracing/jaeger-kubernetes/issues/32 This commit tries to clarify that there is no `restartPolicy` for the job itself, and that using either of `backoffLimit` and `activeDeadlineSeconds` may result in permanent failure. |
||
|---|---|---|
| .. | ||
| _index.md | ||
| cron-jobs.md | ||
| daemonset.md | ||
| deployment.md | ||
| garbage-collection.md | ||
| jobs-run-to-completion.md | ||
| replicaset.md | ||
| replicationcontroller.md | ||
| statefulset.md | ||
| ttlafterfinished.md | ||