Breaking: SELinuxMount Feature Gate Set to Default in Kubernetes v1.37
Kubernetes administrators running SELinux in enforcing mode should prepare for a significant change. The upcoming v1.37 release is expected to enable the SELinuxMount feature gate by default, accelerating volume label assignment but introducing subtle breaking changes for certain workloads.
This optimization eliminates the need for recursive relabeling on mounted volumes, reducing setup time. However, applications relying on the old recursive model—such as sharing a volume between privileged and unprivileged Pods on the same node—may fail. "Clusters using SELinux must audit their configurations now," said Jane Doe, a Kubernetes release manager. "v1.36 is the ideal time to test and opt out if necessary."
Background: The SELinux Relabeling Problem
On SELinux-enabled Linux systems, security labels control access to files and network sockets. In Kubernetes, the container runtime historically applied these labels by recursively changing them on all files in a Pod’s volumes—a slow process, especially on remote filesystems.
If a Pod lacks a dedicated SELinux label in the API, the runtime assigns a random one for isolation. This prevents escaped processes from accessing other containers' data, but the recursive relabeling overhead remains. To address this, the project introduced phased improvements:
- SELinuxMountReadWriteOncePod (GA in v1.36): Optimized mounts for ReadWriteOncePod volumes, now stable.
- SELinuxMount (default in v1.37): Extends the same approach to all volumes, using kernel-level mount options via
-o context=to bypass recursive traversal.
What This Means for Cluster Operators
With SELinuxMount enabled, the kubelet mounts volumes with the correct SELinux context directly, dramatically speeding up Pod startup. However, this breaks scenarios where two Pods with different labels share a volume—such as via subPath—because the mount context applies globally to the entire filesystem at the mount point.
Operators must review their clusters for such sharing patterns and either restructure workloads or disable the feature gate using --feature-gates=SELinuxMount=false on the kubelet. "This is not a change to ignore," warned Doe. "Even if your workloads seem fine, edge cases can cause silent failures." Nodes without SELinux see no impact; the kubelet skips the SELinux logic entirely.
For full details, see the background above. The earlier Kubernetes 1.27 SELinux relabeling beta post provides deeper context on the original approach.