huawei-cloud-cce-capacity-trend-forecaster

Analyzes Huawei Cloud CCE capacity trends, forecasts bottlenecks, and simulates HPA and node autoscaler policies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? It helps operators understand how Huawei Cloud CCE cluster capacity evolves over time, predict when CPU, memory, or disk will hit bottleneck thresholds, and decide how to tune HPA and node autoscaler settings before resources run out or are wasted. ## Core Features & Use Cases - Capacity Trend Analysis: Collects node CPU, memory, and disk metrics over windows from 1 hour to 1 month, computing avg, p95, max, slope, trend direction, and bottleneck arrival predictions. - Elasticity Simulation & Reports: Simulates recommended node counts with configurable targets and headroom, then generates JSON, Markdown, and HTML reports with embedded SVG curve charts plus comparable history records. - HPA Configuration Workflow: Generates HPA manifests and previews or applies HPA configuration through a two-step confirm=true approval flow. - Use Case: Run a weekly capacity analysis on a production cluster, discover CPU p95 trending toward the 80% bottleneck threshold, preview an HPA adjustment for an uncovered Deployment, and compare the next week's record to validate the change. ## Quick Start Ask the assistant to run a 6-hour capacity trend analysis for your CCE cluster by providing the region and cluster ID, for example: analyze capacity trends for cluster <cluster-id> in cn-north-4 over the last 6 hours.

Frequently Asked Questions about huawei-cloud-cce-capacity-trend-forecaster

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

FAQPage Schema
How do I analyze CCE cluster capacity trends on Huawei Cloud?▼

Run the huawei_analyze_cce_capacity_trend action with region and cluster_id, optionally setting hours from 1 to 744. It collects node metrics, HPA status, and autoscaler status, then writes JSON, Markdown, and HTML reports with trend charts.

How to forecast when CCE node CPU or memory will run out?▼

The analyzer computes slope and trend direction per resource and predicts hours until the configured bottleneck threshold (default 80 percent) is reached. Rising trends with high p95 are flagged as capacity risks in the report.

Does this skill modify HPA or node pool settings automatically?▼

No. Analysis and simulation are read-only, and HPA configuration uses a two-step workflow: call huawei_configure_cce_hpa without confirm to preview, then add confirm=true only after explicit user approval. Node pool changes always require authorization.

What credentials and permissions are needed for CCE capacity analysis?▼

Set HUAWEI_AK and HUAWEI_SK environment variables; project ID is auto-fetched via IAM. Required permissions include cce:cluster:list, cce:node:list, cce:nodepool:list, cce:deployment:list, cce:hpa:list, and aom:metric:get.

Why is a single capacity period not enough for downsizing decisions?▼

A single window can miss burst patterns, so the skill requires at least two comparable history records before lowering baseline capacity. If p95 or max utilization is near the bottleneck threshold, it recommends keeping headroom instead of reducing nodes.

What happens when AOM metrics are unavailable during analysis?▼

The skill reports the gap in the data_gaps output field and does not fabricate trend conclusions. You should treat the affected resources as unknown and rerun analysis once metric collection is restored.