Live data from Hacker News

Do I Need Kubernetes?

mbird.biz

1–10 of 180 posts

Re: Do I Need Kubernetes?

#2
Honestly nobody needs k8s, but nobody really needs anything. If you know it and you know it suits your needs, then sure! Go for it! Have fun.

If you don't know it, then learn it first. Then you can properly evaluate whether it suits your requirements or not.

There's huge value in choosing something that your team already knows + is familiar with

I'd totally advocate for learning something new, but solving a business problem probably isn't the best time for this :)

I think the article gave a great overview though, and is perhaps a good way to decide what to learn next

Re: Do I Need Kubernetes?

#3
I only have one tiny detail: Bursty traffic means that your cluster needs to be able to deal with the peaks. If you running an on prem Kubernetes cluster, then there is no savings, unless you can use the capacity for something else during non peak periods.

The scaling, and potential savings is a cloud feature, not a feature of Kubernetes.

Re: Do I Need Kubernetes?

#5
Not a single mention of elastic beanstalk or App Engine? The best middle ground for small teams who just want one reliable website with minimal scaling (and who can't just choose a nom-aws service).

Re: Do I Need Kubernetes?

#6
> Run your applications in Docker from day 1 (with docker-compose it’s as valuable for dev as it is for production) and think carefully before letting your applications store local state.

I think this is the key take away for many startups. Get it so you:

    1. Have a single-command way to bring up your entire backend
    2. That command can run on your dev machine
    3. You document all of the settings for your containers and deps 

Once you have that in a docker-compose.yml file migrating to something like kube when you need health checks, autoscaling, etc is easy.

The only thing you must be critical of is bashing people over the head to make everything you run in your company run in this environment you've created. No special deployments. Establish 1 method with 1 tool and go from there.

Every company I've worked at I've brought a single command `docker-compose up -d` workflow and people were amazed by the productivity gains. No more remembering ports (container_name.local.company.com), no more chasing down configuration files and examples, no more talking to shared DBs, etc.

Re: Do I Need Kubernetes?

#7
> To make a cluster useful for the average workload a menagerie of add-ons will be required. Some of them almost everyone uses, others are somewhat niche.

This is the concern I have with k8s. All this complexity introduces operational and security concerns, while adding more work to do before you can just deploy business value (compared to launching on standard auto-scaling cloud instances)

Re: Do I Need Kubernetes?

#9
post #6

> Run your applications in Docker from day 1 (with docker-compose it’s as valuable for dev as it is for production) and think carefully before letting your applications store local state. I think this is the key take away for many startups. Get it so you: 1. Have a single-command way to bring up your entire backend 2. That command can run on your dev machine 3. You document all of the settings for your containers and…

Can I ask people who _don't_ use Kubernetes and maybe have architectures built on proprietary cloud services: how do you manage this?

Re: Do I Need Kubernetes?

#10

> To make a cluster useful for the average workload a menagerie of add-ons will be required. Some of them almost everyone uses, others are somewhat niche. This is the concern I have with k8s. All this complexity introduces operational and security concerns, while adding more work to do before you can just deploy business value (compared to launching on standard auto-scaling cloud instances)

Like most infrastructure work there is an upfront cost, but after paying that the result enables you to ship value faster and easier.
Post reply on HN