-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extending dockershim removal to Kubernetes 1.24 instead of 1.23 #2767
Comments
#2221, from this link it sounds like dockershim will be removed in Kubernetes 1.24. But in Kubernetes blog (https://kubernetes.io/blog/2020/12/02/dockershim-faq/), dockershim will be removed in 1.23. Can anyone help to confirm? Thanks. |
To be clear, this means it will stay in tree for 1.23 but will be removed in 1.24? |
What happened to cri-dockerd / external dockershim? Just like cloud providers there's no requirement that CRI be in-tree, and there's no requirement to move to containerd speficially. |
Agree with @BenTheElder, I thought Mirantis was picking up stewardship of dockershim externally? |
yep, https://github.com/Mirantis/cri-dockerd is already out. |
@jsturtevant that's what the KEP currently as checked in says. I am debating if i should do a |
@dims i think it would make a huge difference for folks using DIY K8s if you can ship in 1.23 with docker support. |
+1 to this |
FYI - this should probably be closed, the associated tracking issue was updated with this information: |
@dims can you please confirm that if docker will stay as supported in 1.23 or it's only code in-tree and need to build by whoever wants to use it? |
@msjingli as of today the plan is for 1.23 will remain the same as 1.22 - please see details in https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2221-remove-dockershim/README.md |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):/sig node
The text was updated successfully, but these errors were encountered: