Hacker News Reader

Comment by otabdeveloper4 | Hacker News Reader

I've only played with k8s for like an hour in total, but it's pretty obvious to me that k8s fell very much victim to the second system effect.

It's an insanely complex solution to a very niche problem - scaling stateless web app backend nodes written in scripting languages.

Stray even a little bit off the garden path and you start feeling pain.

View on HN

You only played with it an hour and you reached all these conclusions?

Yes, because I saw that my (not-so-niche, actually) use case wasn't even considered, and "noped" outta there as fast as I could.

What was your use case?

Some ETL logic packaged in Docker containers with a bit of simple scheduling and orchestration.

K8s sounds like a good idea on paper - you get reproducibility and resilence "for free" - but then I found out I have to effectively roll my own everything with k8s anyways and went with Jenkins instead.

> scaling stateless web app backend nodes written in scripting languages

K8s solves a far wider problem space. Need to run a data store? Use a StatefulSet and PersistentVolumes. Need an occasional task? Jobs and CronJobs. Need to know what's happening? Metrics and logs have APIs. Load balancing? Ingress? Firewalls? Security?

If someone knew nothing of operating systems other than a class on MINIX, I suspect running a massive datacenter would be easier with k8s than running a medium system of debian boxes.

Reply on news.ycombinator.com