To clarify- Kubernetes as typically configured has strong multitenancy for API access control. However, other aspects of multitenancy such as memory, CPU (inclu

To clarify- Kubernetes as typically configured has strong multitenancy for API access control. However, other aspects of multitenancy such as memory, CPU (including cross-container data leakage), network, disk/filesystem are implementation dependent. The most common implementations (i.e. on Linux with Docker or containerd) provide generally weak or no control over each of these aspects. Some (Kata Container, Firecracker) have stronger controls, and some (Windows Server Containers) have even fewer controls. But for complete separation, either separate worker node groups with very strict, limited API access or separate clusters are needed.