If the answer is no, you can’t, then:
Are there any pitfalls here in this regard?
If the answer is no, then
Basically, it’s all going to be manual. You are pretty much going to set up everything again from scratch somewhere else. Since Federation V2 is not yet ready for production use, multicluster communication is always going to be an issue.
Can you easily replicate the cluster somewhere else by exporting the configuration used by the managed Digital Ocean Kubernetes master, and deploy it on, for example, AWS? If this is universal then I think by prebuilding and bootstrapping components as custom charts and enable database concurrency and replicating it before migrating the cluster over and pull the plug for the cluster here would reasonably work?
Subconsciously, I have a hunch that having a managed solution is a bad idea because if you don’t control the initial deployment, then it will not be replicable without the original deployment manager, which is not portable, not standardized and often proprietary, which defeats the purpose of Kubernetes, which is to standardize deployment and enable vendor neutrality.
That is deploying everything yourself using kubectl on vanilla droplets? That can maximize portability even without federation V2 support. The Kubenete idea is to use infrastructure as a service, or IaaS. Just like Mobile service carriers or ISPs, they should be a pipe for data aka. IaaS, not a platform as a service PaaS. So, moving from T&T to T-Mobile, for example, should be frictionless.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $100 of credit to try our products over 60 days!
Hey there!
Thanks for your questions. DOKS cannot be used to provision clusters on other cloud providers. It is possible to export your data from an existing cluster, enabling you to migrate to a different region or cloud provider.
Take a look at this post which explains how to export all of your resources as YAML https://github.com/kubernetes/kubernetes/issues/24873
And also take a look at this project from Heptio which will allow you to export your workloads and their data, as well as perform backups: https://github.com/heptio/velero
Regards, Phil