From 27ceb5928adbbed93ab545931d568777a001537f Mon Sep 17 00:00:00 2001 From: Ajay <217481+ajaygm@users.noreply.github.com> Date: Fri, 8 Jan 2021 11:48:48 +0530 Subject: [PATCH] rephrased as suggested by tengqm Co-authored-by: Qiming Teng --- .../docs/concepts/workloads/controllers/garbage-collection.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/garbage-collection.md b/content/en/docs/concepts/workloads/controllers/garbage-collection.md index aaf9cd08ac..1b1de5d0a4 100644 --- a/content/en/docs/concepts/workloads/controllers/garbage-collection.md +++ b/content/en/docs/concepts/workloads/controllers/garbage-collection.md @@ -154,7 +154,8 @@ kubectl also supports cascading deletion. To delete dependents in the foreground using kubectl, set `--cascade=foreground`. To orphan dependents, set `--cascade=orphan`. -The default behavior is to delete dependents in the background i.e. no `--cascade` option or `--cascade=background`. +The default behavior is to delete the dependents in the background which is the +behavior when `--cascade` is omitted or explicitly set to `background`. Here's an example that orphans the dependents of a ReplicaSet: