Closed haosdent closed 5 years ago
We are running virtlet as VM on kubernetes solution, and it is in pre-prod stage. And get rid of criproxy is in our plan, we also had design about it. We consider to have a vm-shim-v2 that follows containerd shim v2 spec to launch VM. But at the OCI level, we may miss some necessary information to build a VM, we need the shim to communicate with virtlet daemonset pod to build whole libvirt xml domain. Will keep posted if we've done the implementation.
@keyingliu Thank you very much for your reply. May you mind share your email? Or do you use wechat?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Is this change still in the roadmap?
we need the shim to communicate with virtlet daemonset pod to build whole libvirt xml domain.
@keyingliu Have you create an issue at https://github.com/containerd/containerd for this?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Hi, does virtlet have plans to integrated with container runtime v2 API like kata instead of set up CRI proxy in every server? CRI proxy is not user-friendly.
containerd runtime v2 API https://github.com/containerd/containerd/tree/master/runtime/v2