News for hackers. Stuff that matters.
Re:Docker by G3rn0ti on Sunday March 26, 2023 @02:28AM (#35311656)
> then Swarm was supposed to

> be the cashcow that turned

> that into cashflow. And then

> k8s happened.

We are still using Docker Swarm in production. It seems to be working fine so I always wondered why it never took off. But I am not a Devop. Can sb please give some insight on why kubernetes took off instead and why Dock Inc. failed with its cloud product?

Re:Docker by BossingAround on Sunday March 26, 2023 @02:37AM (#35311701)
Good question, I'm also interested in the answer. Probably has something to do with K8s being backed by Google, which has battle tested it in the form of their internal Borg infrastructure.
Re:Docker by hayst4ck on Sunday March 26, 2023 @02:52AM (#35311784)
My understanding is that k8s was definitely never used internally at google (at least at the beginning). They may have learned some lessons from Borg, but k8s is very very much not Borg nor a Borg component. I remember lack of battle testing and architectural differences being a key criticism when k8s was released.
Re:Docker by KineticLensman on Sunday March 26, 2023 @03:04PM (#35318214)
Z
Re:Docker by mmtmn on Sunday March 26, 2023 @03:11AM (#35311897)
Kubernetes took off because it was an open-source project that had the backing of major cloud providers like Google, Microsoft, and Amazon. The project was started by Google and was based on their internal container management system called Borg. Kubernetes was designed to be highly scalable, flexible, and easy to use, which made it popular among developers and enterprises alike.

On the other hand, Dock Inc. failed with its cloud product because it was not able to compete with other cloud providers like Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform. Dock Inc. was a startup that was focused on providing a container-based platform for building and deploying applications. However, it was not able to gain traction in the market, and its product was not as mature or feature-rich as those offered by larger cloud providers.

Another reason for Dock Inc.'s failure could be a lack of community support. Kubernetes has a strong community of developers who contribute to the project and help improve it. This has helped to build a robust ecosystem of tools and services around Kubernetes, which has made it easier for developers to adopt it. Dock Inc. may not have had the same level of community support, which could have made it harder for them to gain traction in the market.

Re:Docker by syspec on Sunday March 26, 2023 @04:29AM (#35312343)
Clearly written by chat gpt
Re:Docker by akvadrako on Sunday March 26, 2023 @04:17AM (#35312278)
k8s is basically a standard interface for cloud providers, where you can define load balancers, persistent volumes, certificates, etc. in addition to jobs and services. It has a well thought out declarative language that maps well to how ops runs things at scale.

There are quite a few optional tools built on the k8s model, like service meshes or tools to orchestrate a postgres cluster.

Swarm is a small piece of that, the scheduling system, and you have to run it yourself. It's really not comparable.

Re:Docker by ransom1538 on Sunday March 26, 2023 @07:43AM (#35313419)
"Can sb please give some insight on why kubernetes took off instead and why Dock Inc. failed with its cloud product?"

IMHO, Google did something smart/evil here. Google did not use the docker-compose style yaml files for k8s configurations. This turned into a big deal. If you have a docker-compose file and want to run it in k8s - you cannot. So you need to make a decision: go with docker-compose yamls which has no place to be hosted except swarm OR go with k8s yaml style and be able to run it on aws,gcp, etc.

Re:Docker by harha_ on Sunday March 26, 2023 @08:00AM (#35313535)
Swarm is fine but k8s is a lot more advanced. I've used both and now that I understand k8s, I would choose it over swarm any day. Microk8s is neat if you want a lightweight cluster.
Re:Docker by tartieret on Monday March 27, 2023 @04:29PM (#35332030)
I still use Docker Swarm in production, but the main issue is the lack of support from cloud provider and tooling. For instance, there is no good solution like ArgoCD for continuous deployment and updating your stacks. In addition, if you want to be able to automatically add a new node to the cluster, you basically have to write some infrastructure code by yourself. This makes infrastructure as code / configuration as code a pain, and these things are required to be compliant with stuff like SOCII