But that is one of the outs that Kube gives you. Start on Kube/GCE and then if needing, you can migrate to colo boxes, and dynamically even. The beauty of a Kube based cloud platform is you can literally start anywhere, go anywhere.
There are some companies using k8s not just for the ability to move, but as a hybrid starting ground.
One bandwith intense workload is running with GKE for all state/databases, but uses a bare-metal k8s cluster for compute and bandwidth intensive stuff. They actually use federation and the bare-metal cluster basically looks for a local database doesn't find one and gets routed to the next available global cluster, which is GKE.
Due to the cache and read dependend nature of the database queries the latency impact is worth it.
