Anubhav Vardhan
34ded72a7f
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 <tim@scalefactory.com>
946 B
946 B
title, id, date, full_link, short_description, aka, tags
| title | id | date | full_link | short_description | aka | tags | ||
|---|---|---|---|---|---|---|---|---|
| Event | event | 2022-01-16 | /docs/reference/kubernetes-api/cluster-resources/event-v1/ | A report of an event somewhere in the cluster. It generally denotes some state change in the system. |
|
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 generates a different kind of
Event record (API group audit.k8s.io).