mfburnett

oof this is very unfortunate; we're also signed up for Azlo through Stripe Atlas

This University of Maryland student made this experimental organ using 49 back-driven stepper motors this summer - absolutely incredible

Probably the simplest/fastest setup guide I've seen to go from zero to a running Kubernetes cluster on OS X

And if anyone has any questions about using Spread with Gitlab CI to deploy to Kubernetes, let us know! (Redspread cofounder here.)

Thanks! :)

Fixed this issue with the message showing "waiting for load balancer" - now it returns the NodePort!

Thanks! What else would you want to see in a general use framework?

Very cool - thanks for sharing!

Yes so the "Waiting for load balancer deployment..." is a confusing message leftover from its original use for a remote cluster - we're fixing it asap, but it actually has already worked. Go ahead and get your Docker daemon IP and then grab the NodePort with `$ kubectl describe services/mattermost-app` and put in the IP:NodePort into your browser to see the Mattermost instance running.

The easiest way to install kubectl is actually to install gcloud first (https://cloud.google.com/sdk/#Quick_Start) and then install kubectl with `$ gcloud components update kubectl`

Thanks for bringing this up!

Love the Convox team! We're both trying to make deploying to our respective orchestrators (EC2 for Convox and Kubernetes for Redspread) easier.

Hey, thank you! We're building out "git for deployment" - starting with a series of commands to make it easy to deploy to and develop with Kubernetes, and working our way to application versioning (capturing and versioning the expected state of an application before it's deployed by an orchestrator, like Kubernetes). Then, we'll make money on the "Github" - collaborative deployment tools built on top of our versioning workflow.

Thank you! Yes, we're approaching it with a Unix philosophy :)

So backstory: first we went with "omnikube", but that name was already taken and caused some early and funny confusion (see our issue on local development). But monokube and hyperkube were already taken, so localkube was our compromise.

Of course - glad you think so! That's exactly why we built it.

Oh haven't seen this! Is it compatible with Kubernetes 1.2? Not a huge fan of scripting - we think it breaks the abstraction of a container.

Previous options were either figuring out how to set up hyperkube (which was kind of a pain) or monokube. Neither were set up for Kubernetes 1.2 or had good networking options!

Hey everyone, cofounder of Redspread (YC W16) here. We just shipped Localkube, local development with Kubernetes. You can set up a full configured Kubernetes 1.2 cluster on your local machine in one command with Spread, our command line tool. Localkube has everything you need for networking, and is a single executable, single container, and single process.

It's the easiest way we've seen to set up a Kubernetes cluster and get started immediately.