Live data from Hacker News

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

docs.docker.com

131–140 of 155 posts

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

#131
post #120

Earlier quoted context omitted.

minikube is a specific version/distro/packaging of kubernetes meant for testing on local laptop. Docker Swarm runs exactly the same way with exactly the same components and with the same ease on laptop as well as the cloud. TL;DR - you cant run minikube in production.

I see your point. For k8s production, you'd have to use a solution provided by the cloud operator, GoogleKE / AzureKS / AmazonKS / etc. Which leaves the on-prem cluster and/or baremetal hosted cluster uncovered. Not that I'm convinced it's worth running baremetal anything, you're likely to be less efficient than large cloud operators because of economies of scale. Nit: $ minikube get-k8s-versions The following Kubern…

I used this for baremetal: https://github.com/kubernetes-incubator/kubespray

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

#132

As I read through this all it feels sort of weird even typing it but I kind of hope Amazon or Microsoft buys Docker rather than Oracle, Google or IBM. I think Microsoft still employs thousands of great engineers and have been early embracers of containerization among the large companies out there and because Satya was a large part of growing Azure into what it is (IMHO a pretty solid set of services) it could make a…

I was wondering if you think the whole Docker inc is closing or something like that. Docker is only shutting down their cloud offering for Docker Swarm and I think it is to bundle their resources and focus on integrating Kubernetes.

I’m trying and failing to imagine a future where Docker achieves business success as a stand-alone entity.

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

#133
Long time docker user here.

Docker Cloud was getting worse and worse. Tutum (they acquired, rebranded and killed it) was great. But docker team just destroyed it.

That is a shame. Tutum was great since it scaled up and down very well. Nobody thinks about scaling down, but this is important in many ways.

Right now IMO: - Docker swarm - scales up and down ok. Had too many bugs with even on stable. - Rancher - fine, very good for medium deployments. - k8 - winner for larger scale but scales down badly.

This is really sad.

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

#134
post #117
post #109

Earlier quoted context omitted.

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

I get the impression that Nomad was never particularly alive to begin with, which is a shame since it seems better designed. But it doesn't have that "ZOMG Google has blessed us with the secrets of the borg" that DevOps crave.

Nomad was my choice for queue centric workloads, but it doesn't seem to fit the webserver / long living services as good as Kubernetes. I'm not sure, but I would think you could run Nomad and Kubernetes on the same servers, sharing the Docker runtime.

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

#135
post #117

Earlier quoted context omitted.

I get the impression that Nomad was never particularly alive to begin with, which is a shame since it seems better designed. But it doesn't have that "ZOMG Google has blessed us with the secrets of the borg" that DevOps crave.

Nomad was my choice for queue centric workloads, but it doesn't seem to fit the webserver / long living services as good as Kubernetes. I'm not sure, but I would think you could run Nomad and Kubernetes on the same servers, sharing the Docker runtime.

If you run two schedulers they don't have a correct view of available capacity. You can use Mesos as a meta-scheduler but that introduces more complexity.

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

#136
post #66

Earlier quoted context omitted.

Kubernetes had won the container scheduler wars. At GitLab we're all in on making a PaaS based on k8s and our CI/CD and the container registry that is part of GitLab.

> At GitLab we're all in on making a PaaS based on k8s This is very interesting. Could you talk more on this ? There is definitely space for an "opinionated k8s distro with batteries included". I have wished for Swarm to become this....

It is not a Kubernetes distribution. You can use any distribution or CaaS you want. The beginning of it is in GitLab Auto DevOps https://about.gitlab.com/2017/10/04/devops-strategy/

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

#137
post #93
post #66

Earlier quoted context omitted.

Kubernetes had won the container scheduler wars. At GitLab we're all in on making a PaaS based on k8s and our CI/CD and the container registry that is part of GitLab.

Interesting. Is there a blog post where i can read more about this?

https://docs.gitlab.com/ee/topics/autodevops/ and https://about.gitlab.com/2017/10/04/devops-strategy/

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

#138

I've been meaning to learn kubernetes for a while now having been a docker compose user for a few years. Swarm seemed super appealing due to easy migration and simplicity. Having gone through a few tutorials for Kube I still feel a little overwhelmed with the volume of configuration, and also how local development is meant to be done. This was always a very cool part of compose.

I found kubernetes up and running really helpful. Kubernetes the hard way was really useful, but a painful weekend.

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

#139
post #80

Earlier quoted context omitted.

Do you know if there are any good tools for migrating your manifest/compose yaml files to k8s, especially using more recent features such as configs and secrets?

There is kompose with a k: https://github.com/kubernetes/kompose

Doesn't seem to support some of the more recent features, such as secrets and configs :(

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

#140

We are extremely worried about the future of Docker Swarm as well. We love Swarm - but we are seeing most work out of the Docker team is to give a migration path to kubernetes. A huge number of docker swarm networking bugs are not being worked on. We will be happy if Docker talks about Swarm becoming a management UX for K8s - but we need visibility. These are production orchestration systems. The migration path is no…

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…

There were two swarm's, the swarm classic — which was okayy, & then the newer swarm Mode, introduced in docker 1.12. I'm not sure which one you refer to when you say v0.4. But swarm mode was good, extremely simple & worked well for the right workloads. Like most solutions it is not a silver bullet for every orchestration need, but worked very well in microservices, new-ish architectures. K8s is great too, but it seems like an overkill for a handful of services. Also setup of K8s used to be hard, especially HA. The learning curve is also quite steep. One of the features in swarm mode that makes docker swarm extremely intuitive — IPVS, is being incorporated in K8s. So I guess there has been some cross pollination on both sides. But I do not think the swarm mode is going to die anytime soon.
Post reply on HN