In partnership with
TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities, and articles.
👋 👋 A big thank you to today's sponsor WISPR FLOW
The AI notetaker that gets the hard words right
Your AI is only as good as what you feed it. Feed it a transcript with your product names, acronyms, and numbers spelled wrong, and you spend the afternoon hand-fixing the output.
Wispr Flow Notetaker uses your dictionary and calendar, so product names, acronyms, numbers, and uncommon names come out spelled right. It pops up when your meeting starts and captures Zoom, Google Meet, Teams, and Slack huddles with one click, no bot joining the call.
Then your meetings show up inside Claude or ChatGPT through the built-in connector. No copy paste. Try Notetaker free on Mac and Windows.
👀 Remote Jobs
Mozilla is hiring a Senior Software Engineer, Cloud Engineering
Remote Location: Worldwide
Protege is hiring a Forward Deployed Engineer, Healthcare
Remote Location: Worldwide
📚 Resources
Looking to promote your company, product, service, or event to 50,000+ Cloud Native Professionals? Let's work together. Advertise With Us
🧠 DEEP DIVE USE CASE
Kubernetes Container Runtime Internals Explained
When your Pod starts in Kubernetes, the container runtime is one of the first components to take action.
What Is a Container Runtime?
A container runtime is the system level component responsible for:
Pulling container images from a registry
Unpacking and mounting the image layers
Creating isolated environments using Linux namespaces and cgroups
Executing the container process using a low level runtime like
runcReporting back container state to the kubelet for health and lifecycle tracking
It sits underneath your Kubernetes worker node, abstracted behind the Container Runtime Interface (CRI), and acts as the bridge between kubelet and the host operating system.
Popular Container Runtime Types
Kubernetes supports several CRI compatible runtimes. Each has specific use cases and trade offs:
containerd (Default in GKE, EKS, k3s. Handles image pulls, snapshots, and lifecycle. Lightweight and production ready)
CRI-O (Kubernetes focused, minimal runtime. Used in OpenShift and upstream clusters for strict CRI compliance)
Docker Engine (Deprecated since v1.24. Still used for image builds but not for running containers in Kubernetes)
gVisor (Sandbox runtime offering user space isolation. Ideal for multi tenant or untrusted workloads)
Kata Containers (Uses lightweight VMs for stronger isolation. Suitable for high security environments)
Mirantis CR (Enterprise grade fork of Docker Engine with commercial support)
Note: Kubernetes did not “drop Docker,” it dropped the Docker Engine as a container runtime. You can still use Docker to build images, but use CRI-O or containerd to run them inside Kubernetes.
Let’s explore the two most popular runtimes used across managed Kubernetes environments and self hosted clusters.
CRI-O Runtime Flow
Containerd Runtime Flow
🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)
Upgrade to Paid to read the rest.
Become a paying subscriber to get access to this post and other subscriber-only content.
UpgradePaid subscriptions get you:
- Access to archive of 250+ use cases
- Deep Dive use case editions (Thursdays and Saturdays)
- Access to Private Discord Community
- Invitations to monthly Zoom calls for use case discussions and industry leaders meetups
- Quarterly 1:1 'Ask Me Anything' power session
