huawei-cloud-cce-network-failure-diagnoser

Diagnose Huawei Cloud CCE network 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-network-failure-diagnoser-pancake0001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: huawei-cloud-cce-network-failure-diagnoser
Source: https://github.com/pancake0001/huawei-cloudnative-skills/tree/main/releases/container/cce/huawei-cloud-cce-network-failure-diagnoser
Command: npx skills add https://github.com/pancake0001/huawei-cloudnative-skills --skill huawei-cloud-cce-network-failure-diagnoser-pancake0001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It pinpoints the root cause of Kubernetes network failures on Huawei Cloud CCE—such as unreachable Services, DNS errors, Ingress 502/504, NetworkPolicy blocks, and ELB/EIP/NAT issues—by correlating cluster and cloud-network evidence into a ranked diagnosis report. ## Core Features & Use Cases - Layered Evidence Collection: Gathers read-only evidence across nodes/CNI, DNS/CoreDNS, Services and EndpointSlices, NetworkPolicies, Ingress, and cloud ELB/VPC/EIP/NAT layers via hcloud and the kubectl-cce plugin. - Ranked Cause Analysis: Ranks likely causes (e.g., ServiceNoReadyEndpoint, NetworkPolicyBlocked, ELBBackendUnhealthy) with direct evidence, ruled-out layers, and verification gaps. - Structured Reports: Produces a Markdown report with executive summary, network path funnel, object snapshots, and safe handoff recommendations—no mutating commands are ever run. - Use Case: When users report that an Ingress returns 502, run this skill to check EndpointSlice readiness, Ingress backend mapping, and ELB member health, then receive a ranked root-cause report with recommended next steps. ## Quick Start Ask the assistant to diagnose why the Service 'api' in namespace 'default' of CCE cluster <cluster-id> in region cn-north-4 is unreachable.

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

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

FAQPage Schema
How do I diagnose an unreachable Service in Huawei Cloud CCE?▼

Provide the region, cluster_id, namespace, and Service name. The skill checks the Service selector, Endpoints, EndpointSlices, and backend Pod readiness via kubectl cce, then ranks causes such as selector mismatch or no ready endpoints with supporting evidence.

How do I troubleshoot Ingress 502 or 504 errors on CCE?▼

The skill inspects Ingress rules, backend Service/port mapping, EndpointSlice readiness, and optionally ELB listener, pool, member, and health monitor state through read-only hcloud commands. It reports whether the failure is in Kubernetes routing or the cloud load balancer layer.

What tools and permissions does CCE network diagnosis require?▼

It requires the hcloud CLI, kubectl with the kubectl-cce plugin, and read-only access. IAM needs CCE cluster read plus optional ELB/VPC/EIP/NAT list permissions; Kubernetes RBAC needs get/list on Services, Endpoints, EndpointSlices, Ingresses, NetworkPolicies, Pods, and Events.

Can this skill fix NetworkPolicy or ELB configuration problems automatically?▼

No. The skill is strictly read-only and never runs apply, create, patch, delete, scale, or hcloud write operations. It recommends candidate fixes with expected impact and hands changes off to an approved remediation workflow after user confirmation.

Why does kubectl cce fail with an x509 certificate error?▼

An x509 validation error means the upstream TLS certificate could not be verified. Retry the same command with --cce-insecure-upstream-tls=true placed immediately after cce, and use this option only when that specific TLS error occurs.

What happens if I provide a cluster name instead of a cluster UUID?▼

The skill lists CCE clusters in the given region and performs an exact name match. If exactly one cluster matches, it converts the name to its UUID and verifies it; if there is no match or multiple matches, it stops and asks you for the correct UUID.