From c2a5b2b39abf552a1dc87ecb119d55f1a9a58370 Mon Sep 17 00:00:00 2001 From: Aditya Soni <39667294+theadisoni@users.noreply.github.com> Date: Tue, 15 Jun 2021 15:04:04 +0530 Subject: [PATCH] Update garbage-collection.md --- .../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 1b1de5d0a4..3e8bf31c1c 100644 --- a/content/en/docs/concepts/workloads/controllers/garbage-collection.md +++ b/content/en/docs/concepts/workloads/controllers/garbage-collection.md @@ -68,7 +68,7 @@ is subject to deletion once all owners are verified absent. Cluster-scoped dependents can only specify cluster-scoped owners. In v1.20+, if a cluster-scoped dependent specifies a namespaced kind as an owner, -it is treated as having an unresolveable owner reference, and is not able to be garbage collected. +it is treated as having an unresolvable owner reference, and is not able to be garbage collected. In v1.20+, if the garbage collector detects an invalid cross-namespace `ownerReference`, or a cluster-scoped dependent with an `ownerReference` referencing a namespaced kind, a warning Event