When it comes to securing container runtime, Windows containers are a bit different than Linux containers. For Windows containers, the operating system uses a Job object (not to be confused with Kubernetes Job object!) per container with a system namespace filter for all processes running in a given container. This provides a logical isolation from the host machine that cannot be disabled. You can read more about the Windows container architecture in Chapter 1, Creating Containers.
This fact has a consequence: privileged containers are not available in Windows, though they are available in Linux. Additionally, with the incoming support for Hyper-V containers in Kubernetes, you will be able to secure the container runtime even more and enforce better isolation.
For Linux containers, you would consider using securityContext for a pod in order...
