| ▲ | tptacek 2 hours ago | ||||||||||||||||||||||||||||||||||||||||
If you're segregating internal workloads, by all means use nested virtualization on EC2 or DO or something. Your threat model is different and you probably have a lot more room to maneuver when a KVM escape is announced, because you have some level of trust in all your workloads. If you're running multitenant for mutually-untrusting customers, that excuse goes out the window. | |||||||||||||||||||||||||||||||||||||||||
| ▲ | JoshTriplett 2 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||
One distinction I'd make as well is "are you running more than one customer's workload on the same system" (yikes, don't), vs "are you using nested virt as additional protection rather than running the customer workload directly on an instance, but one instance only gets jobs from one customer". | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||