Garbage Collection: Background deletion explanation is hard to understand

[guettli]

Page: https://kubernetes.io/docs/concepts/architecture/garbage-collection/#background-deletion

Background cascading deletion

In background cascading deletion, the Kubernetes API server deletes the owner object immediately and the controller cleans up the dependent objects in the background. By default, Kubernetes uses background cascading deletion unless you manually use foreground deletion or choose to orphan the dependent objects.

I have problems understanding this text.

First: If I read that, then I think Finalizers seem to get ignored if you use background-deletion. But I don't think so.

Second: "... the controller cleans up the dependent objects". What is "the controller" here? If I have a custom controller for my CRDs. Is that meant with "the controller"?

[steve-hardman]

/language en

[steve-hardman]

I also agree there is room of improving the existing content in the page.

[ayushpatil2122]

@guettli
Finalizers are not ignored during background deletion. The owner object is marked for deletion, but finalizers still execute before fully deleting it.

The controller refers to the Kubernetes controller that manages the lifecycle of resources, which could include your custom controller for CRDs. It's responsible for cleaning up dependent objects in the background.

[sftim]

/retitle Garbage Collection: Background deletion explanation is hard to understand

[katcosgrove]

/triage accepted
/priority backlog

[Nishant-k-sagar]

If there is still room to work on this issue, I would like to work on this. @guettli
@ayushpatil2122
Kindly /assign this to me