Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I commented about DCOS vs Kubernetes many times before here on HN.

I had a production cluster running on mesos/marathon (mesosphere). Also have an open source project heavily invested in it [1].

Recently, I refactored the entire environment to work on Kubernets and the open source project is following it as well (It is basically a miror of my production ENV).

After this long story I will say this.

They are both hard to set up correctly, especially if you follow best-practices of closed networks and publicly accessed resources (VPN, Internet Gateway etc...).

Kubernetes has a lot of "force" around it right now with the community booming. Posts like this (with it's many problems), is somewhat of a proof becuase it shows a vibrant community around a project.

Kube is more stable from my experience.

Like you mentioned, I would not run Kube production on anything less than 200-250$ which means multiple masters and multiple slaves for the pod runners.

It's nice to run something cheap to check the capabilities but not more than that.

Regarding DO, I'm a big fan and run a lot of projects (personal) with them, for production grade stacks I would use AWS/Google/Azure, those give you better capabilities around hardening a cluster (security, networking) for production workloads.

[1] http://docs.the-startup-stack.com



this is very interesting! can you talk about the problems you found. Im not sure what you mean by pod runners.. are you referring to kubelet here?

we are considering a k8s based stack.. but have seen very few on-metal deployments with k8s.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: