(I work for GCP) It looks something like this: your container -> Compute Engine VM (GKE Node) -> container -> Borg The container on top of Borg is used for s

(I work for GCP) It looks something like this: your container -> Compute Engine VM (GKE Node) -> container -> Borg The container on top of Borg is used for scheduling and management. Joe's talk has a slide on this. As a GCP customer, you never have to worry about this or care about it, as it is an implementation detail. >"The isolation is not perfect, though: containers cannot prevent interference in resources that the operating-system kernel doesn't manage, such as level 3 processor caches and memory bandwidth, and containers need to be supported by an additional security layer (such as virtual machines) to protect against the kinds of malicious actors found in the cloud." As a GCP customer using GKE, your applications are separated from other GCP customer using VMs. However, if you want to run your OWN untrusted workloads, then in the past you would have to spin up a separate VM for untrusted workload A and a one VM for untrusted workload B. This sucks in terms of resource utilization. It would be better in many cases if you could run workload A and B on the same VM. That's where gVisor comes into play. your untrusted container -> gVisor -> Compute Engine VM (GKE Node) -> container -> Borg I hope this makes sense!