Aside from that, there’s no reason to have dockershim in Kubelet; CRI has been out for a while now...
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-node" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To post to this group, send email to kubernete...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/CANw6fcFKtY5u5gJfXW3vJ11Vr9vuUSZwbZWY7US9KSiskG19sA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/CY4PR21MB05048D89FB89800517C9380BDB610%40CY4PR21MB0504.namprd21.prod.outlook.com.
I think this is probably best discussed in a KEP, but I am supportive of documenting a plan to eventually eliminate the dockershim from the in-tree kubelet at a time that is responsible for the whole community just to reduce the amount of code to maintain. The KEP would have to address many of the questions raised from Mike. From experience, I can say that transitioning from dockershim -> external CRI is non-trivial, and we would need to give a sufficient amount of advanced warning announcing the intent over many releases.
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-node" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To post to this group, send email to kubernete...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/4c899b08-8215-49f7-b7ac-e77fcd2ffd41%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-node+unsub...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To post to this group, send email to kubernetes-si...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CANw6fcFKtY5u5gJfXW3vJ11Vr9vuUSZwbZWY7US9KSiskG19sA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-node+unsub...@googlegroups.com.
Folks,
For several versions now, Docker ships with containerd. In theory we can use containerd’s CRI plugin to connect to it directly (instead of going through docker shim, dockerd and then reach containerd).
My proposition is to connect to containerd on newer Docker versions and keep the shim as long as we support old Docker versions.
I don’t have a strong opinion on how the shim is going to be nursed until it’s removed (could be a separate binary or remain in kubelet).
Pros:
Cons:
Have a wonderful day!
--
Rostislav (Ross) M. Georgiev
VMware Open Source Technology Center
From: kubernetes-sig-c...@googlegroups.com <kubernetes-sig-c...@googlegroups.com>
On Behalf Of Davanum Srinivas
Sent: Thursday, February 21, 2019 12:43 AM
To: Brian Grant <brian...@google.com>
Cc: kubernetes-sig-cluster-lifecycle <kubernetes-sig-c...@googlegroups.com>; kubernetes-sig-node <kubernete...@googlegroups.com>; kubernetes-sig-architecture <kubernetes-si...@googlegroups.com>; kubernet...@googlegroups.com
Subject: Re: Thoughts on separating a CRI for docker from Kubelet
Brian,
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-cluster-lifecycle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
kubernetes-sig-cluster...@googlegroups.com.
To post to this group, send email to
kubernetes-sig-c...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/CANw6fcEYZewq%3DSdRwAmx7tyhaAncnbrNiEKu1-j%2BsEyyRWs9oQ%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "kubernetes-sig-node" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To post to this group, send email to kubernete...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/MN2PR05MB6094F5A69E63103FBFD7B47AB37E0%40MN2PR05MB6094.namprd05.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/CAMK2eKJhqJhg%2BspV7yQj0uMDEKUkaTvUfCQnG-Z9xRnz-ibr3Q%40mail.gmail.com.