From 4086706d999fc9834498d2a49f257d1eb38be71f Mon Sep 17 00:00:00 2001 From: flyer Date: Tue, 17 Oct 2017 00:44:40 +0800 Subject: [PATCH] garbage-collection.md: add CronJob/Job that sets ownerReference (#5917) --- docs/concepts/workloads/controllers/garbage-collection.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/concepts/workloads/controllers/garbage-collection.md b/docs/concepts/workloads/controllers/garbage-collection.md index ada0fc7446..cbb19276b4 100644 --- a/docs/concepts/workloads/controllers/garbage-collection.md +++ b/docs/concepts/workloads/controllers/garbage-collection.md @@ -24,9 +24,10 @@ points to the owning object. Sometimes, Kubernetes sets the value of `ownerReference` automatically. For example, when you create a ReplicaSet, Kubernetes automatically sets the -`ownerReference` field of each Pod in the ReplicaSet. In 1.6, Kubernetes +`ownerReference` field of each Pod in the ReplicaSet. In 1.8, Kubernetes automatically sets the value of `ownerReference` for objects created or adopted -by ReplicationController, ReplicaSet, StatefulSet, DaemonSet, and Deployment. +by ReplicationController, ReplicaSet, StatefulSet, DaemonSet, Deployment, Job +and CronJob. You can also specify relationships between owners and dependents by manually setting the `ownerReference` field.