Live data from Hacker News

Show HN: Redspread (YC W16) – CLI to deploy Docker to Kubernetes in one command

github.com

11–20 of 44 posts

Re: Show HN: Redspread (YC W16) – CLI to deploy Docker to Kubernetes in one command

#12
post #10

Great to see such a great tool for deployments. Will you be adding support for managing multiple containers in a single deployment and scaling deployments up/down?

Hey thank you! So right now Spread supports deploying multiple containers in a single deployment. We want to let Kubernetes be Kubernetes as much as possible, so scaling deployments up/down (I assume autoscaling is what you meant!) is actually coming out in 1.2 - with a release date of March 7!

Re: Show HN: Redspread (YC W16) – CLI to deploy Docker to Kubernetes in one command

#14
post #8

So what exactly is Kubernetes?

Hey! Very simply, Kubernetes puts containers on servers. It takes care of a lot of logic around scheduling, networking, health checks (i.e. what happens if a pod goes down). I wrote a blog post that breaks down basic Kube architecture, if you're interested: https://blog.redspread.com/2015/12/31/basic-kubernetes-vocab... A little history - it's an open source project by Google, modeled after Google's infrastructure (B…

Blog post on Kube vocab is really clear and simple.. any other suggestions how to learn/read more?

Re: Show HN: Redspread (YC W16) – CLI to deploy Docker to Kubernetes in one command

#17

Why would I want to have a ctr file separate from my pod or rc?

Hey! Good question. So we're encouraging a .ctr file because we think container reusability will become really important, especially as more organizations share containers across teams.

We're playing around with this idea of embedding different kube objects and containers to construct applications across directories, so setting up directories with .ctr files will make the introduction of that feature pretty easy.

Re: Show HN: Redspread (YC W16) – CLI to deploy Docker to Kubernetes in one command

#18

Earlier quoted context omitted.

Hey! Very simply, Kubernetes puts containers on servers. It takes care of a lot of logic around scheduling, networking, health checks (i.e. what happens if a pod goes down). I wrote a blog post that breaks down basic Kube architecture, if you're interested: https://blog.redspread.com/2015/12/31/basic-kubernetes-vocab... A little history - it's an open source project by Google, modeled after Google's infrastructure (B…

Blog post on Kube vocab is really clear and simple.. any other suggestions how to learn/read more?

Thank you! So I've also compiled a list of K8s resources we found to be the most helpful: https://blog.redspread.com/2016/01/05/most-useful-kubernetes...

For example, the Godocs for Kubernetes are always kept up-to-date and are great for jumping around structs.

Re: Show HN: Redspread (YC W16) – CLI to deploy Docker to Kubernetes in one command

#19

Why would I want to have a ctr file separate from my pod or rc?

Hey! Good question. So we're encouraging a .ctr file because we think container reusability will become really important, especially as more organizations share containers across teams. We're playing around with this idea of embedding different kube objects and containers to construct applications across directories, so setting up directories with .ctr files will make the introduction of that feature pretty easy.

This is platform agnostic, correct? I can use AWS or DO, right?

Re: Show HN: Redspread (YC W16) – CLI to deploy Docker to Kubernetes in one command

#20

Earlier quoted context omitted.

Hey! Good question. So we're encouraging a .ctr file because we think container reusability will become really important, especially as more organizations share containers across teams. We're playing around with this idea of embedding different kube objects and containers to construct applications across directories, so setting up directories with .ctr files will make the introduction of that feature pretty easy.

This is platform agnostic, correct? I can use AWS or DO, right?

It works wherever you've set up a Kubernetes cluster! So as long as you have kubectl configured correctly, you're good to go.
Post reply on HN