From e20b4585cedecb371d7149ab91d9beb9522018d5 Mon Sep 17 00:00:00 2001 From: Chao Xu Date: Mon, 28 Nov 2016 21:01:47 -0800 Subject: [PATCH] sync gc is not going to be supported in 1.5 --- docs/user-guide/garbage-collection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/garbage-collection.md b/docs/user-guide/garbage-collection.md index 2dc8e0c36a..bb8d046811 100644 --- a/docs/user-guide/garbage-collection.md +++ b/docs/user-guide/garbage-collection.md @@ -27,7 +27,7 @@ You can set up owner-dependent relationships among other objects by manually set When deleting an object, you can request the GC to ***asynchronously*** delete its dependents by ***explicitly*** specifying `deleteOptions.orphanDependents=false` in the deletion request that you send to the API server. A 200 OK response from the API server indicates the owner is deleted. -Synchronous garbage collection will be supported in 1.5 (tracking [issue](https://github.com/kubernetes/kubernetes/issues/29891)). +We are working on supporting synchronous garbage collection (tracking [issue](https://github.com/kubernetes/kubernetes/issues/29891)). If you specify `deleteOptions.orphanDependents=true`, or leave it blank, then the GC will first reset the `ownerReferences` in the dependents, then delete the owner. Note that the deletion of the owner object is asynchronous, that is, a 200 OK response will be sent by the API server before the owner object gets deleted.