helm-service-upgrades

Manages helm chart upgrades on Kubernetes including breaking change analysis and post-upgrade verification.

2|Updated Oct 20, 2017
One-click install
npx skills add https://github.com/rbudiharso/dotfiles --skill helm-service-upgrades-rbudiharso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helm-service-upgrades
Source: https://github.com/rbudiharso/dotfiles/tree/main/hermes/.hermes/skills/devops/helm-service-upgrades
Command: npx skills add https://github.com/rbudiharso/dotfiles --skill helm-service-upgrades-rbudiharso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about helm-service-upgrades

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

FAQPage Schema
How do I upgrade a helm chart on Kubernetes safely?▼

Compare current and target chart versions with helm search repo, diff values between versions using helm show values, check release notes for breaking changes and mandatory intermediate versions, then run helm upgrade with your values file and watch the pod rollout with kubectl.

How to check breaking changes between helm chart versions?▼

Pull values from both versions with helm show values and diff them to find removed keys, renamed fields, and changed defaults. Also review the chart's GitHub release notes, ArtifactHub changelog, and community posts for mandatory upgrade paths.

Why doesn't helm upgrade update my ConfigMap?▼

Helm does not always update existing ConfigMaps on upgrade when chart templates skip existing resources. Delete the ConfigMap manually with kubectl delete cm before re-running helm upgrade, then verify the new values with kubectl get cm -o yaml.

How do I handle DB migration after a SonarQube helm upgrade?▼

After a major version upgrade, SonarQube reports DB_MIGRATION_NEEDED status. Trigger migration by POSTing to /api/system/migrate_db inside the pod, then poll /api/system/status until it returns UP, which typically takes 2-4 minutes.

Why do I get 403 errors pulling trivy images from ghcr.io on EKS?▼

ghcr.io rate-limits anonymous pulls aggressively, causing 403 errors from EKS nodes. Use ECR pull-through cache with the cache/ prefix for public.ecr.aws images and github/ prefix for ghcr.io images, verifying manifests with crane before deploying.

What causes AccessDeniedException for non-root containers with PVCs?▼

Containers running as non-root (uid 1000) cannot write to PVCs owned by root, causing AccessDeniedException when creating directories. The workaround is to disable persistence for that container and use emptyDir instead when the data is ephemeral.