From my personal experience, yes, but not just for scale. I've used Kubernetes in a 300k person organization and now in a 35 person organization. Kubernetes isn't the simplest solution, but it's just reliability in a box. You can control the network, and the servers, and the load balancing all through the API which means for most things I can install a fully clustered solution with a handful of commands. Set the number of instances I want to run and forget the whole thing exists. Suddenly I'm cloud agnostic by default and the underlying K8s management is handled by the cloud provider.
In the 300k person org it was for scale and reliability. In the 35 person org it's so that 1 guy can manage everything without trying.
I see. My last work experiences have been introducing devops workflows into companies that already had a decent tech body (~200 people) and the traditional divide between IT/Dev.
I think the approach I mention ends up being a good compromise from both sides. If I were starting a company from scratch I would certainly consider it differently.
In the 300k person org it was for scale and reliability. In the 35 person org it's so that 1 guy can manage everything without trying.