There would be many development teams who used to have their own kubernetes cluster (on-premise or cloud) before they discover Rancher! (like our team )
I know Rancher allows us to import an existing cluster (non Rancher launched), but given the fact that for these imported clusters users would not get cool features like taking/restoring snapshots, updating the cluster from rancher UI or cluster.yml file… there would be this strong tendency to replace the existing imported cluster with a rancher launched cluster. Right?
Well…the challenge is that nobody likes down time for the apps and services.
I know we have the concept of etcd and everything to recover a cluster and the workloads.
But I would like to suggest to the Rancher community to come up with a step to step instruction documented in Rancher website about
How to nicely and cleanly migrate from an existing non Rancher launched k8s cluster to a Rancher launched k8s cluster without down time
I think this would be important