That's clearly also a disadvantage, because part of the source of k8s complexity is being a generic services supporter.
Please apply some level of critical thinking before copying/pasting generic selling points that could apply to almost any other open-source IAC framework.
"I could never run a scalable service on the cloud without Kubernetes."
But also
"The alternative to Kubernetes is learning proprietary technologies like "Elastic Beanstalk" and "Azure App Service" and so on. No thank you"
So can we clarify that you truly meant: "I decided not to run a scalable service in the cloud using any of the existing cloud tools that do and have supported that scenario for years. And decided to use k8s instead" :)
You clearly understood one of the primary incentives that drives k8s adoption (career self-interest).
And then you issued advice like "Don't do this". I'm curious if you truly believe that anybody in the above class of people would change their ways on that basis, and without a greater incentive.
Please apply some level of critical thinking before copying/pasting generic selling points that could apply to almost any other open-source IAC framework.