huawei-cloud-cce-dependency-impact-analyzer

What problem does it solve? When a Huawei Cloud CCE workload or Pod becomes unhealthy, teams struggle to determine which Services, Ingresses, EndpointSlices, Nodes, and upstream/downstream paths are affected. This Skill maps the dependency topology and estimates the blast radius of an incident, separating possible propagation paths from observed traffic impact. ## Core Features & Use Cases - Topology Mapping: Collects Deployments, StatefulSets, DaemonSets, Pods, Services, Ingresses, Endpoints, EndpointSlices, and Nodes through read-only hcloud and kubectl-cce queries. - Propagation Path Analysis: Models external paths (Ingress -> Service -> EndpointSlice -> Pods -> Nodes) and internal paths (Service DNS -> Endpoints -> Pods -> Nodes) with confidence scoring. - Structured Impact Report: Produces a Markdown report with Summary, Impact Paths, Next Actions, Evidence, Confidence Limits, and Appendix sections, plus handoff to focused diagnoser skills. - Use Case: After a Deployment rollout causes 502 errors, run this Skill to identify which Ingress entrypoints and Services route to the failing Pods, whether impact is Node- or zone-concentrated, and which diagnoser skill should investigate the root cause. ## Quick Start Ask the assistant to analyze which Services, Ingresses, and Nodes are affected by the failing workload in your CCE cluster by providing the region, project ID, cluster ID, namespace, and target workload name.