Hacker News new | ask | show | jobs
by nisa 348 days ago
This (ragebaity/ai?) post kind of mixes things up. Kubernetes is fine I think but almost everything around it and the whole consulting business is the problem. You can build a single binary, use a single layer oci container and run it with a single config map with memory quota on 30 machines just fine.

Take a look at the early borg papers what problem does it solves. Helm is just insane but you can use jsonnet that is modelled after Google's internal system.

Only use the minimal subset and have an application that is actually build to work fine in that subset.

1 comments

how does jsonnet relate to Helm? It appears to be a template language.
You can use it with tanka or kubecfg, argo and flux also have native support. You can also just render yaml and use kubectl apply
You claim to just “keep it simple” but then rattle off about 10 k8s related tech nouns. No, I don’t think it’s simple.
The granularity of the web stack is ruinous. Of course the opposite also has issues - e.g. iOS, a monolithic stack where there's one standard, but often good tool for every common requirement. But I'd happily take even a semi-competent benevolent dictator over the insane multiplication of options for every single microscopic piece of the stack, each with its own obscure proper noun, phrase, or acronym.
Simple is not easy.