whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update GC cross-namespace note

Browse Source
This commit is contained in:
Jordan Liggitt
2020-11-17 17:38:06 -05:00
parent d249077048
commit 8d96fcb423
1 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/garbage-collection.md
+16 -5
View File
@@ -59,11 +59,22 @@ metadata:
``` ```
{{< note >}} {{< note >}}
Cross-namespace owner references are disallowed by design. This means: Cross-namespace owner references are disallowed by design.
1) Namespace-scoped dependents can only specify owners in the same namespace,
and owners that are cluster-scoped. Namespaced dependents can specify cluster-scoped or namespaced owners.
2) Cluster-scoped dependents can only specify cluster-scoped owners, but not A namespaced owner **must** exist in the same namespace as the dependent.
namespace-scoped owners. If it does not, the owner reference is treated as absent, and the dependent
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.
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
with a reason of `OwnerRefInvalidNamespace` and an `involvedObject` of the invalid dependent is reported.
You can check for that kind of Event by running
`kubectl get events -A --field-selector=reason=OwnerRefInvalidNamespace`.
{{< /note >}} {{< /note >}}
## Controlling how the garbage collector deletes dependents ## Controlling how the garbage collector deletes dependents