Merge pull request #48108 from qlijin/garbage-collection.md

[zh-cn] sync garbage-collection.md

Author: k8s-ci-robot

content/zh-cn/docs/concepts/architecture/garbage-collection.md

@@ -187,16 +187,20 @@ to learn more.
 ### Background cascading deletion {#background-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
+object immediately and the garbage collector controller (custom or default)
+cleans up the dependent objects in the background.
+If a finalizer exists, it ensures that objects are not deleted until all necessary clean-up tasks are completed.
+By default, Kubernetes uses background cascading deletion unless
 you manually use foreground deletion or choose to orphan the dependent objects.
 
 See [Use background cascading deletion](/docs/tasks/administer-cluster/use-cascading-deletion/#use-background-cascading-deletion)
 to learn more.
 -->
 ### 后台级联删除 {#background-deletion}
 
-在后台级联删除过程中，Kubernetes 服务器立即删除属主对象，控制器在后台清理所有依赖对象。
+在后台级联删除过程中，Kubernetes 服务器立即删除属主对象，
+而垃圾收集控制器（无论是自定义的还是默认的）在后台清理所有依赖对象。
+如果存在 Finalizers，它会确保所有必要的清理任务完成后对象才被删除。
 默认情况下，Kubernetes 使用后台级联删除方案，除非你手动设置了要使用前台删除，
 或者选择遗弃依赖对象。