af0f5dcc88
If the previous condition has been a successful rollout then we shouldn't try to estimate any progress. Scenario: * progressDeadlineSeconds is smaller than the difference between now and the time the last rollout finished in the past. * the creation of a new ReplicaSet triggers a resync of the Deployment prior to the cached copy of the Deployment getting updated with the status.condition that indicates the creation of the new ReplicaSet. The Deployment will be resynced and eventually its Progressing condition will catch up with the state of the world. Signed-off-by: Michail Kargakis <mkargaki@redhat.com> |
||
|---|---|---|
| .. | ||
| BUILD | ||
| deployment_util_test.go | ||
| deployment_util.go | ||
| hash_test.go | ||
| pod_util.go | ||
| replicaset_util.go | ||