Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I find it a bit contradictory to argue for boring technology and operate it with Kubernetes at the same time.


Kubernetes is used by thousands of companies, big and small, has been around for more than 6 years, and is well supported by various cloud providers. There's lots of documentation and forums online with plenty help.

It'd argue that there's more documentation available than for any home-grown deployment system.

That's why I consider it battle-tested for my purposes.

Also, the post explains that boring does not necessarily mean "old". It's about using what you know best.


> There's lots of documentation

Sure.

> battle-tested

Not at all.


k8s is boring at this point. You can purchase it as a managed service from the biggest vendors on the planet and reliably find people with 2-3 years experience working with it.


I have worked with EKS for the most when it comes to k8s and I don't find it as smooth as AWS's other offerings. Check the upgrade guide https://docs.aws.amazon.com/eks/latest/userguide/update-clus... There is still quite a lot of engineering needed even when using a "managed" service.


To be fair EKS is bottom of the barrel. Things are a lot better in GKE land.

AWS never wanted EKS to be a thing, that is why it's overpriced and not very good.

Unfortunately ECS is crap and Fargate can't save it at this point.

Hopefully they get over that soon and make the industry standard stuff like EKS and MSK good and actually price competitive with running it yourself (accounting for ease of management premium ofc).


The post describes a handful of technical decisions with no common thread, really.




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

Search: