Building a Deployment Checklist That Actually Prevents Production Incidents
Count the items on your deployment checklist. If there are more than a handful, the list is not telling you that your team is careful. It is telling you how much infrastructure your product team still owns.
That is the argument of this article. A deployment checklist earns its length from application risk: the ways your own code, data, and rollout can hurt users. Every other item — certificates, load balancers, image provenance, autoscaling, connection draining — is a piece of plumbing you are verifying by hand because nothing else verifies it for you. Those items do not need better wording. They need an owner, and the question worth asking is why that owner is still your product team.
This assumes you are already running applications in production, with a pipeline, a rollback story of some kind, and an incident history worth reading. The question is not how to start...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
