skills.rest
pancake0001
pancake0001COMMUNITY
Explore all skills by this author →
GitHub

huawei-cloud-cce-daily-cluster-inspector

Inspect Huawei Cloud CCE cluster health with quick checks and escalated deep diagnosis.

1|Updated May 27, 2026
Search Tags:#kubernetes#health check#huawei cloud#cluster inspection#daily operations#cce#aom
One-click install
npx skills add https://github.com/pancake0001/huawei-cloudnative-skills --skill huawei-cloud-cce-daily-cluster-inspector-pancake0001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: huawei-cloud-cce-daily-cluster-inspector
Source: https://github.com/pancake0001/huawei-cloudnative-skills/tree/main/releases/container/cce-unscheduled/huawei-cloud-cce-daily-cluster-inspector
Command: npx skills add https://github.com/pancake0001/huawei-cloudnative-skills --skill huawei-cloud-cce-daily-cluster-inspector-pancake0001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires huaweicloudsdkcce, huaweicloudsdkcore, huaweicloudsdkaom, huaweicloudsdkecs, huaweicloudsdkvpc, huaweicloudsdkces, huaweicloudsdkevs, huaweicloudsdkeip, huaweicloudsdkelb, huaweicloudsdkiam, kubernetes, matplotlib, numpy, requests, pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Running full cluster diagnostics on every health check wastes time and resources, while skipping checks risks missing critical issues. This Skill performs periodic, read-only health inspections of Huawei Cloud CCE clusters using a quick-check-first strategy, escalating to deep diagnosis only when anomalies appear. ## Core Features & Use Cases - Quick Health Checks: Run lightweight cluster inspections via huawei_cce_quick_check or huawei_cce_auto_inspection and output a heartbeat summary when the cluster is healthy. - Escalated Deep Diagnosis: When anomalies are found, run parallel or domain-specific inspections across Pod, Node, Event, AOM alarm, and ELB dimensions, then classify risks as P0/P1/P2. - Read-Only Reporting: Export formal inspection reports with huawei_export_inspection_report and hand off actionable items to the auto-remediation skill — this Skill never mutates cluster state. - Use Case: An operations engineer schedules a daily CCE inspection. The Skill runs a quick check, detects abnormal Pods, escalates to Pod and Node inspections, and produces a P0/P1/P2 risk report with remediation handoff recommendations. ## Quick Start Ask the AI to run a daily health inspection on your Huawei Cloud CCE cluster by providing the region and cluster ID, for example: run a quick health check on my CCE cluster in cn-north-4 and summarize any risks.

Frequently Asked Questions about huawei-cloud-cce-daily-cluster-inspector

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

FAQPage Schema
How do I run a daily health check on a Huawei Cloud CCE cluster?▼

Provide the region and cluster_id, then run huawei_cce_quick_check or huawei_cce_auto_inspection for a lightweight first pass. If anomalies are found, escalate to huawei_cce_deep_diagnosis or parallel inspection actions grouped by Pod, Node, Event, AOM, and ELB.

What is the difference between quick check and deep diagnosis for CCE inspection?▼

Quick check (huawei_cce_quick_check) is a lightweight health summary intended for every inspection cycle. Deep diagnosis (huawei_cce_deep_diagnosis) runs heavier multi-domain analysis and should only be triggered when the quick check detects anomalies.

Can this inspection skill restart nodes or scale workloads automatically?▼

No. The skill operates under R1 read-only constraints and prohibits scaling, deletion, drain, reboot, hibernate, and awake actions. Detected risks produce recommendations that are handed off to the huawei-cloud-cce-auto-remediation-runner skill for confirmed execution.

What IAM permissions are required for CCE cluster inspection?▼

You need cce:cluster:get, cce:cluster:createCert, cce:node:list, aom:instance:list, aom:metricsData:get, and aom:alarm:get permissions. Credentials are supplied via HUAWEI_AK, HUAWEI_SK, and HUAWEI_REGION environment variables.

Why does the CCE inspection return empty metrics data?▼

Empty metrics usually mean no AOM Prometheus instance exists for the cluster or the aom:instance:list permission is missing. Verify the AOM instance is bound to the cluster and that the IAM policy grants AOM read access.

How do I get a formal inspection report from the cluster health check?▼

After running inspections, call huawei_export_inspection_report with the region and cluster_id to generate a persistent report. When using parallel inspection, call huawei_aggregate_inspection_results first to consolidate results.

Related Skills

Explore More Software Engineering Skills→
paulanunes85paulanunes85
1

kubectl-cli

Execute kubectl commands to diagnose and fix Kubernetes cluster issues in AKS and ARO environments.

Community
Intermediate
incidentfoxincidentfox
654

remediation

Execute Kubernetes pod restarts, deployment scaling, and rollbacks with dry-run checks.

Official
Advanced
unblockedunblocked
13

headless-validate-bug

Validate bug reports from Jira, Linear, and GitHub Issues.

Official
Advanced
DynatraceDynatrace
120

dt-obs-kubernetes

Query Kubernetes inventory and health data with Dynatrace DQL to diagnose deployment and pod issues.

Official
Advanced