Build reversible migrations
Infrastructure changes become safer when the replacement can be prepared and tested before the previous path is removed.
Separate preparation from activation
Build the new service independently. Inspect the host before installing anything, preserve unrelated workloads, and verify local dependencies. Activate one public dependency at a time: address assignment, DNS, control-plane registration, and finally user traffic.
This sequence keeps failures attributable. If several dependencies change simultaneously, a rollback becomes guesswork.
Define evidence and rollback
Write the success checks before the change. They should cover process state, listening sockets, firewall behavior, public DNS, certificates, management connectivity, and a real client request. Define the observation that will trigger rollback and the exact operation required.
Backups are useful only when their scope and restoration procedure are known. A small copy of the previous configuration beside a tested restore command is often more valuable than an unexamined full-system archive.
Record the active state
Documentation should describe object relationships, routing intent, public exposure, and verification results without storing credentials. Future operators need to understand why the system is shaped this way, not merely repeat the last command that happened to work.
- ← Previous
Certificates are a lifecycle