huawei-cloud-cce-container-migration-planner

What problem does it solve? Planning a CCE cluster migration requires manually inventorying workloads, networking, and storage across clusters and cloud services, then reasoning about dependencies, risks, and rollback — a slow, error-prone process that often misses hidden cross-service dependencies. ## Core Features & Use Cases - Read-only resource inventory: Lists CCE clusters, node pools, addons, Deployments, Services, Ingresses, PVCs/PVs, ConfigMaps, Secrets (existence only), plus VPC, subnets, security groups, ELB, EIP, EVS, and SFS/SFS Turbo via a Python SDK dispatcher. - Dependency matrix and batch design: Builds dependency relationships across ingress traffic, service calls, storage bindings, and configuration, then designs migration batches with validation points, downtime windows, and rollback strategies. - Risk assessment with safety boundaries: Produces severity-classified risk lists and manual confirmation checklists; it never creates, modifies, migrates, or deletes any resource. - Use Case: Ask for a migration plan from a CCE cluster in cn-north-4 to another region, and receive a structured report covering inventory, dependency matrix, migration batches, risks, and rollback plan. ## Quick Start Ask the assistant to plan a migration for your CCE cluster by providing the region and cluster ID, for example: inventory all workloads and dependencies in my CCE cluster and generate a migration plan with risk assessment.