diff --git a/content/zh/docs/concepts/overview/working-with-objects/finalizers.md b/content/zh/docs/concepts/overview/working-with-objects/finalizers.md
new file mode 100644
index 0000000000000..296f491bddbe2
--- /dev/null
+++ b/content/zh/docs/concepts/overview/working-with-objects/finalizers.md
@@ -0,0 +1,142 @@
+---
+title: Finalizers
+content_type: concept
+weight: 60
+---
+
+<!-- overview -->
+
+{{<glossary_definition term_id="finalizer" length="long">}}
+
+<!--
+You can use finalizers to control {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}
+of resources by alerting {{<glossary_tooltip text="controllers" term_id="controller">}} to perform specific cleanup tasks before
+deleting the target resource. 
+-->
+你可以通过使用 Finalizers 提醒{{<glossary_tooltip text="控制器" term_id="controller">}}在删除目标资源前执行特定的清理任务，来控制资源的{{<glossary_tooltip text="垃圾回收" term_id="garbage-collection">}}。
+
+<!--
+Finalizers don't usually specify the code to execute. Instead, they are
+typically lists of keys on a specific resource similar to annotations.
+Kubernetes specifies some finalizers automatically, but you can also specify
+your own.
+-->
+Finalizers 通常不指定要执行的代码。
+相反，它们通常是特定资源上的键的列表，类似于注解。
+Kubernetes 自动指定了一些 Finalizers，但你也可以指定你自己的。
+
+<!--
+## How finalizers work
+
+When you create a resource using a manifest file, you can specify finalizers in
+the `metadata.finalizers` field. When you attempt to delete the resource, the
+controller that manages it notices the values in the `finalizers` field and does
+the following: 
+
+  * Modifies the object to add a `metadata.deletionTimestamp` field with the
+    time you started the deletion.
+  * Marks the object as read-only until its `metadata.finalizers` field is empty.
+-->
+## Finalizers 如何工作   {#how-finalizers-work}
+当你使用清单文件创建资源时，你可以在 `metadata.finalizers` 字段指定 Finalizers。
+当你试图删除该资源时，管理该资源的控制器会注意到 `finalizers` 字段中的值，
+并进行以下操作：
+
+  * 修改对象，将你开始执行删除的时间添加到 `metadata.deletionTimestamp` 字段。
+  * 将该对象标记为只读，直到其 `metadata.finalizers` 字段为空。
+
+
+<!--
+The controller then attempts to satisfy the requirements of the finalizers
+specified for that resource. Each time a finalizer condition is satisfied, the
+controller removes that key from the resource's `finalizers` field. When the
+field is empty, garbage collection continues. You can also use finalizers to
+prevent deletion of unmanaged resources.
+-->
+然后，控制器试图满足资源的 Finalizers 的条件。
+每当一个 Finalizer 的条件被满足时，控制器就会从资源的 `finalizers` 字段中删除该键。
+当该字段为空时，垃圾回收继续进行。
+你也可以使用 Finalizers 来阻止删除未被管理的资源。
+
+<!--
+A common example of a finalizer is `kubernetes.io/pv-protection`, which prevents
+accidental deletion of `PersistentVolume` objects. When a `PersistentVolume`
+object is in use by a Pod, Kubernetes adds the `pv-protection` finalizer. If you
+try to delete the `PersistentVolume`, it enters a `Terminating` status, but the
+controller can't delete it because the finalizer exists. When the Pod stops
+using the `PersistentVolume`, Kubernetes clears the `pv-protection` finalizer,
+and the controller deletes the volume.
+-->
+一个常见的 Finalizer 的例子是 `kubernetes.io/pv-protection`，
+它用来防止意外删除 `PersistentVolume` 对象。
+当一个 `PersistentVolume` 对象被 Pod 使用时，
+Kubernetes 会添加 `pv-protection` Finalizer。
+如果你试图删除 `PersistentVolume`，它将进入 `Terminating` 状态，
+但是控制器因为该 Finalizer 存在而无法删除该资源。
+当 Pod 停止使用 `PersistentVolume` 时，Kubernetes 清除 `pv-protection` Finalizer，控制器就会删除该卷。
+
+<!--
+## Owner references, labels, and finalizers {#owners-labels-finalizers}
+
+Like {{<glossary_tooltip text="labels" term_id="label">}}, [owner references](/concepts/overview/working-with-objects/owners-dependents/)
+describe the relationships between objects in Kubernetes, but are used for a
+different purpose. When a
+{{<glossary_tooltip text="controller" term_id="controller">}} manages objects
+like Pods, it uses labels to track changes to groups of related objects. For
+example, when a {{<glossary_tooltip text="Job" term_id="job">}} creates one or
+more Pods, the Job controller applies labels to those pods and tracks changes to
+any Pods in the cluster with the same label.
+-->
+## 属主引用、标签和 Finalizers {#owners-labels-finalizers}
+与{{<glossary_tooltip text="标签" term_id="label">}}类似，
+[属主引用](/zh/concepts/overview/working-with-objects/owners-dependents/)
+描述了 Kubernetes 中对象之间的关系，但它们作用不同。
+当一个{{<glossary_tooltip text="控制器" term_id="controller">}}
+管理类似于 Pod 的对象时，它使用标签来跟踪相关对象组的变化。
+例如，当 {{<glossary_tooltip text="Job" term_id="job">}} 创建一个或多个 Pod 时，Job 控制器会给这些 Pod 应用上标签，
+并跟踪集群中的具有相同标签的 Pod 的变化。
+
+<!--
+The Job controller also adds *owner references* to those Pods, pointing at the
+Job that created the Pods. If you delete the Job while these Pods are running,
+Kubernetes uses the owner references (not labels) to determine which Pods in the
+cluster need cleanup.
+
+Kubernetes also processes finalizers when it identifies owner references on a
+resource targeted for deletion. 
+
+In some situations, finalizers can block the deletion of dependent objects,
+which can cause the targeted owner object to remain in a read-only state for
+longer than expected without being fully deleted. In these situations, you
+should check finalizers and owner references on the target owner and dependent
+objects to troubleshoot the cause. 
+-->
+Job 控制器还为这些 Pod 添加了*属主引用*，指向创建 Pod 的 Job。
+如果你在这些 Pod 运行的时候删除了 Job，
+Kubernetes 会使用属主引用（而不是标签）来确定集群中哪些 Pod 需要清理。
+
+当 Kubernetes 识别到要删除的资源上的属主引用时，它也会处理 Finalizers。
+
+在某些情况下，Finalizers 会阻止依赖对象的删除，
+这可能导致目标属主对象，保持在只读状态的时间比预期的长，且没有被完全删除。
+在这些情况下，你应该检查目标属主和附属对象上的 Finalizers 和所有者引用，来排查原因。
+
+{{<note>}}
+<!--
+In cases where objects are stuck in a deleting state, try to avoid manually
+removing finalizers to allow deletion to continue. Finalizers are usually added
+to resources for a reason, so forcefully removing them can lead to issues in
+your cluster. 
+-->
+在对象卡在删除状态的情况下，尽量避免手动移除 Finalizers 以允许继续删除操作。
+Finalizers 通常因为特殊原因被添加到资源上，所以强行删除它们会导致集群出现问题。
+{{</note>}}
+
+
+## {{% heading "whatsnext" %}}
+
+<!--
+* Read [Using Finalizers to Control Deletion](/blog/2021/05/14/using-finalizers-to-control-deletion/)
+  on the Kubernetes blog.
+-->
+* 阅读 Kubernetes 博客的[使用 Finalizers 控制删除](/blog/2021/05/14/using-finalizers-to-control-deletion/)。
diff --git a/content/zh/docs/reference/glossary/finalizer.md b/content/zh/docs/reference/glossary/finalizer.md
new file mode 100644
index 0000000000000..aff1b7bd1f529
--- /dev/null
+++ b/content/zh/docs/reference/glossary/finalizer.md
@@ -0,0 +1,64 @@
+---
+title: Finalizer
+id: finalizer
+date: 2021-07-07
+full_link: /zh/docs/concepts/overview/working-with-objects/finalizers/
+short_description: >
+  一个命名空间范围的键，告诉 Kubernetes 等到特定的条件被满足后，
+  再完全删除被标记为删除的资源。
+aka: 
+tags:
+- fundamental
+- operation
+---
+
+<!--
+---
+title: Finalizer
+id: finalizer
+date: 2021-07-07
+full_link: /zh/docs/concepts/overview/working-with-objects/finalizers/
+short_description: >
+  A namespaced key that tells Kubernetes to wait until specific conditions are met
+  before it fully deletes an object marked for deletion.
+aka: 
+tags:
+- fundamental
+- operation
+-->
+
+
+<!--
+Finalizers are namespaced keys that tell Kubernetes to wait until specific
+conditions are met before it fully deletes resources marked for deletion.
+Finalizers alert {{<glossary_tooltip text="controllers" term_id="controller">}}
+to clean up resources the deleted object owned.
+-->
+Finalizer 是命名空间范围的键，告诉 Kubernetes 等到特定的条件被满足后，
+再完全删除被标记为删除的资源。
+Finalizer 提醒{{<glossary_tooltip text="控制器" term_id="controller">}}清理被删除的对象拥有的资源。
+<!--more-->
+
+<!--
+When you tell Kubernetes to delete an object that has finalizers specified for
+it, the Kubernetes API marks the object for deletion, putting it into a
+read-only state. The target object remains in a terminating state while the
+control plane, or other components, take the actions defined by the finalizers.
+After these actions are complete, the controller removes the relevant finalizers
+from the target object. When the `metadata.finalizers` field is empty,
+Kubernetes considers the deletion complete.
+-->
+当你告诉 Kubernetes 删除一个指定了 Finalizer 的对象时，
+Kubernetes API 会将该对象标记为删除，使其进入只读状态。
+此时控制平面或其他组件会采取 Finalizer 所定义的行动，
+而目标对象仍然处于终止中（Terminating）的状态。
+这些行动完成后，控制器会删除目标对象相关的 Finalizer。
+当 `metadata.finalizers` 字段为空时，Kubernetes 认为删除已完成。
+
+<!--
+You can use finalizers to control {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}
+of resources. For example, you can define a finalizer to clean up related resources or
+infrastructure before the controller deletes the target resource.
+-->
+你可以使用 Finalizer 控制资源的{{<glossary_tooltip text="垃圾回收" term_id="garbage-collection">}}。
+例如，你可以定义一个 Finalizer，在删除目标资源前清理相关资源或基础设施。
\ No newline at end of file