kubo-deployment

Disclosure: I work for Pivotal, which competes with Mesosphere in this arena. Read with discretion. If shilling persists, consult your techcrunch. With that out of the way: you should try Kubo. Google & Pivotal have been working on Kubo[0] to make the management of Kubernetes easier by using BOSH as the deployment/update/repair system. You make deployments by editing a yaml file. Or, better yet, but having a tool edit the file for you as part of a structured CI/CD pipeline (I've seen both and I am a fan of the latter). BOSH works at the IaaS layer. Insofar as you mean "spin up and down VMs", Kubo is well-suited for that exact problem. You also get a bunch of upgrade and self-healing stuff for free. Pivotal is also adding a commercial offering based on Kubo, PKS[1], which has been built with Google[2] and VMWare[3]. You might not need it f

I'm putting in a word for Kubo[1], which makes the scaling easier. It is however still manual unless you build some other automation around it. [1] https://github.com/cloudfoundry-incubator/kubo-deployment Disclosure: I work for Pivotal, we built Kubo with Google.

If you need a management system that's not tied to AWS, I'd recommend folk look at Kubo. We (Pivotal) and Google have been working on it for a while now. https://www.youtube.com/watch?v=uOFW_0J9q70 for the motivation (tl;dr Kubernetes solves container orchestration, but doesn't solve its own management). https://github.com/cloudfoundry-incubator/kubo-deployment for the main repo. Disclose: I work for Pivotal.

> The rest of us still need to do a bit of work to find/adapt/build our own. I usually recommend people just take an existing PaaS and run with it. I'm wildly biased in this regard because I work on one as my day job. Also because rolling your own is hard. Really really hard. We have literally hundreds of engineers in dozens of teams, and that doesn't count the engineers our partners have assigned. We've been cranking for years. It's just a lot of hard engineering for stuff you don't see until it arrives, and arrives unpleasantly. Kubernetes makes it a lot easier, especially if you need lots of flexibility, but it still leaves you to assemble a lot of parts and management is left very much as an exercise for the reader. If you build on Kubernetes, may I recommend Kubo[0] to manage it? We built it with Google, but because it's based on BOS

> When I used kube in 2016 the cluster turnup support was bad; it seemed like you could use it managed in the G cloud but not anywhere else. You might like to look at Kubo[1], which was jointly built by Googlers and Pivots to make this more manageable. We built it based on requests from joint customers who want BOSH as their infrastructure-level platform and the choice of Cloud Foundry or Kubernetes for application-level platform. [1] https://github.com/pivotal-cf-experimental/kubo-deployment edit: forgot my usual disclosure. I work on Cloud Foundry for Pivotal, though not on Kubo.

I think a better link for the general HN crowd would be the deployment repo: https://github.com/pivotal-cf-experimental/kubo-deployment