3 ms·
Er, any links about the Kubernetes changes? They spent multiple releases adopting and moving to CRI. Meaning any CRI implementation can be used in his where doc
by colemickens 8y ago
Er, any links about the Kubernetes changes? They spent multiple releases adopting and moving to CRI. Meaning any CRI implementation can be used in his where docker(shim) was previously used. This includes -- containerd, crio, kata, pouch, gvisor, and at least three more whose names I forget.
Hardcoding another container runtime would be disappointing to see and highly surprising.
Also, since no one anywhere in this thread is talking about it... You can get Dockers container execution engine without any of the "docker". Docker has spent significant time and presumably money splitting out `containerd` and I'm surprised it's not mentioned in this thread so far. It's compatible with Kuberenetes CRI, etc, etc.
- jchw 8y agoSorry, what I meant was that the default CRI implementation would be based on containerd. This is as I understood it as an outsider and may not be true. edit: Here's an actual link. https://kubernetes.io/blog/2018/05/24/kubernetes-containerd-integration-goes-ga/ https://kubernetes.io/blog/2018/05/24/kubernetes-containerd-...