Hacker News Reader

Comment by hartator | Hacker News Reader

Auto-scaling doesn’t take 3-5 hours to set up. Or come work for us!

He used GCP, setup a pubsub topic and a cloud function. It took less than an hour to setup, the rest of the time was rewriting a portion of the code to write to the queue, etc.

There’s other ways in other platforms as well (eg if you’re using Kubernetes)

With a Kubernetes autoscaler, this takes you ~20 Minutes to setup pod autoscaling. If you run your k8s on say GKE, setting up node autoscaling is another 5 Minutes.

I totally agree with you, once you've factored in the dozens of hours gaining knowledge of k8s and hundreds+ of hours of experience dealing with it in production. You can get by with far less, but it's going to be pretty stressful when things go sideways in prod without knowing exactly why.

This is sort of a strange argument. If your argument is that we need to factor in prior knowledge, naturally I will ask: how MUCH prior knowledge?

* do i need to factor in experience with VMs?

* do i need to factor in OS and networking theory learnt in college?

* do i need to factor in high school algebra?

* do i need to factor in learning the english language?

Of course you need to factor in learning k8s. Before, it was learning VM's+ {ansible, chef, salt}, before that it was prob something else.

In theory maybe.

In practice - the application running in the pod has to be aware of this, and the most intensive part are rarely the bottleneck. Most of the time this is an architecture issue, not a resource issue. This takes time and experience, and overhauling a platform to remove a bottleneck is usually very painful if you have a bit more complex setup.

We put everything in Kubernetes to scale. Now large uploads and downloads fail more often than before.

Are you saying k8s is to blame for large file upload/download failures? Maybe your infra needs a tweak?

Reply on news.ycombinator.com