Menu

1 / 5

Kubernetes v1.37 Hardens the Volume You Already Mount

DEV Community: kubernetes·Taha Echakiri·2 days ago
#wulJU8iT
#devtokubernetes#devto#dev#kubernetes#mount
Reading 0:00
15s threshold

TL;DR

Kubernetes v1.37 ships two storage-security features: emptyDir permission modes and bind mount options (announcement).

bindMountOptions puts noexec , nosuid and nodev on the bind mount any volume creates inside a container; mode sets how an emptyDir is created instead of the hardcoded 0777.

Both are Alpha behind VolumeBindMountOptions and EmptyDirVolumeMode gates on the API server and kubelet.

Netics' take: the deepest container security gap was never the image — it was the writable volume; these flags close the path where a compromised process turns scratch space into an executable.

Practical move: enable the gates on one node, apply noexec / nosuid to emptyDir and /tmp mounts, and set 01777 on shared workspace volumes.

Reproduction of the official Kubernetes blog post "Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions" (September 16, 2026); source: kubernetes.io/blog

The most common writable volume had the least control

Here is the quiet fact…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.