Boring technology is a feature, not an apology
Every migration I have regretted started with the sentence “this is much more modern”. Not because the new tool was bad — usually it was fine — but because we underestimated how much of our operational knowledge was stored in the shape of the old one.
A boring stack is a stack whose failure modes you have already met. That is not a small thing. When the pager goes off at 2 a.m., the difference between “I have seen this before” and “I think this is the queue” is roughly an hour of downtime.
The real cost of novelty
Novelty is not paid at adoption. It is paid six months later, when your YAML is three versions behind and the one person who understood the upgrade path has changed jobs.
Choose new things deliberately, in one layer at a time, and write down why.
That is the whole trick. One new layer per year, with an ADR next to it, and a rollback that you have actually executed at least once on a staging machine.