What if the Helm release history is corrupted?

The skill includes advanced scenarios for when 'no revision' is found, including manual resource adoption and inspection of Helm storage secrets.

What happens if a Helm release is stuck in 'pending-upgrade'?

This skill provides steps to force a new upgrade, rollback to a previous working revision, or manually clean up resources to unstick the release state.

Does this skill support atomic deployments?

Absolutely. It emphasizes using the --atomic and --wait flags to ensure deployments either succeed fully or automatically rollback on failure.

Can I rollback to a specific version number?

Yes, the skill guides Claude to identify the correct revision using 'helm history' and execute a rollback to that specific revision number.

Helm Release Recovery

Name: Helm Release Recovery
Author: laurigates

bylaurigates

•

Deployment & DevOps

Automates recovery from failed Helm deployments by managing rollbacks, stuck release states, and deployment history.

About

This skill provides Claude with specialized knowledge to diagnose and resolve Helm deployment failures within Kubernetes environments. It enables the AI to handle common issues like stuck 'pending-install' or 'pending-upgrade' states, perform atomic rollbacks to known-good revisions, and audit release history to maintain infrastructure stability. By utilizing this skill, developers can quickly restore service health using best-practice recovery workflows, including forced resource updates, manual cleanup operations, and metadata restoration.

Key Features

Detailed inspection of Helm release history and deployment status
Support for atomic deployment flags and cleanup-on-fail logic
3 GitHub stars
Diagnosis and resolution of stuck states like pending-install or pending-upgrade
Advanced recovery workflows for corrupted release metadata and storage secrets
Automated rollback to specific or previous release revisions

Use Cases

Unsticking a Helm release trapped in a pending state due to Kubernetes API issues
Auditing release history to identify and restore the last stable configuration
Restoring a production environment after a failed application upgrade or timeout

About

Key Features

Detailed inspection of Helm release history and deployment status
Support for atomic deployment flags and cleanup-on-fail logic
3 GitHub stars
Diagnosis and resolution of stuck states like pending-install or pending-upgrade
Advanced recovery workflows for corrupted release metadata and storage secrets
Automated rollback to specific or previous release revisions

Use Cases

Unsticking a Helm release trapped in a pending state due to Kubernetes API issues
Auditing release history to identify and restore the last stable configuration
Restoring a production environment after a failed application upgrade or timeout