kubernetes/pkg/controller/deployment
Michail Kargakis d5227e364d controller: decouple cleanup policy from deployment strategies
Deployments get cleaned up only when they are paused, they get scaled up/down,
or when the strategy that drives rollouts completes. This means that stuck
deployments that fall into none of the above categories will not get cleaned
up. Since cleanup is already safe by itself (we only delete old replica sets
that are synced by the replica set controller and have no replicas) we can
execute it for every deployment when there is no intention to rollback.
2017-01-19 10:33:24 +01:00
..
util refactor: use metav1.ObjectMeta in other types 2017-01-17 16:17:19 -05:00
BUILD mechanical 2017-01-16 09:35:12 -05:00
deployment_controller_test.go refactor: use metav1.ObjectMeta in other types 2017-01-17 16:17:19 -05:00
deployment_controller.go controller: decouple cleanup policy from deployment strategies 2017-01-19 10:33:24 +01:00
OWNERS Update OWNERS based on PR comments 2016-11-02 16:28:23 -07:00
progress.go controller: wait for all pods to be deleted before Recreating 2016-12-15 19:55:18 +01:00
recreate_test.go start the apimachinery repo 2017-01-11 09:09:48 -05:00
recreate.go controller: decouple cleanup policy from deployment strategies 2017-01-19 10:33:24 +01:00
rollback.go Update deployment equality helper 2017-01-11 18:34:12 +01:00
rolling_test.go rename /release_1_5 to /clientset 2016-12-14 12:39:48 -08:00
rolling.go controller: decouple cleanup policy from deployment strategies 2017-01-19 10:33:24 +01:00
sync_test.go start the apimachinery repo 2017-01-11 09:09:48 -05:00
sync.go controller: decouple cleanup policy from deployment strategies 2017-01-19 10:33:24 +01:00