If you struggle with any of that (a lot of what you listed is not strictly necessary to running managed kubernetes, specifically EKS) you are also going to struggle with a lot of other things on AWS, or wrangling a VM setup at any kind of scale.

▲

paulryanrogers 4 hours ago | parent | next [-]

So they're holding it wrong?

▲

mschuster91 4 hours ago | parent | prev [-]

> a lot of what you listed is not strictly necessary to running managed kubernetes, specifically EKS

Oh it's not necessary per se but if you want to host a web service with any sort of state and not having to do stuff in parallel either by hand or by terraform, I'd consider the integrations pretty vital.

It's easy enough (well, it's still addons whose versions you have to keep updated each on their own) once it is set up, but getting to the point where you have something reproducibly running for the first time is annoying as hell.

	▲	zbentley 2 hours ago \| parent [-]
		I think the best supported and most mature pattern on most big cloud providers is precisely > do stuff in parallel either by hand or by terraform …specifically by terraform. Making k8s own the provisioning and management of external infrastructure on principle (as opposed to when that makes sense, e.g. load balancers/gateway/CSI providers) is not a good approach. Sure, it feels unified, but the cost of unification is incredibly not worth it.