Sounds like you are into some 90's top-down management mentality right there. Good luck with that. (in my experience, that no longer works well, and is a poor solution applied in highly regulated markets and mainframe land) That makes your lack of high speed software supply chain management not go away, and with ECS you'll just get mandatory Fargate update notifications, unless you're using ECS EC2 in which case, what you are even doing?

We don't allow systems that cannot be mass-managed and don't have an active lifecycle that keeps up with demand. Sometimes that doesn't mean K8S, but often it does because it's the only large adopted system with a high speed reconciler. But the teams get to choose that on their own.

Edit: let me rephrase that a little.

It seems that software lifecycle speed and business speed interact to a degree where if the software is faster than the business, you need a different product or speed up the business. For me, that would mean that if either aren't an option, I'd change jobs because it doesn't align with my standards.

I stopped after your first sentence. There is no way that level of thinking can lead to an orderly organization.

Oneplane sounds right to me. Perhaps to you “order” is the most important thing, rather than teams’ efficiency, effectiveness and innovation. Which if so sort of proves the 90s point.

Unless your company has one product ("orderliness"), that seems not all that relevant. It's also highly unlikely that some sort of 'boss at the top' knows everything and therefore is the only one with the capability to make choices.