kubernetes

Leading up to Kubernetes v1, getting set up was quite painful but the api is now stable.

It turns out Kubernetes master is a single node currently which means they haven't built high availability into the master at all...

This is not to say that Kubernetes is bad but … it's a commitment which isn't appropriate for everyone.

Well, yes, because for one thing, Kubernetes (if done correctly) provides HA/failover that did not previously exist.

It would be nice if kubernetes would adopt some of hashicorps stuff like consul, templates, and vault.

One of the more compelling features is one-step cluster package installation (ex: dcos package install kubernetes).

But when you consider a kubernetes cluster of docker containers that you never SSH into...

There's already a few topics on the mailing list about etcd losing its data and Kubernetes doesn't know how to recover.

So if you invest in Kubernetes and later want to take advantage of Mesos you can lift up k8s and put Mesos underneath.

I'm not aware that kubernetes integrates with this stuff in any way or provides a sufficient alternative.

My company is exploring our options in the container orchestration space and have been testing out kubernetes on aws in the past week.

Speaking mainly from experience, kubernetes isn't that hard to get set up.

Moreover, Docker / Kubernetes aims to solve the problem of building services that can easily scale to hundreds of machines and hundreds of millions of users, "Google-style".

Kubernetes secrets are a really great solution to this problem.

I can't speak for Kubernetes, as I haven't tried it, but we've just started the migration to using Mess/Marathon for infrastructure management.

This is the perfect role for somebody that loves Go, Docker, Kubernetes, Mesos, Hadoop/Spark, and distributed systems.