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 changes.4---56# DevOps Rollout Plan Generator78Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.910## Input Requirements1112Gather these details before generating the plan:1314### Change Description15- What's changing (infrastructure, application, configuration)16- Version or state transition (from/to)17- Problem solved or feature added1819### Environment Details20- Target environment (dev, staging, production, all)21- Infrastructure type (Kubernetes, VMs, serverless, containers)22- Affected services and dependencies23- Current capacity and scale2425### Constraints & Requirements26- Acceptable downtime window27- Change window restrictions28- Approval requirements29- Regulatory or compliance considerations3031### Risk Assessment32- Blast radius of change33- Data migrations or schema changes34- Rollback complexity and safety35- Known risks3637## Output Format3839Generate a structured rollout plan with these sections:4041### 1. Executive Summary42- What, why, when, duration43- Risk level and rollback time44- Affected systems and user impact45- Expected downtime4647### 2. Prerequisites & Approvals48- Required approvals (technical lead, security, compliance, business)49- Required resources (capacity, backups, monitoring, rollback automation)50- Pre-deployment backups5152### 3. Preflight Checks53- Infrastructure health validation54- Application health baseline55- Dependency availability56- Monitoring baseline metrics57- Go/no-go decision checklist5859### 4. Step-by-Step Rollout Procedure60**Phases**: Pre-deployment, deployment, progressive verification61- Specific commands for each step62- Validation after each step63- Duration estimates6465### 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 normal7071### 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 notification7677### 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 notification8384**Stakeholder Matrix**: Who to notify, when, via what method, with what content8586### 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 learned9091### 9. Contingency Plans92Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure93For each: Symptoms, response, timeline9495### 10. Contact Information96- Primary and secondary on-call97- Escalation path98- Emergency contacts (infrastructure, security, database, networking)99100## Plan Customization101102Adapt 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)107108## Remember109110- 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"
GitHub (Microsoft)