For the love of god startups don’t need Kubernetes setup. Stop doing this, please.

Choose serverless instead; document your code while you’re working on it; skip retarded unit tests and do integration tests.

Not hard. Why over complicate everything.

Speaking my language.

Someone heard a buzzword! Seriously though, I can’t think of a single reason why a *startup* should go for containers, let alone Kubernetes, since I assume that as a startup you can purposefully architect from the scratch to the cloud… serverless should be the default way to go, and services over code as well, where you can.

I think it wholly depends on the project, not the form of the entity developing it. But generally, Kubernetes is overhyped and overused for projects that could have a simpler architecture.

I know this is a generalization that also I agree with, but I joined a startup as a lead infrastructure dev about 6 months ago.

We use k8s for managing all services, and we could not do it without it.

So while most projects don't need it, when you do it's one of the most powerful tools you have.

@PonySlaystation ALSO speaking my language. K8s is actually *really* good at what it does. You just better be damn sure your application needs it for what it does and not somebody's resume.

I wholeheartedly disagree with that statement. Only rule I follow: use tools that suit the job/situation.
Never use a tool for the sake of using a tool, in size or age of company.

Startup can have quite a big IT department.
Startup might require on site hardware first but later moving to the cloud or other way around. Kubernetes really helps with that. But only if this complexity is warranted at the start.

@yehaaw There is no instead here, you can have serverless k8s

@PAKA You definitely can. That’s not the point. Over engineering in startups is.

@PAKA And focusing on wrong things.

@yehaaw I won't argue with that part