Merge pull request #31980 from tengqm/zh-glossary-event

[zh] Add glossary Event

content/zh/docs/reference/glossary/event.md

@@ -0,0 +1,56 @@
+---
+title: 事件（Event）
+id: event
+date: 2022-01-16
+full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/
+short_description: >
+   对集群中周处发生的事件的报告。通常用来表述系统中某种状态变更。
+aka: 
+tags:
+- core-object
+- fundamental
+---
+
+<!--
+title: Event
+id: event
+date: 2022-01-16
+full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/
+short_description: >
+   A report of an event somewhere in the cluster. It generally denotes some state change in the system.
+aka: 
+tags:
+- core-object
+- fundamental
+-->
+
+<!--
+Each Event is a report of an event somewhere in the {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
+It generally denotes some state change in the system.
+-->
+每个 Event 是{{< glossary_tooltip text="集群" term_id="cluster" >}}中某处发生的事件的报告。
+它通常用来表述系统中的某种状态变化。
+
+<!--more-->
+
+<!--
+Events have a limited retention time and triggers and messages may evolve with time. 
+Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger, 
+or the continued existence of events with that reason. 
+-->
+事件的保留时间有限，随着时间推进，其触发方式和消息都可能发生变化。
+事件用户不应该对带有给定原因（反映下层触发源）的时间特征有任何依赖，
+也不要寄希望于对应该原因的事件会一直存在。
+
+<!--
+Events should be treated as informative, best-effort, supplemental data.
+-->
+事件应该被视为一种告知性质的、尽力而为的、补充性质的数据。
+
+<!--
+In Kubernetes, [auditing](/docs/tasks/debug-application-cluster/audit/) generates a different kind of
+Event record (API group `audit.k8s.io`).
+-->
+在 Kubernetes 中，[审计](/zh/docs/tasks/debug-application-cluster/audit/)
+机制会生成一种不同种类的 Event 记录（API 组为 `audit.k8s.io`）。
+