From deployment-rollback-manager
Implements rollback procedures for Kubernetes, ECS, Lambda, and cloud VM deployments. Detects failures via monitoring and health checks, reverts to stable versions, verifies success, and generates reports.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin deployment-rollback-managerThis skill is limited to using the following tools:
Implement and execute deployment rollback procedures for Kubernetes, ECS, Lambda, and cloud VM deployments. Detect failed deployments via health checks and error rate monitoring, then automatically or manually revert to the last known good version with minimal downtime and data integrity preservation.
Orchestrates multi-stage deployment pipelines with Kubernetes, CI/CD platforms, and strategies like blue-green, canary, rolling updates across dev/staging/prod.
Provides zero-downtime deployment strategies including blue-green, canary releases, rolling updates, rollbacks, feature flags, and health checks. Useful for release management and minimizing risks.
Provides rollback procedures, risk assessment, pre/post-deployment validation checklists, and contingency planning for safe deployments.
Share bugs, ideas, or general feedback.
Implement and execute deployment rollback procedures for Kubernetes, ECS, Lambda, and cloud VM deployments. Detect failed deployments via health checks and error rate monitoring, then automatically or manually revert to the last known good version with minimal downtime and data integrity preservation.
kubectl configured with cluster access and permission to manage deploymentsrevisionHistoryLimit, ECS task definition versions)kubectl rollout undo deployment/<name> to revert to the previous revision| Error | Cause | Solution |
|---|---|---|
no rollout history found | Revision history limit set to 0 or deployment was created fresh | Increase revisionHistoryLimit in deployment spec; manually specify the target image tag |
Rollback succeeded but errors persist | Issue is in configuration or external dependency, not application code | Check ConfigMaps, Secrets, and external service health; rollback configuration changes separately |
Database schema incompatible after rollback | Forward-only migration applied during failed deployment | Apply a down migration or use expand-contract pattern; never deploy breaking schema changes alongside code |
Old image no longer in registry | Lifecycle policy deleted the previous image | Restore from backup or rebuild from the git tag; extend image retention for production tags |
Rollback causes service disruption | Insufficient replicas during rollback transition | Set maxUnavailable: 0 in rolling update strategy to ensure zero-downtime rollback |