Every day I deal with AWS, Google Cloud and Oracle Cloud. Previously I used DigitalOcean and OVH. I have no issues onboarding people to work with the less popular options - as long as they get how Kubernetes / Linux / containers work, it's pretty good.
EKS, AKE, GKE, LKE, DOKS, OKD, Rancher... Whatever they're all compatible with what you want to do. There are definitely upsides to the cloud, but Kubernetes is the common denominator everywhere.
Wanna run GPU workloads on-prem? Buy some servers and do so. The only hairy thing is managing your own storage, quite the responsibility. (Look at Atlassian right now).
GKE https://cloud.google.com/container-engine/docs/cluster-autos...
AWS https://github.com/kubernetes/autoscaler/blob/master/cluster...
Azure https://github.com/kubernetes/autoscaler/blob/master/cluster...
Alibaba Cloud https://github.com/kubernetes/autoscaler/blob/master/cluster...
Brightbox https://github.com/kubernetes/autoscaler/blob/master/cluster...
OpenStack Magnum https://github.com/kubernetes/autoscaler/blob/master/cluster...
DigitalOcean https://github.com/kubernetes/autoscaler/blob/master/cluster...
CloudStack https://github.com/kubernetes/autoscaler/blob/master/cluster...
Exoscale https://github.com/kubernetes/autoscaler/blob/master/cluster...
Equinix Metal https://github.com/kubernetes/autoscaler/blob/master/cluster...
OVHcloud https://github.com/kubernetes/autoscaler/blob/master/cluster...
Linode https://github.com/kubernetes/autoscaler/blob/master/cluster...
OCI https://github.com/kubernetes/autoscaler/blob/master/cluster...
Hetzner https://github.com/kubernetes/autoscaler/blob/master/cluster...
Cluster API https://github.com/kubernetes/autoscaler/blob/master/cluster...
Vultr https://github.com/kubernetes/autoscaler/blob/master/cluster...
TencentCloud https://github.com/kubernetes/autoscaler/blob/master/cluster...
These are all cloud providers that invested into their own managed Kubernetes, I'm certain all of them aren't as sleek as the big three, but it shows that there's definitely momentum behind sticking your workloads into Kubernetes.
In the past, if you needed a load-balancer & reverse proxy you'd use Nginx or HAProxy regardless of the underlying machine. Now in the cloud, although you can technically run it on a VM, it's not "best practice" and you should instead reimplement it using your cloud vendor's proprietary equivalent, whether it's AWS ELB/ALB or something else, and that experience isn't portable across competing clouds.
Those are not tools from the past. They still work really well and there is no law requiring your brand new startup to be on AWS.
Most companies (even more when they are B2B) have very predictable workloads.
But anyone who’s done infra at scale can easily get up to speed on any of the big three—-as long as you take the time to understand the differences, and actually model costs before starting to play around.