News for hackers. Stuff that matters.

A comment on /story/39313623. Parent comment

Re: by Spivak on Saturday February 10, 2024 @12:59AM (#39323985)
I think they're more getting a k8s requiring a whole mess of 3rd party code to actually be useful when bringing it to prod. For EKS you end up having coredns, fluentbit, secrets store, external dns, aws ebs csi controller, aws k8s cni, etc.

And in the end it's hard to say if you've actually gained anything except now this different code manages your AWS resources like you were doing with CF or terraform.

[ Parent | on HN ]
Re: by mschuster91 on Saturday February 10, 2024 @06:08AM (#39325276)
We have all of that neatly extracted into a Terraform module. Write it once and now EKS clusters are essentially disposable.
[ Parent | on HN ]
Re: by Solvency on Saturday February 10, 2024 @10:15AM (#39326692)
You just added yet another Thing in that huge pile of things representing millions of lines of code. That's the point.
[ Parent | on HN ]
Re: by dvfjsdhgfv on Saturday February 10, 2024 @12:12PM (#39327999)
Everything we run our workloads on is based on millions of LoCs, whether it's in the OS, in K8S, in is built-in or external kinds. If you decide to run K8S in AWS, you'll be better of using Karpenter, external-secrets and all these things as they will make your life easier in various ways.
[ Parent | on HN ]
Re: by lijok on Saturday February 10, 2024 @05:45PM (#39330915)
Why is that inherently a problem?

How many LOCs in the linux kernel again?

[ Parent | on HN ]