4 ms·

I have experienced first hand several cases of k8s gone wrong. In the end I have come to the conclusion that most companies don't really need the complexity of

I have experienced first hand several cases of k8s gone wrong. In the end I have come to the conclusion that most companies don't really need the complexity of k8s. Seriously, most k8s projects I have been involved with required so much effort to bootstrap and keep it going, it just blew me away! The experience for the average developer was just frustrating and infuriating: AWS ECS to the rescue! Some will argue: vendor lock in! Really? I bet most services out there are already vendor locked in, just go with the flow and make your life easier. I have seen companies failing because investing so much in building infrastructure, supposly vendor lock in free (or so they thought) that they lost sight and did not invest enough building the actual product: no revenue -> party is over. Don't make the same mistake.

imnotjames 5y ago
ECS trades kubernetes manifests and generalized tools for cloudformation or the AWS UI, though.. Most everything else seems to be the same thing as if you ran with EKS, just different names for everything. Setting it up yourself, though, no, I wouldn't do that unless I had a large enough team to maintain it.
- WYepQ4dNnG 5y ago
  > ECS trades kubernetes manifests and generalized tools for cloudformation or the AWS UI, though.. Terraform has served me well, it does come with some pain as well, but nothing compared to k8s.
flowerlad 5y ago
> most companies don't really need the complexity of k8s If you want to run a complex service consisting of multiple microservices, auto scaling and so on, nothing beats Kubernetes. But you're right, most small businesses just need a simple web site, and for them, an Amazon Lightsail VM might suffice.
- rantwasp 5y ago
  yeah, nothing beats K8s except you know... maybe serverless. or maybe cloud primitives that are already there and are handled by someone else. IMHO, unless you have a huge fleet of bare metal machines K8s is an overhead you don't need
  - jakupovic 5y ago
    Thanks for your HO but you're wrong. K8s is the future and the new JVM.
  - gyoza 5y ago
    i run k8s on my home network, its nice to not have to log into my linsux box to see logs and restart things. I like having the ability to just nuke my thing at home and it comes up the same way it did before,... Not sure why it too me so long to adopt work mentality at home but its great. Plex acting funny? kill the pod. Sonar needs an update? Kill the pod.
908B64B197 5y ago
> I have seen companies failing because investing so much in building infrastructure, supposly vendor lock in free (or so they thought) that they lost sight and did not invest enough building the actual product: no revenue -> party is over. How was the stock comp for engineers at these companies?
- WYepQ4dNnG 5y ago
  late stage "startup" who had struggled with growth for years, they thought they needed to invest in building a more complex system and infrastructure, and they hired tons of engs (who actually had literally nothing to do) ... instead what they really needed was to focus on their customers and build them a useful product that simply worked. They spent months building and deploying their own k8s cluster: EKS was "vendor lock in" so that wasn't a good choice for them, but guess what, all their infrastructure was already running in AWS anyway and their product was already vendor locked in: RDS, S3, etc ... also ... to make things even more complex, they thought they needed to go all-in super distributed micro services: it took literally months to get new "services" up and running in production. It was a s*t show! One of the many story of let's break the monolith, embrace microservice, thus k8s ... gone horribly wrong. Eventually most engs left ....
  - 908B64B197 5y ago
    > but guess what, all their infrastructure was already running in AWS anyway and their product was already vendor locked in: RDS, S3, etc ... I laughed, but your response doesn't answer my question regarding engineers comp.
    - WYepQ4dNnG 5y ago
      stock options, not great
  - rantwasp 5y ago
    > Eventually most engs left .... and now have k8s on their resume. Bazinga!
  - 5y ago
me_me_me 5y ago
Thank you. At least I am not alone. I just want to write some code and not waste a week redeploying K8s shit again... send help...

imnotjames 5y ago

ECS trades kubernetes manifests and generalized tools for cloudformation or the AWS UI, though.. Most everything else seems to be the same thing as if you ran with EKS, just different names for everything. Setting it up yourself, though, no, I wouldn't do that unless I had a large enough team to maintain it.

WYepQ4dNnG 5y ago
> ECS trades kubernetes manifests and generalized tools for cloudformation or the AWS UI, though.. Terraform has served me well, it does come with some pain as well, but nothing compared to k8s.

flowerlad 5y ago

> most companies don't really need the complexity of k8s If you want to run a complex service consisting of multiple microservices, auto scaling and so on, nothing beats Kubernetes. But you're right, most small businesses just need a simple web site, and for them, an Amazon Lightsail VM might suffice.

rantwasp 5y ago
yeah, nothing beats K8s except you know... maybe serverless. or maybe cloud primitives that are already there and are handled by someone else. IMHO, unless you have a huge fleet of bare metal machines K8s is an overhead you don't need
- jakupovic 5y ago
  Thanks for your HO but you're wrong. K8s is the future and the new JVM.
- gyoza 5y ago
  i run k8s on my home network, its nice to not have to log into my linsux box to see logs and restart things. I like having the ability to just nuke my thing at home and it comes up the same way it did before,... Not sure why it too me so long to adopt work mentality at home but its great. Plex acting funny? kill the pod. Sonar needs an update? Kill the pod.

908B64B197 5y ago

> I have seen companies failing because investing so much in building infrastructure, supposly vendor lock in free (or so they thought) that they lost sight and did not invest enough building the actual product: no revenue -> party is over. How was the stock comp for engineers at these companies?

WYepQ4dNnG 5y ago
late stage "startup" who had struggled with growth for years, they thought they needed to invest in building a more complex system and infrastructure, and they hired tons of engs (who actually had literally nothing to do) ... instead what they really needed was to focus on their customers and build them a useful product that simply worked. They spent months building and deploying their own k8s cluster: EKS was "vendor lock in" so that wasn't a good choice for them, but guess what, all their infrastructure was already running in AWS anyway and their product was already vendor locked in: RDS, S3, etc ... also ... to make things even more complex, they thought they needed to go all-in super distributed micro services: it took literally months to get new "services" up and running in production. It was a s*t show! One of the many story of let's break the monolith, embrace microservice, thus k8s ... gone horribly wrong. Eventually most engs left ....
- 908B64B197 5y ago
  > but guess what, all their infrastructure was already running in AWS anyway and their product was already vendor locked in: RDS, S3, etc ... I laughed, but your response doesn't answer my question regarding engineers comp.
  - WYepQ4dNnG 5y ago
    stock options, not great
- rantwasp 5y ago
  > Eventually most engs left .... and now have k8s on their resume. Bazinga!
- 5y ago

me_me_me 5y ago

Thank you. At least I am not alone. I just want to write some code and not waste a week redeploying K8s shit again... send help...