Re:Do not do in code what can be done in infrastructure (2017)
by betaby on Friday August 13, 2021 @10:46AM
(#28169539)
That's in fact how I read the author. He advocates using already written well know software like Traefik, LinkerD, Envoy and so on, and not to reinvent their functionality in your code.
[ Parent
| on HN ]
Re:Do not do in code what can be done in infrastructure (2017)
by BiteCode_dev on Friday August 13, 2021 @11:01AM
(#28169724)
Or k9s ? But then it's so hard to manage you end up paying a cloud provider to do it for your or hire the dupper k9s expert.
Re:Do not do in code what can be done in infrastructure (2017)
by sascha_sl on Friday August 13, 2021 @12:30PM
(#28171087)
k0s is a lightweight ready made runtime
k3s is similar, but older
k8s is kubernetes
k9s is a canine joke and terminal client for k8s
Just so I'm not just nitpicking, k0s and k3s are both good solutions to hosting kubernetes on bare metal or cheap VPSs. Hetzner in particular is starting to get most of the features you typically lack on VPS providers in that price range (software-defined networks, load balancers, storage) packaged in a kubernetes cloud-controller.
Re:Do not do in code what can be done in infrastructure (2017)
by vinceguidry on Friday August 13, 2021 @04:10PM
(#28173915)
I found k0s to be fairly skin deep, much is missing compared to the other solutions.
Re:Do not do in code what can be done in infrastructure (2017)
by sascha_sl on Friday August 13, 2021 @04:37PM
(#28174202)
That is by design. k3s installs a bunch of things that assume you’re on bare metal, k0s knows you’ll probably bring your own ingress and cloud controller. It is just kubeadm, but in one binary.