[zh] Resync concepts section (13)

content/zh/docs/concepts/overview/working-with-objects/names.md

@@ -36,6 +36,15 @@ For non-unique user-provided attributes, Kubernetes provides [labels](/docs/user
 
 {{< glossary_definition term_id="name" length="all" >}}
 
+{{< note >}}
+<!--
+In cases when objects represent a physical entity, like a Node representing a physical host, when the host is re-created under the same name without deleting and re-creating the Node, Kubernetes treats the new host as the old one, which may lead to inconsistencies.
+-->
+当对象所代表的是一个物理实体（例如代表一台物理主机的 Node）时，
+如果在 Node 对象未被删除并重建的条件下，创新创建了同名的物理主机，
+则 Kubernetes 会将新的主机看作是老的主机，这可能会带来某种不一致性。
+{{< /note >}}
+
 <!--
 Below are three types of commonly used name constraints for resources.
 -->