Eh, maybe. I see your point. The thing is, Mesos on it's own isn't k8s. Mesos is a scheduler. k8s is a full stack. So it's always been a bit off to fully compa

Eh, maybe. I see your point. The thing is, Mesos on it's own isn't k8s. Mesos is a scheduler. k8s is a full stack. So it's always been a bit off to fully compare the two. If your system fit clearly within what k8s did well, then you were fine and the stack worked. If you had a more complicated architecture with parts that didn't play well with containers or k8s' scheduling model, life became pretty difficult. That's one reason I liked Mesos is you could build the stack you needed for _your_ infrastructure. Granted, I don't think most shops had the kind of problems that warranted Mesos, let alone k8s (that's still true today). But k8s is "good enough" for lots of problems and understandably that's where the community went.