From 34ded72a7fc41688901e2f5ebe6f449fca349869 Mon Sep 17 00:00:00 2001 From: Anubhav Vardhan Date: Sun, 16 Jan 2022 11:45:36 +0530 Subject: [PATCH] Update event.md Update content/en/docs/reference/glossary/event.md Create event.md Create event.md Update event.md Add full link Update content/en/docs/reference/glossary/event.md Update content/en/docs/reference/glossary/event.md Update content/en/docs/reference/glossary/event.md Update event.md Update event.md Co-Authored-By: Tim Bannister --- content/en/docs/reference/glossary/event.md | 25 +++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 content/en/docs/reference/glossary/event.md diff --git a/content/en/docs/reference/glossary/event.md b/content/en/docs/reference/glossary/event.md new file mode 100644 index 0000000000..e534a91527 --- /dev/null +++ b/content/en/docs/reference/glossary/event.md @@ -0,0 +1,25 @@ +--- +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. + + +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`).