kubernetes/pkg/controller/deployment
Michail Kargakis af0f5dcc88
Fix deployment timeout reporting
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>
2017-09-08 17:48:46 +02:00
..
util Fix deployment timeout reporting 2017-09-08 17:48:46 +02:00
BUILD Adds the rand.SafeEncodeString function and uses this function to 2017-08-30 14:01:11 -07:00
deployment_controller_test.go Migrate to NewControllerRef from meta/v1 package 2017-08-06 22:43:46 +10:00
deployment_controller.go controllers: simplify deepcopy calls 2017-08-29 19:21:24 +02:00
OWNERS Update OWNERS for pkg/controller/deployment 2017-01-26 10:24:52 -08:00
progress_test.go run hack/update-all 2017-06-22 11:31:03 -07:00
progress.go Remove failure check from deployment controller 2017-08-03 18:49:16 +02:00
recreate_test.go controllers: simplify deepcopy calls 2017-08-29 19:21:24 +02:00
recreate.go controller: cleanup complete deployments only 2017-07-11 19:20:14 +02:00
rollback.go run hack/update-all 2017-06-22 11:31:03 -07:00
rolling_test.go Scripted migration from clientset_generated to client-go. 2017-07-17 15:05:37 -07:00
rolling.go controller: cleanup complete deployments only 2017-07-11 19:20:14 +02:00
sync_test.go Scripted migration from clientset_generated to client-go. 2017-07-17 15:05:37 -07:00
sync.go Adds the rand.SafeEncodeString function and uses this function to 2017-08-30 14:01:11 -07:00