Cluster and app management services in Docker Cloud are shutting down on May 21

Post by 112233 » Sat, Mar 24, 2018, 3:08 PM UTC

cygned wrote: post #36

scrollaway wrote: post #4

Earlier quoted context omitted.

> Twitter users People . People are up in arms. Anyway, yeah, that's insane. Even Google, who constantly shuts stuff down, usually does so with way more heads up. For comparison, Google Reader, a completely free service, shut down with 3.5 months advance notice. Google Wave got almost 6 months notice.

> Google Reader It still hurts.

Post by coredog64 » Sat, Mar 24, 2018, 3:26 PM UTC

gaius wrote: post #85

candiodari wrote: post #84

Earlier quoted context omitted.

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-…

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/

Post by manigandham » Sat, Mar 24, 2018, 3:45 PM UTC

eecc wrote: post #67

adamtulinius wrote: post #56

Earlier quoted context omitted.

Why did you pick Swarm for production? We followed Swarm from the beginning, but after a few releases at v0.4 it was clear not to ever use Swarm, and that it mostly was the Docker PR machine that made it sound nice, and not the actual features. Maybe it got better later on, but the first several Swarm announcements seemed really off-putting to me. We ended up on Mesos/Marathon, not that that has a bright future eithe…

Hmm, that k8s “has won” might make me a bit sad - not that I’ve ever gasped some fresh air out of the stranglehold of AWS - as I was impressed with Mesos. Can you share some 1st person opinions on Mesos, and where K8s is a step forward, backward or aside? TIA

Post by wmf » Sat, Mar 24, 2018, 4:06 PM UTC

jrs95 wrote: post #109

adamtulinius wrote: post #56

Earlier quoted context omitted.

Why did you pick Swarm for production? We followed Swarm from the beginning, but after a few releases at v0.4 it was clear not to ever use Swarm, and that it mostly was the Docker PR machine that made it sound nice, and not the actual features. Maybe it got better later on, but the first several Swarm announcements seemed really off-putting to me. We ended up on Mesos/Marathon, not that that has a bright future eithe…

Is HashiCorp’s Nomad in a similar position at this point? I really enjoy it’s (relative) simplicity.

Post by pacala » Sat, Mar 24, 2018, 4:33 PM UTC

gaius wrote: post #83

y4mi wrote: post #55

Earlier quoted context omitted.

> Well, "won" in quotes. I am not a k8s fanboy or anything, I simply observe that all the major cloud providers are offering managed k8s services that have superseded their own proprietary container-type offerings. For better or worse that's where the momentum is. If you wanted to containerize your stack right now, k8s then pick one of the big 3, seems like a safe bet. kubernetes got released more than a year earlier…

The only real upsite is how easy it is to install and maintain. But that's hardly important with pretty cheap hosted solutions around (at least cheap in comparison to hiring several SRE to maintain the cluster) Indeed - something like AKS can get you up and running very quickly, whereas as recently as 6 months ago unless you had a k8s wizard-guru on staff, there was no point in even trying to go it alone, esp. not in…