Kubernetes is like sex in high school. Everyone says they’ve done it but very few have <i>actually</i> done it.<p>It’s a bit early to say anything. If anything the death of k8s will be sparked by all those who fail to implement it the right way like we all did with AWS.<p>I first got into AWS very early on and one of its early official selling points was ephemerality yet most of us treat everything as pets, EC2 has affectively become just a vanilla hosting/managed provider with an API on top.<p>K8s isn’t difficult or complex, it’s just different and once you get it you get it. What ruins it is things like not following its intended paradigm, breaking the isomorphism and determinism of the containers… insisting things ansible, chef, salt, et la.. are still required. Grabbing a shell into container to debug something non app related, effectively breaking the ephemeral nature. The only thing you’ve effectively done is added additional complexity without hacking off any of the stuff that should be dead<p>Before k8s goes out I think no-code and then by extension no-infra will become a lot more ubiquitous, and if anything no-code will consolidate off a good chunk of our industry
The worst thing about kubernetes, or the hype around kubernetes, is that it leads people who never liked microservices and never took the time to understand how to do them well, to turn their stack into a series of microservices.