From 761d210f63056c7e172e970b9c13dce512c68efd Mon Sep 17 00:00:00 2001 From: Jiacheng Xu Date: Wed, 24 Jul 2019 04:36:14 +0200 Subject: [PATCH] Update garbage-collection.md (#15495) --- .../docs/concepts/workloads/controllers/garbage-collection.md | 2 +- 1 file changed, 1 insertion(+), 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 5c23a92910..45303b66e8 100644 --- a/content/en/docs/concepts/workloads/controllers/garbage-collection.md +++ b/content/en/docs/concepts/workloads/controllers/garbage-collection.md @@ -93,7 +93,7 @@ collector deletes the object's dependents. Once the garbage collector has delete the owner object. Note that in the "foregroundDeletion", only dependents with -`ownerReference.blockOwnerDeletion` block the deletion of the owner object. +`ownerReference.blockOwnerDeletion=true` block the deletion of the owner object. Kubernetes version 1.7 added an [admission controller](/docs/reference/access-authn-authz/admission-controllers/#ownerreferencespermissionenforcement) that controls user access to set `blockOwnerDeletion` to true based on delete permissions on the owner object, so that unauthorized dependents cannot delay deletion of an owner object.