huawei-cloud-cce-auto-remediation-runner

Executes preview-first, confirm-required remediation actions on Huawei Cloud CCE clusters.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Performing recovery operations on Huawei Cloud CCE clusters (rollbacks, node drains, reboots, scaling) is risky when done blindly. This Skill converts remediation intent into reviewable execution plans that require explicit user confirmation before any mutation, and verifies cluster health afterward. ## Core Features & Use Cases - Preview-First Mutation Guardrails: Every write action (rollback, scale, drain, reboot, delete, hibernate, HSS vulnerability status change) returns a preview with risk level (R1/R2/R3) and refuses to execute until the user explicitly confirms with confirm=true. - Auto-Remediation Orchestration: The huawei_auto_remediation_run action diagnoses a failing Deployment, rolls back to a previous revision when the root cause is CrashLoop, image pull, probe, or startup command failure, waits for recovery, and produces a Markdown execution report. - Broad Action Coverage: Supports workload rollback/scale/resize/delete, node cordon/uncordon/drain, ECS reboot/start/stop, node pool resize, cluster hibernate/awake, EIP bind/unbind, and HPA configuration, plus read-only verification actions. - Use Case: After a root-cause analysis shows a new Deployment revision is in CrashLoopBackOff, use this Skill to preview a rollback to the previous revision, confirm the plan, execute it, and verify pods return to healthy status. ## Quick Start Ask the assistant to preview a rollback of Deployment app-server in namespace default on your CCE cluster, then confirm the plan so it executes and verifies pod health.

Frequently Asked Questions about huawei-cloud-cce-auto-remediation-runner

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

FAQPage Schema
How do I roll back a failed Deployment on Huawei Cloud CCE?▼

Call huawei_auto_remediation_run or huawei_rollback_cce_workload with region, cluster_id, namespace, and workload name. The first call returns a preview showing current and target revisions; only after you explicitly confirm does the rollback execute with confirm=true.

How do I drain or reboot a CCE node safely?▼

Use huawei_cce_node_drain or huawei_reboot_ecs, which are classified as R3 high-risk actions. They always run in preview mode first, require explicit per-object user confirmation, and must be followed by read-only verification such as huawei_get_kubernetes_nodes.

Does this skill execute remediation automatically without confirmation?▼

No. Auto-adding confirm=true is explicitly prohibited. Every mutation action must go through preview, explicit user confirmation of action, object, and risks, then execution, then post-execution verification.

What credentials and permissions are required for CCE remediation?▼

You need HW_ACCESS_KEY and HW_SECRET_KEY environment variables, with optional HW_REGION_NAME and HW_PROJECT_ID. IAM permissions include cce:cluster:get, cce:node:update, cce:nodepool:update, and AOM read permissions for validation.

When should I not use the auto-remediation runner?▼

Do not use it for read-only diagnosis, which belongs to the root-cause-analyzer or domain diagnoser skills. It also refuses batch or fuzzy-target remediation and will not roll back when the root cause is unsuitable, such as non-deployment failures.

What risk levels does the remediation workflow enforce?▼

Actions are classified R1 (read-only verification, no confirmation), R2 (runtime impact like scale, cordon, rollback; preview plus confirm), and R3 (destructive like delete, drain, reboot, hibernate; explicit per-object confirmation plus mandatory verification).