kubernetes: Recreate deployments dont wait for pod termination
The scenario is a single replica with an attached EBS.
The create seems to happen right after the delete not waiting for the pod to be terminated. This results in the two kubelets fighting over the EBS which generally results in AWS becoming unhappy meaning the EBS has to be force detached.
From the docs All existing Pods are killed before new ones are created when .spec.strategy.type==Recreate I would have thought deployments would wait until the pod is actually killed.
Is this a bug or am i misinterpreting the docs?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 23 (12 by maintainers)
Commits related to this issue
- Merge pull request #27713 from kargakis/wait-for-synced-rs-in-recreate Automatic merge from submit-queue controller: wait for synced old replica sets on Recreate Partially fixes https://github.com/... — committed to kubernetes/kubernetes by k8s-github-robot 8 years ago
- Merge pull request #45639 from ChipmunkV/fix-recreate-syncs Automatic merge from submit-queue 1.6 backport: Recreate deployments dont wait for pod termination The #27362 was fixed in #43963. Wasn't... — committed to kubernetes/kubernetes by deleted user 7 years ago
Why it’s closed?
It’s not fixed: Recreate still doesn’t wait for termination.