From 94e45834894b602ea11cbc3a68ff9f2ad6026438 Mon Sep 17 00:00:00 2001 From: Kenneth Owens Date: Mon, 11 Dec 2017 15:35:13 -0800 Subject: [PATCH] Garbage collection updates for 1.9 (#6555) * 1.9 gc policy update * carify deletion --- docs/concepts/workloads/controllers/garbage-collection.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/concepts/workloads/controllers/garbage-collection.md b/docs/concepts/workloads/controllers/garbage-collection.md index 2f83cc87ab..98c78d184c 100644 --- a/docs/concepts/workloads/controllers/garbage-collection.md +++ b/docs/concepts/workloads/controllers/garbage-collection.md @@ -106,9 +106,11 @@ To control the cascading deletion policy, set the `deleteOptions.propagationPoli field on your owner object. Possible values include "Orphan", "Foreground", or "Background". -The default garbage collection policy for many controller resources is `orphan`, -including ReplicationController, ReplicaSet, StatefulSet, DaemonSet, and -Deployment. So unless you specify otherwise, dependent objects are orphaned. +Prior to Kubernetes 1.9, the default garbage collection policy for many controller resources was `orphan`. +This included ReplicationController, ReplicaSet, StatefulSet, DaemonSet, and +Deployment. For kinds in the extensions/v1beta1, apps/v1beta1, and apps/v1beta2 group versions, unless you +specify otherwise, dependent objects are orphaned by default. In Kubernetes 1.9, for all kinds in the apps/v1 +group version, dependent objects are deleted by default. Here's an example that deletes dependents in background: