+1, great points. Thanks, David.
> On Dec 9, 2016, at 8:22 PM, 'David Oppenheimer' via Kubernetes user > discussion and Q&A <kubernetes-users@googlegroups.com> wrote: > > As an aside, comparing Mesos scalability to Kubernetes scalability isn't > really meaningful; you need to compare Mesos + a Mesos framework to > Kubernetes. For example, if you run Aurora on Mesos (which is what Twitter > does) then you will presumably be able to run clusters that scale up to 30k > bare metal nodes (I believe that's the cluster size they've said they run). > If you run a different framework, you will get different results. > > I would also caution in general against using Kubernetes-on-Mesos just for > scalability reasons. Kubernetes itself doesn't become more scalable when you > run it on Mesos. If Kubernetes scales to X nodes, Kubernetes-on-Mesos is not > going to scale to more than X nodes. To put it another way, if you have a Y > > X node Mesos cluster, then Y-X of the nodes will not be part of the > Kubernetes cluster. > > > >> On Fri, Dec 9, 2016 at 4:59 PM, Joseph Jacks <jacks....@gmail.com> wrote: >> To add to what Brandon just said, that flow chart on slide 39 is facetious, >> at best. You can absolutely run "legacy" apps on K8s as well, as long as >> they can be packaged in a container, they will run on K8s just fine. >> >> I've heard of a few folks running K8s on Mesos using the framework that >> David referred to, but nothing in a serious manner (certainly not production >> ready) and it says a lot that Mesosphere (the one main company >> commercializing Mesos) decided to not contribute to the project anymore and >> instead focus on making Marathon better. >> >> By far, the biggest emphasis people make where Mesos is supposedly a better >> fit over K8s is when you have a lot of "Bid Data" workloads: Spark, >> Cassandra, Storm, etc... the thing is, there are a number of companies >> running those applications on K8s. Support for data-intensive processing >> workloads on K8s is only getting better. See StatefulSets. >> >> Scale is certainly a consideration, but a ~5K node K8s cluster supported in >> a fully loaded ~1 second response time SLO for any API call (target for the >> latest 1.5 release) means that in order to achieve Twitter-scale with K8s >> (largest production Mesos user to my knowledge) all you'd need is ~20 >> clusters. I believe Twitter runs more Mesos clusters than this. >> >> HTH, >> JJ. >> >> >>> On Dec 9, 2016, at 7:32 PM, Brandon Philips <brandon.phil...@coreos.com> >>> wrote: >>> >>>> On Friday, December 9, 2016 at 11:06:51 AM UTC-8, kvch...@gmail.com wrote: >>>> On Thursday, December 8, 2016 at 9:30:03 PM UTC-8, David Oppenheimer >>>> wrote: >>>> > I know there are some people using Kubernetes-on-Mesos, but we haven't >>>> > really heard any details on the exact use cases they're addressing. >>>> > (Maybe someone on the mailing list who is using it will reply.) Here is >>>> > the press release from Mesosphere announcing it two years ago. >>>> > Mesosphere is no longer directly involved in the project, and it's part >>>> > of the "Kubernetes incubator" here. >>> >>> That flowchart is out of date. Kubernetes has been tested up to 2,000 nodes >>> and should support 5,000 hosts and beyond with the new etcd3 >>> --storage-backend: http://kubernetes.io/docs/admin/kube-apiserver/ >>> >>> Brandon >>> >>> >>>> > On Thu, Dec 8, 2016 at 8:42 PM, BYEONG-GI KIM <bg...@bluedigm.com> >>>> > wrote: >>>> > >>>> > Hello. >>>> > >>>> > >>>> > I'm wonder the exact purpose to integrate Kubernetes with Mesos, since >>>> > Kubernetes has already supported resource management & monitoring itself >>>> > as mentioned at http://kubernetes.io/docs/user-guide/compute-resources/ >>>> > and http://kubernetes.io/docs/user-guide/monitoring/. >>>> > >>>> > >>>> > Could you explain what the benefits can be brought by using Mesos on >>>> > Kubernetes? Is it for resource management automation?... I'd really want >>>> > to know the current limitations of Kubernetes and what is solved by via >>>> > Mesos. >>>> > >>>> > >>>> > Thanks in advance. >>>> > >>>> > >>>> > Best regards >>>> > >>>> > >>>> > KIM >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > >>>> > You received this message because you are subscribed to the Google >>>> > Groups "Kubernetes user discussion and Q&A" group. >>>> > >>>> > To unsubscribe from this group and stop receiving emails from it, send >>>> > an email to kubernetes-use...@googlegroups.com. >>>> > >>>> > To post to this group, send email to kubernet...@googlegroups.com. >>>> > >>>> > Visit this group at https://groups.google.com/group/kubernetes-users. >>>> > >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> ------------------------- >>>> >>>> I got this link from Racksapce: >>>> https://www.socallinuxexpo.org/sites/default/files/presentations/SCALE_14_Docker_Kubernetes_Mesos_Compared_0.pdf >>>> >>>> >>>> Please refer to slid number 39 and draw your own conclusion. Hope this >>>> shed some light. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Kubernetes user discussion and Q&A" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to kubernetes-users+unsubscr...@googlegroups.com. >>> To post to this group, send email to kubernetes-users@googlegroups.com. >>> Visit this group at https://groups.google.com/group/kubernetes-users. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Kubernetes user discussion and Q&A" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to kubernetes-users+unsubscr...@googlegroups.com. >> To post to this group, send email to kubernetes-users@googlegroups.com. >> Visit this group at https://groups.google.com/group/kubernetes-users. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
