[candiodari]

It feels awfully 19th century though that despite k8s having "won", by far the biggest container schedulers by containers scheduled are, no doubt:

(I think this is the correct order, not 100% sure of course)

1) google borg (maybe omega) [1]

2) amazon ec2

3) whatever microsoft is using

(large gap)

4) all the rest of the world combined, a small portion of which is k8s

[1] https://www.quora.com/Does-Google-use-the-Open-Source-Kubern...

(one might even say [1] seems to imply it'll never happen, or at least take a very long time. Also if you read the papers it becomes very clear that "Google Borg" includes a lot of things these days at many levels, from custom ASICs, device firmware (as in standard device, google borg firmware), BIOS firmware, entirely custom sub-kernel code, custom kernels, custom userspace (ie. Google-specific libc that's not optional), ... all of these will turn out to have dependencies on eachother that have to be redone for k8s, could take a while to migrate over)

(although I have not read any papers on it (I'd love some though), I'd bet amazon is in a similar boat, and of course Microsoft is Microsoft)

[gaius]

EC2 is not a container scheduler - it's an IaaS for VMs. The Amazon container PaaS (ECS/EKS) is a layer on top of EC2. And that is being superseded by Fargate which will make the underlying EC2 invisible. If you need a Fargate-like capability now, Azure AKS does it.

See https://azure.microsoft.com/en-us/services/container-service... and https://aws.amazon.com/fargate/

[coredog64]

Fargate is expensive as hell for long running services. You should only be using it for something that creates value 100% of the time that it is running.

[candiodari]

So what is the EC2 container scheduler before Fargate called ? Any papers on it ?

[gaius]

ECS and EKS.