huawei-cloud-cce-workload-failure-diagnoser

Diagnose Huawei Cloud CCE workload rollout and availability failures with read-only kubectl evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a Deployment, StatefulSet, or DaemonSet in a Huawei Cloud CCE cluster gets stuck during rollout or loses available replicas, engineers must manually correlate workload status, ReplicaSets, Pods, Events, and logs to find the root cause. This Skill automates that read-only evidence collection and ranks the most likely causes with a structured rollout funnel. ## Core Features & Use Cases - Rollout Funnel Analysis: Walks the chain from control-plane generation observation through new ReplicaSet creation, Pod scheduling, readiness, and availability to pinpoint the first failing layer. - Evidence-Based Cause Ranking: Maps symptoms like ProgressDeadlineExceeded, ImagePullBackOff, CrashLoopBackOff, OOMKilled, FailedScheduling, probe failures, and FailedMount to labeled causes with confidence scores and cited evidence. - Safe Read-Only Diagnosis: Uses hcloud CCE commands for cluster discovery and the kubectl-cce plugin for Kubernetes reads, never mutating resources, and hands off remediation to dedicated skills. - Use Case: A Deployment update stalls with new Pods stuck in Pending. The Skill verifies cluster access, inspects the Deployment and its ReplicaSets, filters Events to the workload, identifies FailedScheduling due to node taints, and recommends handing off to the node failure diagnoser. ## Quick Start Ask the AI to diagnose why Deployment 'api-server' in namespace 'prod' of CCE cluster <cluster-id> in region cn-north-4 is not rolling out, and provide a ranked cause report.

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

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

FAQPage Schema
How do I diagnose a stuck Deployment rollout in Huawei Cloud CCE?▼

Provide the region, cluster ID, namespace, and Deployment name. The Skill verifies access with hcloud and kubectl-cce, inspects the Deployment, its ReplicaSets, Pods, and Events, then builds a rollout funnel showing the first failing layer with ranked causes.

What Kubernetes workload types does this CCE diagnosis support?▼

It supports Deployment, StatefulSet, and DaemonSet workloads. For each type it compares generation, updated, ready, and available replica counters, plus strategy-specific fields like StatefulSet partition and DaemonSet desiredNumberScheduled.

Can this skill fix or roll back a failed CCE workload?▼

No. It is strictly read-only and never runs apply, delete, scale, rollout undo, cordon, or drain commands. Remediation actions are only proposed as recommendations and handed off to the auto-remediation-runner skill.

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

The kubectl-cce plugin may hit upstream TLS validation failures against the CCE API Gateway. Retry the same command with --cce-insecure-upstream-tls=true placed immediately after cce, and use this flag only when that specific error occurs.

What credentials and tools are required for CCE workload diagnosis?▼

You need the hcloud KooCLI binary, kubectl with the kubectl-cce plugin, and Huawei Cloud AK/SK credentials configured via environment variables or CLI flags. The account needs IAM permission to list CCE clusters and RBAC read access to the target namespace.

What happens if my cluster_id is a name instead of a UUID?▼

The Skill lists CCE clusters with hcloud and performs an exact name match, converting it to a UUID only when exactly one cluster matches. If there is no match or multiple matches, it stops and asks you to provide the correct UUID rather than guessing.