Container Compute Service:kube-eventer

Component overview

kube-eventer consists of two sub-components:

• kube-event-init: Runs once during installation to initialize SLS Event Center instance resources. This gives kube-eventer the storage and analysis backend it needs from the moment your cluster starts generating events.

• kube-eventer: Continuously collects and reports all cluster events to the SLS Event Center. Events are retained for 90 days and searchable through dashboards, alarms, and a full-text search interface. To route events to additional systems, configure kube-eventer to forward to DingTalk or EventBridge. For the full list of supported outputs and configuration details, see the kube-eventer GitHub repository.

Use cases

• Store and search all cluster events: All events are sent to SLS Event Center automatically, with 90 days of persistent storage and built-in search and analysis.

• Detect node anomalies: Use SLS dashboards and alarms to detect node anomalies, including anomalies on virtual nodes in ACS clusters.

• Forward events to other systems: Route cluster events to DingTalk for team notifications or to EventBridge for downstream automation.

• Extend node monitoring: Add custom node monitoring plugins to expand the scope of anomaly detection beyond the built-in coverage.

Change records