devops-rollout-plan

Topics in the source

• DevOps Rollout Plan Generator
• Input Requirements
• Change Description
• Environment Details
• Constraints & Requirements
• Risk Assessment
• Output Format
• 1. Executive Summary

Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes. Gather these details before generating the plan: What's changing (infrastructure, application, configuration) Version or state transition (from/to) Problem solved or feature added Target environment (dev, staging, production, all) Infrastructure type (Kubernetes, VMs, serverless, containers) Affected services and dependencies Current capacity and scale Acceptable downtime window Change window restrictions Approval requirements Regulatory or compliance considerations Blast radius of change Data migrations or schema changes Rollback complexity and safety Known risks Generate a structured rollout plan with these sections: What, why, when, duration Risk level and rollback time Affected systems and user impact Expected downtime Required approvals (technical lead, security, compliance, business) Required resources (capacity, backups, monitoring, rollback automation) Pre-deployment backups Infrastructure health validation Application health baseline Dependency availability Monitoring baseline metrics Go/no-go decision checklist Phases: Pre-deployment, deployment, progressive ve

This is an excerpt. Refer to the complete source and its current requirements.