Hacker News new | past | comments | ask | show | jobs | submit login

A few thoughts...

1) Kubernetes is an infra platform for the ops in DevOps. If developers need to spend a lot of time doing Kubernetes it takes away from their ability/time to do their dev. So, there are a lot of platform teams who pull together tools to simplify the experience for devs or DevOps specialists who handle operating the workloads.

2) Kuberentes is, as Kelsey Hightower puts it, a platform to build platforms. You need DevOps/SREs to do that.

3) Kubernetes is hard. The API is huge and it's complex. The docs are limited.




I've said it before, and I'll say it again: Kubernetes is hard, huge, complex because it solves hard, huge, complex problems. Or tries to anyway.


The corollary of course is that if you don't currently have hard, huge, complex scalability problems, well, you do now...


Yup. If the org in every aspect is not ready for scale, stick to simpler solutions.


  > 3) Kubernetes is hard. The API is huge and it's complex.
  > The docs are limited.
Eh, I wouldn't go that far. Kubernetes has a lot of API surface for features that are useless (config maps), attractive nuisances (CRDs, packet routing), or outright dangerous (secrets). If you strip it down to its core mission of distributed process scheduling, the API is reasonable and the docs are extensive.

The biggest challenge with learning Kubernetes is that third-party documentation is largely funded by ecosystem startups flogging their weird product. It can be very difficult to figure out things like network overlays when there's so few examples that don't involve third-party tools.


I'm not sure how config maps are "useless". It seems to be a pretty important element of the platform in general.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: