AWS announced EKS Version Rollback this week, and I think it is one of those features that will sound boring to anyone who has never owned a Kubernetes upgrade calendar.

It is not boring.

For years, the practical answer to "what if the cluster upgrade goes wrong?" has been a mixture of planning, nervousness, staging environments, compatibility checks, careful node rollouts, and someone saying "we can always rebuild" in a tone that did not make anyone feel better.

Kubernetes is excellent at making infrastructure programmable. It has been much less comforting when the thing you just programmed is the control plane itself.

So yes, EKS rollback is a product feature. You can roll a cluster back by one minor version within a limited window. EKS runs readiness checks. Auto Mode can also handle worker node rollback as part of the path.