Files
kubernetes/pkg/kubectl
Kubernetes Submit Queue f0ce5bd8d8 Merge pull request #44672 from kargakis/update-deployment-completeness
Automatic merge from submit-queue (batch tested with PRs 43575, 44672)

Update deployment and daemonset completeness checks

maxUnavailable being taken into account for deployment completeness has caused a lot of confusion (https://github.com/kubernetes/kubernetes/issues/44395, https://github.com/kubernetes/kubernetes/issues/44657, https://github.com/kubernetes/kubernetes/issues/40496, others as well I am sure) so I am willing to just stop using it and require all of the new Pods for a Deployment to be available for the Deployment to be considered complete (hence both `rollout status` and ProgressDeadlineSeconds will not be successful in cases where a 1-pod Deployment never becomes successful because its Pod never transitions to ready).

@kubernetes/sig-apps-api-reviews thoughts?
```release-note
Deployments and DaemonSets are now considered complete once all of the new pods are up and running - affects `kubectl rollout status` (and ProgressDeadlineSeconds for Deployments)
```
Fixes https://github.com/kubernetes/kubernetes/issues/44395
2017-04-24 10:34:00 -07:00
..
2017-04-14 10:40:57 -07:00
2017-04-14 10:40:57 -07:00
2017-04-14 10:40:57 -07:00
2017-01-11 09:09:48 -05:00
2017-03-08 07:58:01 -08:00
2017-01-11 09:09:48 -05:00
2017-01-11 09:09:48 -05:00
2017-01-20 08:04:53 -05:00
2017-01-11 09:09:48 -05:00
2017-01-25 17:32:22 -08:00
2017-01-30 12:46:59 -05:00
2017-01-20 08:04:53 -05:00
2017-01-11 09:09:48 -05:00
2017-01-26 13:54:40 -05:00
2017-01-11 09:09:48 -05:00
2017-03-08 07:58:01 -08:00
2017-01-11 09:09:48 -05:00
2016-12-14 12:39:49 -08:00