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! :)

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

Basically tooling that takes you from a collection of images and service/replication controller definitions to a running stack. The main questions we ended up trying to answer were things like: how many nodes in the cluster? What machine type? Which images need to be deployed and which tag of each image? Which k8s objects need to be created and what customization has to be done to them in the process? We ended up with a combination of make files and shell scripts that defined all these aspects of a specific running cluster, created the cluster, deployed the images, created the services, etc.

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!

That's the trick. I was expecting some sort of message to tell me where to find the service.

Mattermost, Postgres and Kubernetes set up in minutes. Great work.

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

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

Convox team member here. Big fan of the Redspread team too :)

As Mackenzie says, we do have very similar goals of making deployments easy. I think we're also seeing the problems in a very similar way.

Most devs and teams want to focus solely on writing, deploying and maintaining their business apps and services. There are a lot of technical details to sort out for any container orchestration system, so we're building great tools that make these low level challenges vanish.

Redspread wants to be the Kubernetes experts so you don't have to be. Same with Convox and AWS.

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.

Thanks for the info. I can definitely see the need for something like this at my work. Hope it works out for you guys!