Secure workloads
- Overview The ways to isolate and harden a workload on Syself Autopilot, from a shared kernel up to a per-pod VM, and where to configure each one.
- Run a workload in a user namespace Map container root onto an unprivileged host UID with one field, so a container escape does not land as root on the node.
- Set security contexts on a workload Where security contexts fit in the workload-hardening ladder, with a pointer to the security page that owns the fields, the restricted example, and Pod Security Standards enforcement.