What problem does it solve? Kubernetes Events in Huawei Cloud CCE clusters are scattered across the live API server and historical LTS log streams, making it hard to spot repeated warnings like FailedScheduling, ImagePullBackOff, or FailedMount during an incident. This Skill unifies current and historical Event queries, aggregates them by reason, namespace, and affected resource, and produces evidence ready for diagnosis handoff. ## Core Features & Use Cases - Current Event Queries: Read Warning or Normal Events cluster-wide or per namespace through external kubeconfig access with automatic fallback to the kubectl cce plugin. - Historical LTS Queries: Retrieve time-bounded historical Events from LTS using the default-event LogConfig, with server-side keyword filtering and pagination. - Event Aggregation and Analysis: Group Events by reason, type, namespace, and involved object, surface repeated patterns, and optionally check the current status of referenced resources. - Use Case: During an incident, ask for Warning Events in a namespace, then analyze the results to find that FailedScheduling dominates, and hand the evidence off to a workload or node diagnosis skill. ## Quick Start Ask the assistant to list the Warning Kubernetes Events for your CCE cluster by providing the region and cluster ID, for example: show the recent Warning events for cluster <cluster-id> in region <region>.