Isolating Pods with RuntimeClass in Kubernetes
Kubernetes’ RuntimeClass is a node-level resource that lets you specify which container runtime handles a Pod’s containers. By default, Kubernetes uses your cluster’s primary runtime (e.g. runc). With RuntimeClass you can opt particular Pods into alternative runtimes—such as gVisor or Kata Containers—that provide stronger isolation or specialized sandboxing. This tutorial walks through configuring two popular sandbox runtimes on containerd, defining RuntimeClass objects, and launching Pods with custom runtimes.
Keep reading with a 7-day free trial
Subscribe to Pods & Pixels to keep reading this post and get 7 days of free access to the full post archives.