huawei-cloud-cce-node-failure-diagnoser

Diagnose Huawei Cloud CCE node failures using hcloud and read-only kubectl-cce evidence.

1|Updated May 27, 2026
One-click install
npx skills add https://github.com/pancake0001/huawei-cloudnative-skills --skill huawei-cloud-cce-node-failure-diagnoser-pancake0001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: huawei-cloud-cce-node-failure-diagnoser
Source: https://github.com/pancake0001/huawei-cloudnative-skills/tree/main/releases/container/cce/huawei-cloud-cce-node-failure-diagnoser
Command: npx skills add https://github.com/pancake0001/huawei-cloudnative-skills --skill huawei-cloud-cce-node-failure-diagnoser-pancake0001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a CCE node goes NotReady, shows pressure conditions, or disrupts workloads, engineers must manually correlate cluster metadata, node conditions, kube-node-lease freshness, Events, and Pod impact across multiple tools. This Skill automates that read-only evidence collection and produces a ranked root-cause diagnosis report. ## Core Features & Use Cases - Node liveness and condition analysis: Inspects Ready status, kube-node-lease freshness, DiskPressure, MemoryPressure, PIDPressure, NetworkUnavailable, and kubelet/CRI/CNI problem signals. - Workload impact assessment: Lists Pods on the node, classifies evicted, failed, and restart-heavy Pods, and detects node-local patterns like FailedCreatePodSandBox. - Ranked cause report: Outputs an executive summary, top causes with evidence and ruled-out alternatives, safe next steps, and remediation handoff recommendations. - Use Case: A node shows Ready=Unknown and Pods are stuck in ContainerStatusUnknown. The Skill verifies the stale lease, reviews node Events, confirms control-plane heartbeat loss, and recommends handoff to the auto-remediation runner. ## Quick Start Diagnose why node 192.168.0.10 in my CCE cluster is NotReady in region cn-north-4 for cluster ID <cluster-id>.

Frequently Asked Questions about huawei-cloud-cce-node-failure-diagnoser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a CCE node that is NotReady?▼

Provide the region, cluster ID, and node name or IP. The Skill verifies the cluster with hcloud, then uses kubectl-cce to inspect node conditions, kube-node-lease freshness, Events, and Pods on the node, producing a ranked cause report.

What does Ready=Unknown with a stale kube-node-lease mean?▼

It means the control plane has lost heartbeat visibility into the node, labeled ControlPlaneDisconnected. The cause may be kubelet, node network, runtime, or maintenance, so the Skill reports the broader conclusion before listing node-side checks.

Can this Skill cordon, drain, or reboot a faulty node?▼

No. The Skill is strictly read-only and never runs cordon, drain, taint, reboot, delete, or scale operations. It recommends candidate fixes and hands off mutations to the auto-remediation runner after user confirmation.

What prerequisites are required for kubectl-cce node diagnosis?▼

You need hcloud, kubectl with the kubectl-cce plugin, valid credentials, and IAM plus Kubernetes RBAC read access to nodes, leases, events, pods, and pod logs. Missing permissions are reported as verification gaps.

Why does kubectl top node fail during diagnosis?▼

The top command fails when metrics-server is unavailable in the cluster. The Skill records this as a verification gap and relies on node conditions, Events, and eviction messages instead of inventing resource trends.