
Welcome to Container Harbour! π’ Ep.15
Episode 15: Leaving Harbour Gracefully π The Production Deployment That Used to Require a 2am Saturday Maintenance Window π€ Every engineer who has been around long enough has a war story. Mine involves: A 2am Saturday maintenance window A 45-minute planned outage A deployment script that nobody had tested end-to-end A rollback that took longer than the deployment One very understanding on-call team Three energy drinks A fundamental reassessment of my life choices We took the service DOWN. We deployed. We brought it UP. Users couldn't access their accounts for 45 minutes. On a Saturday night. Because that's when "traffic was lowest." Today? Our deployments happen at 2pm on a Tuesday. During peak traffic. While the team is in a retro. Nobody notices. The service never goes down. This is the final episode of Container Harbour. Let's make it count. π― The SIPOC of Zero-Downtime Deployment ποΈ Detail Supplier Who triggers the deployment? Developer, CI/CD pipeline, GitOps (ArgoCD, Flux) Input
Continue reading on Dev.to Tutorial
Opens in a new tab



