What problem does it solve? Upgrading a CCE cluster's Kubernetes version is risky: skip-version attempts fail, deprecated APIs break workloads, addon incompatibilities surface mid-upgrade, and teams often underestimate the maintenance window. This Skill produces a structured upgrade assessment—path validation, 76-item pre-check, addon compatibility, window estimation, and execution preview—before any irreversible change is made. ## Core Features & Use Cases - Upgrade Path Validation: Queries ListClusterUpgradePaths and enforces no-skip-version rules, patch-first ordering, and version-specific breaking changes (PSP removal in v1.25, Docker deprecation in v1.27, control node IP changes in v1.28). - 76-Item Pre-Check & Addon Compatibility: Runs ShowClusterUpgradeInfo or CreateUpgradeWorkFlow, maps failed checks to fixes, and classifies addons by upgrade timing (auto, before, or after cluster upgrade). - Window Estimation & Execution Preview: Calculates total upgrade time from node count, batch strategy, and addon count, then generates hcloud CLI commands gated behind a two-step confirmation mechanism. - Use Case: Before upgrading a 10-node cluster from v1.23 to v1.25, use this Skill to confirm the path is direct, verify all 76 pre-checks pass, confirm CoreDNS and NGINX Ingress compatibility, and get an estimated ~4-hour window with rollback strategy. ## Quick Start Ask the assistant to assess upgrading your CCE cluster from its current version to a target version, providing the cluster ID and region so it can run the pre-check and produce an upgrade plan.
