DevOps Rollout Plan Generator
Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.
Input Requirements
Gather these details before generating the plan:
Change Description
- What's changing (infrastructure, application, configuration)
- Version or state transition (from/to)
- Problem solved or feature added
Environment Details
- Target environment (dev, staging, production, all)
- Infrastructure type (Kubernetes, VMs, serverless, containers)
- Affected services and dependencies
- Current capacity and scale
Constraints & Requirements
- Acceptable downtime window
- Change window restrictions
- Approval requirements
- Regulatory or compliance considerations
Risk Assessment
- Blast radius of change
- Data migrations or schema changes
- Rollback complexity and safety
- Known risks
Output Format
Generate a structured rollout plan with these sections:
1. Executive Summary
- What, why, when, duration
- Risk level and rollback time
- Affected systems and user impact
- Expected downtime
2. Prerequisites & Approvals
- Required approvals (technical lead, security, compliance, business)
- Required resources (capacity, backups, monitoring, rollback automation)
- Pre-deployment backups
3. Preflight Checks
- Infrastructure health validation
- Application health baseline
- Dependency availability
- Monitoring baseline metrics
- Go/no-go decision checklist
4. Step-by-Step Rollout Procedure
Phases: Pre-deployment, deployment, progressive verification
- Specific commands for each step
- Validation after each step
- Duration estimates
5. Verification Signals
Immediate (0-2 min): Deployment success, pods/containers started, health checks passing
Short-term (2-5 min): Application responding, error rates acceptable, latency normal
Medium-term (5-15 min): Sustained metrics, stable connections, integrations working
Long-term (15+ min): No degradation, capacity healthy, business metrics normal
6. Rollback Procedure
Decision Criteria: When to initiate rollback
Rollback Steps: Automated, infrastructure revert, or full restore
Post-Rollback Verification: Confirm system health restored
Communication: Stakeholder notification
7. Communication Plan
- Pre-deployment (T-24h): Schedule and impact notice
- Deployment start: Commencement notice
- Progress updates: Status every X minutes
- Completion: Success confirmation
- Rollback (if needed): Issue notification
Stakeholder Matrix: Who to notify, when, via what method, with what content
8. Post-Deployment Tasks
- Immediate (1h): Verify criteria met, review logs
- Short-term (24h): Monitor metrics, review errors
- Medium-term (1 week): Post-deployment review, lessons learned
9. Contingency Plans
Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure
For each: Symptoms, response, timeline
10. Contact Information
- Primary and secondary on-call
- Escalation path
- Emergency contacts (infrastructure, security, database, networking)
Plan Customization
Adapt based on:
- Infrastructure Type: Kubernetes, VMs, serverless, databases
- Risk Level: Low (simplified), medium (standard), high (additional gates)
- Change Type: Code deployment, infrastructure, configuration, data migration
- Environment: Production (full plan), staging (simplified), development (minimal)
Remember
- Always have a tested rollback plan
- Communicate early and often
- Monitor metrics, not just logs
- Document everything
- Learn from each deployment
- Never deploy on Friday afternoon (unless critical)
- Never skip verification steps
- Never assume "it should work"
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 changes4---5# DevOps Rollout Plan Generator67Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.89## Input Requirements1011Gather these details before generating the plan:1213### Change Description1415- What's changing (infrastructure, application, configuration)16- Version or state transition (from/to)17- Problem solved or feature added1819### Environment Details2021- Target environment (dev, staging, production, all)22- Infrastructure type (Kubernetes, VMs, serverless, containers)23- Affected services and dependencies24- Current capacity and scale2526### Constraints & Requirements2728- Acceptable downtime window29- Change window restrictions30- Approval requirements31- Regulatory or compliance considerations3233### Risk Assessment3435- Blast radius of change36- Data migrations or schema changes37- Rollback complexity and safety38- Known risks3940## Output Format4142Generate a structured rollout plan with these sections:4344### 1. Executive Summary4546- What, why, when, duration47- Risk level and rollback time48- Affected systems and user impact49- Expected downtime5051### 2. Prerequisites & Approvals5253- Required approvals (technical lead, security, compliance, business)54- Required resources (capacity, backups, monitoring, rollback automation)55- Pre-deployment backups5657### 3. Preflight Checks5859- Infrastructure health validation60- Application health baseline61- Dependency availability62- Monitoring baseline metrics63- Go/no-go decision checklist6465### 4. Step-by-Step Rollout Procedure6667**Phases**: Pre-deployment, deployment, progressive verification6869- Specific commands for each step70- Validation after each step71- Duration estimates7273### 5. Verification Signals7475**Immediate** (0-2 min): Deployment success, pods/containers started, health checks passing76**Short-term** (2-5 min): Application responding, error rates acceptable, latency normal77**Medium-term** (5-15 min): Sustained metrics, stable connections, integrations working78**Long-term** (15+ min): No degradation, capacity healthy, business metrics normal7980### 6. Rollback Procedure8182**Decision Criteria**: When to initiate rollback83**Rollback Steps**: Automated, infrastructure revert, or full restore84**Post-Rollback Verification**: Confirm system health restored85**Communication**: Stakeholder notification8687### 7. Communication Plan8889- Pre-deployment (T-24h): Schedule and impact notice90- Deployment start: Commencement notice91- Progress updates: Status every X minutes92- Completion: Success confirmation93- Rollback (if needed): Issue notification9495**Stakeholder Matrix**: Who to notify, when, via what method, with what content9697### 8. Post-Deployment Tasks9899- Immediate (1h): Verify criteria met, review logs100- Short-term (24h): Monitor metrics, review errors101- Medium-term (1 week): Post-deployment review, lessons learned102103### 9. Contingency Plans104105Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure106For each: Symptoms, response, timeline107108### 10. Contact Information109110- Primary and secondary on-call111- Escalation path112- Emergency contacts (infrastructure, security, database, networking)113114## Plan Customization115116Adapt based on:117118- **Infrastructure Type**: Kubernetes, VMs, serverless, databases119- **Risk Level**: Low (simplified), medium (standard), high (additional gates)120- **Change Type**: Code deployment, infrastructure, configuration, data migration121- **Environment**: Production (full plan), staging (simplified), development (minimal)122123## Remember124125- Always have a tested rollback plan126- Communicate early and often127- Monitor metrics, not just logs128- Document everything129- Learn from each deployment130- Never deploy on Friday afternoon (unless critical)131- Never skip verification steps132- Never assume "it should work"
egohygiene