Linux user namespaces isolate user and group identifiers (UIDs and GIDs) within containers, preventing lateral movement and enhancing host isolation.In Kubernetes 1.30, user namespaces are moving to beta for all pods.User namespaces map container UIDs/GIDs to non-overlapping, unprivileged ones on the host, limiting access to host resources.Without user namespaces, containers running as root have full privileges on the host, potentially enabling container breakouts.User namespaces mitigate the impact of container breakouts by limiting host file access and reducing privileges.Kubernetes 1.30 introduces custom UID/GID mapping ranges and enforces support for user namespace features in container runtimes.A CVE-2024-21626 demo illustrates how user namespaces mitigate this vulnerability by restricting access to host files.Linux kernel version 6.3 or greater is required, along with compatible container runtimes (CRIO with crun 1.9 or greater, or Containerd 2.0).Containerd 1.7 has experimental user namespace support for Kubernetes 1.25 and 1.26 but has limitations that may affect production use.Contact SIG Node for involvement through Slack, mailing list, or directly via GitHub or Slack.