91–100 of 155 posts
Earlier quoted context omitted.
Who’s beating them? Amazon?
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.
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....
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
It's not a completely fair comparison since we also were able to offload persistent storage to Google Cloud, which is one of the harder problems IMO.
I think Mesos has improved since then, but it always felt like they were a bit behind.
In general Kubernetes feels like it is designed by people with relevant experience. Especially compared to our earlier experiments with Docker Compose files. People are praising their simplicity, but they left us solving a lot of hard problems that Kubernetes solves for us better than we could have done.
Earlier quoted context omitted.
Who’s beating them? Amazon?
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.
Earlier quoted context omitted.
I had to make a decision for an orchestration tool a few weeks ago and I went with K8s. One of the main reasons was that even Docker advertises it on its website and with Docker for Mac. I expect Swarm support to be canceled in a not so distant future and I cannot rely on a tool with an unclear future. Which is a pity because I really liked Swarm for its simplicity. Side note: I am also concerned about Docker in gene…
I'm not sure who's going to beat Docker. Docker is central to most orchestration tools so as long as they make money someplace with their central services, they should be fine.
Docker the company have few options to monetize on Docker the software when it becomes commoditized. They seeminly chose the Enterprise way, which consists of pretty orchestration tools and integrations with Active Directory. (A perfectly valid option, which worked out well for VMware.) That's a dead end now that Kubernetes won container orchestration. It will be interesting to see where they will go next.
Earlier quoted context omitted.
but why? The whole point of containers is that they are ephemeral and can be booted up quickly anywhere because you statically link the whole fucking OS?
The APIs of platforms are often totally different. If you went to docker cloud for its simplicity and now have to move to AWS/GCP/Azure/etc. and don't have a dedicated DevOps that knows one of those platforms already, you have no choice other than taking a developer working on features and putting them on learning the new API in a few weeks including testing. ~8 weeks is not enough for that if you are a cash-strapped…
Docker the file format/command line syntax/etc will long outlive Docker the company Kubernetes “won” so now the competition has shifted from who can innovate to who can execute and operate.
Genuine question - what makes you think that Kubernetes has won?
Earlier quoted context omitted.
> Google Reader It still hurts.
It was the day RSS died for me
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…
I had to make a decision for an orchestration tool a few weeks ago and I went with K8s. One of the main reasons was that even Docker advertises it on its website and with Docker for Mac. I expect Swarm support to be canceled in a not so distant future and I cannot rely on a tool with an unclear future. Which is a pity because I really liked Swarm for its simplicity. Side note: I am also concerned about Docker in gene…
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…
i would encourage you to try Swarm. Its brilliant in its simplicity. I think Docker product marketing and customer success basically sucks. But Swarm as a product has been really, really nice. And yes I continuously evaluate kubernetes and swarm side by side. You can get a swarm cluster running in less than 10 minutes on your local laptop after "apt-get install docker-ce". To run k8s, you will need to first muck abou…
$ brew cask install minikube
$ minikube start