Merge pull request #29394 from Patil2099/cascade-fix

Replace cascade=false -> cascade=orphan

Author: k8s-ci-robot

content/en/blog/_posts/2021-05-14-using-finalizers-to-control-deletion.md

@@ -190,17 +190,17 @@ kubectl get configmap
 No resources found in default namespace.
 ```
 
-To sum things up, when there's an override owner reference from a child to a parent, deleting the parent deletes the children automatically. This is called `cascade`. The default for cascade is `true`, however, you can use the --cascade=false option for `kubectl delete` to delete an object and orphan its children. 
+To sum things up, when there's an override owner reference from a child to a parent, deleting the parent deletes the children automatically. This is called `cascade`. The default for cascade is `true`, however, you can use the --cascade=orphan option for `kubectl delete` to delete an object and orphan its children. 
 
-In the following example, there is a parent and a child. Notice the owner references are still included. If I delete the parent using --cascade=false, the parent is deleted but the child still exists:
+In the following example, there is a parent and a child. Notice the owner references are still included. If I delete the parent using --cascade=orphan, the parent is deleted but the child still exists:
 
 ```
 kubectl get configmap
 NAME           DATA   AGE
 mymap-child    0      13m8s
 mymap-parent   0      13m8s
 
-kubectl delete --cascade=false configmap/mymap-parent
+kubectl delete --cascade=orphan configmap/mymap-parent
 configmap "mymap-parent" deleted
 
 kubectl get configmap

content/en/docs/concepts/workloads/controllers/daemonset.md

@@ -185,7 +185,7 @@ You can modify the Pods that a DaemonSet creates.  However, Pods do not allow al
 fields to be updated.  Also, the DaemonSet controller will use the original template the next
 time a node (even with the same name) is created.
 
-You can delete a DaemonSet.  If you specify `--cascade=false` with `kubectl`, then the Pods
+You can delete a DaemonSet.  If you specify `--cascade=orphan` with `kubectl`, then the Pods
 will be left on the nodes.  If you subsequently create a new DaemonSet with the same selector,
 the new DaemonSet adopts the existing Pods. If any Pods need replacing the DaemonSet replaces
 them according to its `updateStrategy`.

content/en/docs/concepts/workloads/controllers/job.md

@@ -523,7 +523,7 @@ to keep running, but you want the rest of the Pods it creates
 to use a different pod template and for the Job to have a new name.
 You cannot update the Job because these fields are not updatable.
 Therefore, you delete Job `old` but _leave its pods
-running_, using `kubectl delete jobs/old --cascade=false`.
+running_, using `kubectl delete jobs/old --cascade=orphan`.
 Before deleting it, you make a note of what selector it uses:
 
 ```shell

content/en/docs/concepts/workloads/controllers/replicationcontroller.md

@@ -192,7 +192,7 @@ When using the REST API or Go client library, you need to do the steps explicitl
 
 You can delete a ReplicationController without affecting any of its pods.
 
-Using kubectl, specify the `--cascade=false` option to [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands#delete).
+Using kubectl, specify the `--cascade=orphan` option to [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands#delete).
 
 When using the REST API or Go client library, you can delete the ReplicationController object.
 

content/en/docs/tasks/administer-cluster/use-cascading-deletion.md

@@ -302,7 +302,7 @@ For details, read the [documentation for your Kubernetes version](/docs/home/sup
 Run the following command:
 
 ```shell
-kubectl delete deployment nginx-deployment --cascade=false
+kubectl delete deployment nginx-deployment --cascade=orphan
 ```
 
 **Using the Kubernetes API**