re-order sections (#6241)

For new readers without a detailed understanding of how deletion occurs, specifying foreground deletion first gives the needed context to understand what background deletion is eschewing.
This commit is contained in:
Tyler Kellen 2017-11-13 22:10:24 -05:00 committed by Steve Perry
parent 30ea773764
commit 3d5ca2d7ff
1 changed files with 6 additions and 6 deletions

View File

@ -70,12 +70,6 @@ deletion*. There are two modes of *cascading deletion*: *background* and *foreg
If you delete an object without deleting its dependents If you delete an object without deleting its dependents
automatically, the dependents are said to be *orphaned*. automatically, the dependents are said to be *orphaned*.
### Background cascading deletion
In *background cascading deletion*, Kubernetes deletes the owner object
immediately and the garbage collector then deletes the dependents in
the background.
### Foreground cascading deletion ### Foreground cascading deletion
In *foreground cascading deletion*, the root object first In *foreground cascading deletion*, the root object first
@ -100,6 +94,12 @@ unauthorized dependents cannot delay deletion of an owner object.
If an object's `ownerReferences` field is set by a controller (such as Deployment or ReplicaSet), If an object's `ownerReferences` field is set by a controller (such as Deployment or ReplicaSet),
blockOwnerDeletion is set automatically and you do not need to manually modify this field. blockOwnerDeletion is set automatically and you do not need to manually modify this field.
### Background cascading deletion
In *background cascading deletion*, Kubernetes deletes the owner object
immediately and the garbage collector then deletes the dependents in
the background.
### Setting the cascading deletion policy ### Setting the cascading deletion policy
To control the cascading deletion policy, set the `deleteOptions.propagationPolicy` To control the cascading deletion policy, set the `deleteOptions.propagationPolicy`