Day 2 operations are everything that happens after a system is deployed: patching, upgrades, scaling, configuration changes, backup, monitoring and compliance. Day 0 is design, Day 1 is the initial deployment, and Day 2 lasts for the rest of the system’s life.
Most automation effort is spent on Day 2, and that’s where Ansible is used most. Teams change configuration across thousands of hosts, upgrade platforms and roll out security fixes, often under time pressure.
Every Day 2 change is a chance to break something that already works. Version upgrades are the riskiest: a new ansible-core release can remove modules your Playbooks depend on. Steampunk Spotter checks Playbooks and Terraform plans for deprecations and compatibility issues before Day 2 changes run. An internal benchmark showed 8× faster migration to Red Hat AAP.
