1 views collected around this technical thread.
This article explains how the kubectl command interacts with the Kubernetes control plane, detailing one‑way HTTPS requests and two‑way WebSocket communications, and walks through the full execution flow of a kubectl exec command across kube‑api‑server, kubelet, and the CRI runtime.
Kubernetes 1.24 officially deprecated Dockershim in favor of containerd, explaining the reasons, the underlying container runtime components, the changes in pod creation workflow, the impact on users and operators, and providing practical migration steps and best‑practice recommendations.
Starting with Kubernetes v1.24 the built‑in dockershim is removed, requiring users to switch to a CRI‑compatible runtime such as containerd or CRI‑O—or install cri‑dockerd for Docker compatibility—while updating scripts, logs, and tooling, and using crictl or ctr for debugging and managing containers and pods.
This proposal introduces in‑place vertical scaling for Pods by making PodSpec resources mutable, extending PodStatus with ResourcesAllocated, adding ResizePolicy and Resize fields, and updating the CRI UpdateContainerResources and ContainerStatus APIs to support live CPU and memory adjustments without restarting containers.
This article provides a comprehensive overview of Docker's evolution, its modern architecture involving containerd, runc, and CRI, explains how containers are created and managed, and offers step‑by‑step instructions for installing, configuring, and operating containerd with the ctr command‑line tool on Linux.
This article explains the evolution of container runtimes, distinguishing low‑level and high‑level runtimes, introduces key projects such as runC, containerd, CRI‑O, and demonstrates practical demos and CRI integration with Kubernetes, providing code examples and architectural diagrams for cloud‑native practitioners.
The article explains the history of containers, the role of Docker and Kubernetes, why Kubernetes is deprecating Docker's dockershim, the timeline for the change, its impact on users, and the steps required to migrate to OCI‑compatible runtimes such as containerd or CRI‑O.
This article provides a detailed overview of Docker’s evolution, the role of containerd, runc, and CRI in modern container runtimes, explains how Docker delegates container lifecycle management to containerd‑shim, and offers step‑by‑step instructions for installing, configuring, and using containerd with its CLI tools on Linux.
The article explains the background of containers, the role of Docker as a runtime, why Kubernetes is deprecating Docker in favor of CRI‑compatible runtimes, the migration path, and what developers and cluster operators need to know to adapt to the change.
This article explains what containerd is, compares it with Docker, describes Kubernetes' CRI support, and provides step‑by‑step commands for using containerd via crictl, showing that migrating from Docker to containerd is simple and resource‑efficient.
Kubernetes has officially deprecated Docker support by removing the dockershim bridge, explaining that Docker lacks native CRI compliance, and recommends migrating to CRI‑compatible runtimes such as containerd or CRI‑O while clarifying the differences between CRI and OCI runtimes.
Kubernetes has removed Docker support by deprecating the dockershim bridge, urging users to adopt CRI‑compatible runtimes such as containerd or CRI‑O, and explaining the differences between CRI and OCI runtimes, their security implications, and migration recommendations.