Devops Rollout Plan

1---2name: devops-rollout-plan3description: 'Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes'4---5 6# DevOps Rollout Plan Generator7 8Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.9 10## Input Requirements11 12Gather these details before generating the plan:13 14### Change Description15- What's changing (infrastructure, application, configuration)16- Version or state transition (from/to)17- Problem solved or feature added18 19### Environment Details20- Target environment (dev, staging, production, all)21- Infrastructure type (Kubernetes, VMs, serverless, containers)22- Affected services and dependencies23- Current capacity and scale24 25### Constraints & Requirements26- Acceptable downtime window27- Change window restrictions28- Approval requirements29- Regulatory or compliance considerations30 31### Risk Assessment32- Blast radius of change33- Data migrations or schema changes34- Rollback complexity and safety35- Known risks36 37## Output Format38 39Generate a structured rollout plan with these sections:40 41### 1. Executive Summary42- What, why, when, duration43- Risk level and rollback time44- Affected systems and user impact45- Expected downtime46 47### 2. Prerequisites & Approvals48- Required approvals (technical lead, security, compliance, business)49- Required resources (capacity, backups, monitoring, rollback automation)50- Pre-deployment backups51 52### 3. Preflight Checks53- Infrastructure health validation54- Application health baseline55- Dependency availability56- Monitoring baseline metrics57- Go/no-go decision checklist58 59### 4. Step-by-Step Rollout Procedure60**Phases**: Pre-deployment, deployment, progressive verification61- Specific commands for each step62- Validation after each step63- Duration estimates64 65### 5. Verification Signals66**Immediate** (0-2 min): Deployment success, pods/containers started, health checks passing67**Short-term** (2-5 min): Application responding, error rates acceptable, latency normal68**Medium-term** (5-15 min): Sustained metrics, stable connections, integrations working69**Long-term** (15+ min): No degradation, capacity healthy, business metrics normal70 71### 6. Rollback Procedure72**Decision Criteria**: When to initiate rollback73**Rollback Steps**: Automated, infrastructure revert, or full restore74**Post-Rollback Verification**: Confirm system health restored75**Communication**: Stakeholder notification76 77### 7. Communication Plan78- Pre-deployment (T-24h): Schedule and impact notice79- Deployment start: Commencement notice80- Progress updates: Status every X minutes81- Completion: Success confirmation82- Rollback (if needed): Issue notification83 84**Stakeholder Matrix**: Who to notify, when, via what method, with what content85 86### 8. Post-Deployment Tasks87- Immediate (1h): Verify criteria met, review logs88- Short-term (24h): Monitor metrics, review errors89- Medium-term (1 week): Post-deployment review, lessons learned90 91### 9. Contingency Plans92Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure93For each: Symptoms, response, timeline94 95### 10. Contact Information96- Primary and secondary on-call97- Escalation path98- Emergency contacts (infrastructure, security, database, networking)99 100## Plan Customization101 102Adapt based on:103- **Infrastructure Type**: Kubernetes, VMs, serverless, databases104- **Risk Level**: Low (simplified), medium (standard), high (additional gates)105- **Change Type**: Code deployment, infrastructure, configuration, data migration106- **Environment**: Production (full plan), staging (simplified), development (minimal)107 108## Remember109 110- Always have a tested rollback plan111- Communicate early and often112- Monitor metrics, not just logs113- Document everything114- Learn from each deployment115- Never deploy on Friday afternoon (unless critical)116- Never skip verification steps117- Never assume "it should work"