search

cybozu-go / coil

CNI plugin for Kubernetes designed for scalability and extensibility
Apache License 2.0
164 stars 20 forks source link

Install on an existing Flannel-based cluster #156

Closed nsoubelet closed 3 years ago

nsoubelet commented 3 years ago

Hello, this is not an issue, but I could not find any other way to contact you therefore writing here.

The situation is as follows: I have a cluster already up and running which uses Flannel. That is why I don't know whether it is possible to install Coil over that setup. Taking into account that Flannel is a L3 network plugin, I think that simply uninstalling driver won't work because I will untie the entire cluster network...

Am I right? If the answer is yes, then any experience with a migration like this?

Extra info: I found this article https://github.com/kubernetes/kops/blob/master/docs/networking.md#switching-between-networking-providers which is under the Kops repo saying that, in a nutshell, changing between CNI providers is not really recommended.

Thanks guys

ymmt2005 commented 3 years ago

@nsoubelet Hi. Replacing CNI plugins without breaking workloads would be very hard, if at all possible. The only support we can provide is to migrate from Coil v1 to Coil v2.

nsoubelet commented 3 years ago

Hi @ymmt2005 Understood, many thanks.