Hacker News Reader

Comment by nailer | Hacker News Reader

You've said a lot of things but none of these respond to the comment you're referring to.

> 1) Single-handedly forced the other 2 major vendors to implement a standard API.

I (and I'm sure you too, you seem intelligent) would be surprised if say EKS is anywhere close to ECS usage. k8s is considered so complex/poor Amazon sell ECS-on-prem.

It's the epitome of resume driven development - nobody uses k8s for any other reason except to say they use k8s.

View on HN

What's your alternative for stuff that needs to run on more than one server for reliability or scale? I have been duct-taping HA solutions since the late nineties, it definitely wasn't prettier than Kubernetes. We are beyond the phase where we want to care about a physical server with a broken hard disk or power supply. Whether or not Kubernetes-the-software is the answer to the conceptualisation of a "computer" is beyond the point; there is a clear trend towards abstraction of computing hardware for good reasons, even for companies way smaller than the Googles and AWSes of this world.

> What's your alternative for stuff that needs to run on more than one server for reliability or scale?

Same as most people, and as previously mentioned: I pay pay a cloud provider, unless my business is being a cloud provider.

How do you host your stuff on, say, GCP? App engine? Only 1 per project. Compute Engine? Basically a VPS. Cloud Run? Ok, good luck with stuff that requires long running requests or listening to events from a source different from Google Cloud Pub/Sub, because your instances are eventually going to scale down to 0 and not wake up if no HTTP requests are incoming, so basically not an options for microservices if you're rolling with a non-google event broker. Need to host other Kafka, Elastic search, or anything else non-trivially deployable? How do you do that?

You're acting like IaC didn't exist before k8s.

Right now I'd use Pulumi, years ago I'd use Terraform, or the AWS API - I part of the first node AWS API client and part of App Engine before k8s existed. k8s didn't invent infra as code or auto provisioning capacity. The fact that it's advocates act like it did is why k8s is a DevOps meme.

> your instances are eventually going to scale down to 0 and not wake up if no HTTP requests are incoming

That's a good thing. I think you don't understand Serverless.

All of it responds to your original comment which was your statement that it contributed nothing except padded resumes.

I stated several things it contributed -even if you think it's too complex-.

If you don't understand why people use k8s you don't understand the problems it solves. Especially if you think ECS is a substitute.

The thing you stated is that k8s allows people to easily deploy across different cloud providers due to lack of vendor lock in. k8s doesn't because nobody uses it for that - the cost of getting it tunning compared to simpler alternatives removes all value from the cross-platform abilities. That's why k8s is a DevOps meme.

Reply on news.ycombinator.com