<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RuntimeClass :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/runtimeclass/index.html</link><description/><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0</copyright><lastBuildDate>Wed, 28 Oct 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/runtimeclass/index.xml" rel="self" type="application/rss+xml"/><item><title>Sandboxed containers with gVisor and RuntimeClass</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/gvisor/index.html</link><pubDate>Wed, 28 Oct 2026 09:00:00 +0100</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/gvisor/index.html</guid><description>Author: Fabrice JAMMES (LinkedIn).
Objective Download a binary and verify it with its checksum Install the gVisor runtime (runsc) on the nodes, and declare it to containerd Run a pod in a sandbox with a RuntimeClass, and see the difference with a normal pod A normal container shares the kernel of the node: a kernel exploit from a container gives the node. gVisor runs the container on top of a kernel written in Go (the Sentry), which runs in user space and handles the system calls of the container: the kernel of the node only sees a few, filtered system calls of the Sentry.</description></item></channel></rss>