![]() Automatic merge from submit-queue kubectl: respect deployment strategy parameters for rollout status Fixes https://github.com/kubernetes/kubernetes/issues/40496 `rollout status` now respects the strategy parameters for a RollingUpdate Deployment. This means that it will exit as soon as minimum availability is reached for a rollout (note that if you allow maximum availability, `rollout status` will succeed as soon as the new pods are created) @janetkuo @AdoHe ptal |
||
---|---|---|
.. | ||
BUILD | ||
deployment_util_test.go | ||
deployment_util.go | ||
hash_test.go | ||
pod_util.go | ||
replicaset_util.go |