Kubernetes is an enterprise architecture
Five years ago, in the Pivotal Cloud Foundry days, we had a lot bravado. We almost challenged people, dared them to do something radically different. The mindset of doing daily releases, collapsing together multiple roles into product teams (business analyst-cum-product manager, developer, designer - this second a totally foreign concept to most enterprises) and then automating so much infrastructure that ops people were sort of not needed - it was a lot to process if you were a VP of Infrastructure in 2015, or even a CIO.
We would call this an “opinionated” platform. Brian Gracely was the first I remember to thoroughly describe what was going on here. His distinction between structured (“opinionated”) and unstructured platforms was great. We should have hired that guy! :)
Whatever it was called, opinionated/structured meant that meant that we’d made choices about how you architect your application, packaged it, instrumented it, and run it. To get all the benefits - for it to even work - you’d have to follow these opinions. Early on, these types apps would be described as something like “12 factor apps” using microserves. I think we call them “cloud native” apps now.