What problem does it solve? Upgrading helm charts on Kubernetes clusters involves hidden risks: breaking changes in values schemas, mandatory intermediate versions, stale ConfigMaps, and post-upgrade database migrations. This Skill provides a structured workflow to research, execute, and verify helm upgrades safely. ## Core Features & Use Cases - Upgrade Workflow: Compare current vs latest chart versions, diff values between versions, verify Kubernetes compatibility, execute upgrades, and watch rollouts. - Post-Upgrade Verification: Check application health via APIs, trigger and monitor DB migrations (e.g., SonarQube DB_MIGRATION_NEEDED), and validate new features. - New Feature Enablement: Enable chart features like MCP server sidecars, configure secrets, expose services via Gateway API HTTPRoutes, and wire up Hermes MCP client config. - Use Case: Upgrade SonarQube Community Build from chart 2025.6.1 to 2026.4.0 on EKS, handle the mandatory 25.12.0.117093 stepping stone, trigger the DB migration, and enable the new MCP server sidecar with token auth. ## Quick Start Upgrade the sonarqube helm release in the sonarqube namespace to the latest chart version and verify the deployment is healthy.