diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2016-08-05 12:41:31 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-05 12:41:31 -0700 |
| commit | 6941f61f64d26f3d9aeba92e984f3b2a6134064d (patch) | |
| tree | 1cc19a212e2a4e8b9ea25c7e4fd68d20c880eac6 /runtime-pod-cache.md | |
| parent | 9918db9e79a0dbf54bee5f0af150084f1c3c2f4a (diff) | |
| parent | cc0ae5749562b605dce38d41ba3264ae557e9a45 (diff) | |
Merge pull request #30155 from euank/clarify-container-lifecycle
Automatic merge from submit-queue
docs: Detail possible transitions in CRI
Right now the document doesn't make it clear that transitions are unidirectional and a exited container won't be restarted, but replaced by a fresh copy.
cc @yujuhong @feiskyer @kubernetes/sig-node
Diffstat (limited to 'runtime-pod-cache.md')
0 files changed, 0 insertions, 0 deletions