Docker support is being deprecated in Kubernetes - but not just yet
Docker wasn’t supposed to be in there in the first place
When you purchase through links on our site, we may earn an affiliate commission.Here’s how it works.
The mention of Kubernetes dropping support forDockerin therelease notes for its latest release, raised a lot of eyebrows.
Atweetby the Kubernetes SIG Security co-chair, Ian Coldwater didn’t help matters, either: “Docker support is being deprecated in Kubernetes. You need to pay attention to this and plan for it. THIS WILL BREAK YOUR CLUSTERS.”
The move might come as a shock to anyone who’s been busy spinning up containers and not paying attention to the development of Kubernetes. But it really isn’t such a big deal.
Not the end of the world
In the release notes and in a follow upblog post, Kubernetes developers explain that all they are doing is deprecating Docker as a container runtime after v1.20.
If you’re wondering what’s a container runtime, it’s best explained in atrending tweetbyGoogleCloud Platform’s Staff Developer Advocate Kelsey Hightower: “Docker != Containers. There are container images. Docker can build them. There are container registries. Docker can push and pull from them. There are container runtimes. Docker is one of them. There are container processes. Docker can create them but Linux is still the boss.”
So all that has happened is that Kubernetes is deprecating (and will eventually remove) Docker as a container runtime in favor of runtimes that use the Container Runtime Interface (CRI), such as containerd and CRI-O.
For the end-users of Kubernetes there shouldn’t be much of afalloutof this move as the developers explain “Docker-produced images will continue to work in your cluster with all runtimes, as they always have.”
Are you a pro? Subscribe to our newsletter
Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!
However, if you’re rolling your own clusters though, you’ll need to make sure that you don’t use Docker as a container runtime going forward. If you do, you’ll get a depreciation warning with the current v1.20 release.
If you don’t want your clusters to break, make sure you switch to one of the compliant container runtimes before the runtime support for Docker is removed, which is currently planned for v1.22 due in late 2021.
All in all, this move is about enforcing best practices and little else.
Via:The Register
With almost two decades of writing and reporting on Linux, Mayank Sharma would like everyone to think he’sTechRadar Pro’sexpert on the topic. Of course, he’s just as interested in other computing topics, particularly cybersecurity, cloud, containers, and coding.
7 myths about email security everyone should stop believing
Best Usenet client of 2024
Professionals are facing “tech overload” as they try to juggle multiple devices in the workplace
