Originally published at devopsdiary.blog
The first time I asked ChatGPT to write a deployment runbook, it did. That was the problem.
The output was close enough to be dangerous: kubectl steps, rollback sequence, health check endpoints. Structured, clear, apparently professional. But it had no idea whether any of it belonged to us. Whether our tooling matched what it described. Whether the service was subject to SOX controls or just basic SLO monitoring.
It wrote a competent generic runbook for a deployment process that didn't exist at our org. We already had something for that. It was called Google.
What December 2023 looked like from a platform engineering chair
