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

Pod lifecycle edge-cases for Recreate strategy

Browse Source 
Document Pod lifecycle behavior edge-case when using a Recreate strategy. This should document the "unexpected" behavior discussed in kubernetes/kubernetes#58814
This commit is contained in:
Christian Bürgi
2020-05-06 19:58:58 +02:00
committed by GitHub
parent 7bf97549f5
commit cf2d2b7970
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/deployment.md
+9
View File
@@ -1081,6 +1081,15 @@ the default value.
All existing Pods are killed before new ones are created when `.spec.strategy.type==Recreate`. All existing Pods are killed before new ones are created when `.spec.strategy.type==Recreate`.
{{< note >}}
This will only guarantee Pod termination previous to creation for upgrades. If you upgrade a Deployment, all Pods
of the old revision will be terminated immediately. Successful removal is awaited before any Pod of the new
revision is created. If you manually delete a Pod, the lifecycle is controlled by the ReplicaSet and the
replacement will be created immediately (even if the old Pod is still in a Terminating state). If you need an
"at most" guarantee for your Pods, you should consider using a
[StatefulSet](/docs/concepts/workloads/controllers/statefulset/).
{{< /note >}}
#### Rolling Update Deployment #### Rolling Update Deployment
The Deployment updates Pods in a rolling update The Deployment updates Pods in a rolling update