hybrid mode about frakti HOT 5 CLOSED

@kfox1111 We are generally happy to have this. According to discussions in original issue, kubernetes/kubernetes#29913, kubelet does not have plan to support multi-runtimes in short term plan, and in long term, sig-node agreed multi-runtimes may be better implemented by remote runtime itself. frakti is a nice place to do this.

One of the blockers which has been fixed recently is CNI network: #62, this will make this refactoring much easier.

from frakti.

In stead of adding a proxy in front, like: https://github.com/Mirantis/virtlet/blob/master/pkg/criproxy/proxy.go, we plan to vendor dockershim in order to reuse duplicated modules like networking. cc @Crazykev

from frakti.

Hi, just wanted to chime in concerning CRI proxy from Virtlet project that you linked to. It's not tied to other parts of Virtlet and we can spin it off into a separate project rather easily so more projects can make use of it. The possible benefits of using the proxy are saving effort on implementation of multiple-runtime dispatch and an ability to deploy alternative runtimes as DaemonSets (thus much easier setup procedure). Another thing we're working on is single-command Virtlet demo startup based on kubeadm-dind-cluster and you can do similar thing for frakti if you want (the proxy has experimental 'bootstrap' feature where it uses DynamicKubeletConfiguration feature to bootstrap itself; this is good for demos)

As of vendoring dockershim, as far as I can I see pkg/kubelet/dockershim package contains mostly stuff tied to docker, and reusing other parts of kubelet package doesn't preclude the usage of the proxy. So if you reconsider your approach a bit please let us know and we'll be glad to help.

cc @pigmej @jellonek @vefimova

from frakti.

As of single-command demo, we envision it as a simple shell script that can be downloaded to a Linux or a Mac with Docker and used to launch kubeadm-dind-cluster (newer version will not need k8s source) and then install Virtlet on it (on Macs it'll be plain qemu instead of qemu-kvm but that doesn't matter much for demo purpose). Similar approach can be used for other projects that employ CRI proxy.

from frakti.

Thanks @ivan4th, after talk with other frakti maintainers, we reached an agreement that we should not hack container/sandbox ID. So we kept the vendor way. Although less elegant, but friendly to CRI ...

from frakti.