Running the same large scale cluster on Openshift (with a managed lifecycle) on a different cloud, is just a matter of: `openshift-installer create install-con

Running the same large scale cluster on Openshift (with a managed lifecycle) on a different cloud, is just a matter of: `openshift-installer create install-config --dir=install_1` edit the deployment size, and any small vendor specific tweaks like instance size ~5 lines `openshift-installer create cluster --dir=install_1` You'll get a different StorageClass from which you can make Persistent Volume Claims from, easy scaling of nodes using `kubectl scale machineset` or an autoscaler. Even with bare metal setup, which requires setting up some DNS wildcards and DHCP, everything down to the layers(I think they're layers) of the OS filesystem can be managed via a K8s custom resource (backed by ignition). You can create network attachment definitions for multiple nics, you can specify the contents of a config file via a bunch of MachineConfigs. And you can just not do all of this until you need to, you can go straight ahead to creating Deployments, and load balanced services. With KubeVirt, you can use k8s resources and virtctl to manage virtual machines. Vendor specificness is highly minimized by a management layer.