KEP-2221: Removing dockershim from kubelet

[Davanum Srinivas]

Folks,

It's still 1.23 cycle right now, but sending out a last call to completely remove dockershim from kubernetes/kubernetes as soon as master opens for 1.24 which seems to be approximately the first week of Dec at this point [2].

as they say "speak now or forever hold your peace" (or switch to [3]).

thanks,

Dims

[1] https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2221-remove-dockershim/README.md#dockershim-removal-plan

[2] https://www.kubernetes.dev/resources/release/

[3] https://github.com/Mirantis/cri-dockerd

--

Davanum Srinivas :: https://twitter.com/dims

[Davanum Srinivas]

Katie and fellow end user representatives!

Can you please pass this along to end users and avoid any last minute surprises?

These may be helpful to set the context:

- https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/

- https://kubernetes.io/blog/2020/12/02/dockershim-faq/

- https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/

thanks,

Dims

[Sergey Kanzhelev]

Hi,

Dockershim removal is important. The deprecation announcement was made
last December and there is a lot of information about it. It would be
great, however, if we can get more information on the migration
progress and plans.


Please fill out and help us distribute this form:

https://forms.gle/svCJmhvTv78jGdSx8


Also there are many other channels to provide feedback on potential
blockers of the dockershim removal, for example those SIG Node comms
channels: https://github.com/kubernetes/community/tree/master/sig-node#contact.

/Sergey

> --
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/CANw6fcEtFRj5FgQQSN2iM0aa-krRYB1J9Q0kmazCC96HTy0t1Q%40mail.gmail.com.

[Justin Cormack]

The recent Datadog survey https://www.datadoghq.com/container-report/ suggests that around 6% of organizations are using containerd, while the other 94% are still using Dockershim. So I would guess an amount of handholding will be necessary to help the migration to external Dockershim.

Justin

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/CA%2Bsr0%2BCDhwZUxBrcyE0QzRWf8iVoNYw%3Db91%2B%3DHNReeMrnpHNYQ%40mail.gmail.com.

[Mike Brown]

Definitely some misconceptions in the survey report. Should be more like 6% are configured to use containerd or crio directly for CRI pods and the other 94% are using kubelet’s built in default docker shim which uses docker+containerd…. And all the above can be configured to use both runc compatible and vm workloads. 

That said, agree more handholding docs will be helpful in completing the transition to external CRI implementations.  

Cheers, Mike

Sent from my iPhone

On Oct 16, 2021, at 9:42 AM, 'Justin Cormack' via kubernetes-sig-node <kubernete...@googlegroups.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/CALFF2qn4vMznuyW7aTjVXk%3DRa2KTqVDZFcryk2mxDt9ot%2BbtNg%40mail.gmail.com.

[Ricardo Rocha]

Will pass the form in the channels i know.

https://forms.gle/svCJmhvTv78jGdSx8

Quick feedback on the form - couple questions (version,
self-hosted/gcp/azure/aws/etc) i would need multiple options in our case, it
limits to one selection.

[Katie Gamanji]

Hello all, 

I have informed the End User mailing list of the dockershim removal and linked the questionnaire. Will let you know if there is any additional feedback.

Thank you,

Katie G. 

----

Katie Gamanji <kgam...@linuxfoundation.org>

Ecosystem Advocate, Cloud Native Computing Foundation

[Sergey Kanzhelev]

We only have 17 responses in the form so far. It would be great to collect more information if possible before the December deadline.