News for hackers. Stuff that matters.
Re:What we learned after a year on Kubernetes by nuker on Thursday September 17, 2020 @04:59AM (#24502506)
> I learned not to use it and wait until the k8s fad goes away.

Yup, pretty happy with our move from k8s to ECS. Almost there.

Re:What we learned after a year on Kubernetes by Keycap on Thursday September 17, 2020 @07:47AM (#24503433)
You are basically using a very similiar tool/workflow just as a managed service from Amazon with a hard dependency.

This 'k8s' fad is the open source version of what you are using.

Its like you would say 'monitoring is a fad' we migrated away from monitoring and are now using amazon CloudWatch and are super happy with it.

Re:What we learned after a year on Kubernetes by nuker on Thursday September 17, 2020 @08:04AM (#24503561)
> This 'k8s' fad is the open source version of what you are using

That would be AWS EKS. ECS is very different beast. Wins big in infra-as-a-code (CFN). And simpler, fully integrated, and you get full AWS support, not the case with EKS or hand rolled kube.

> .. monitoring is a fad ..

We did some pretty fancy things in monitoring. ELK and more. And yes, it uses some useful bits of CW.

Re:What we learned after a year on Kubernetes by crowquill on Thursday September 17, 2020 @09:20AM (#24504254)
Another happy ECS user here. You get most of the benefits of Kubernetes, without a lot of its complexity and maintenance. Yes, it’s a proprietary service and all, but that’s not really an issue. The applications are already containerized and could be moved to any other vendor/tool with relatively low effort if you ever needed to.