Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well, set me up one. :P


my pubkeys are below, send me an ip address and port to an ssh server

https://github.com/cameronnemo.keys


Anyone can ssh into a server and apt-get haproxy and tweak the configuration and get it "working" where the definition of working is accepting and routing traffic. But that's just a hobby setup. When people say setting up a load balancer is complex they are talking about professional setups, not a one off software install on a single server.


So give me a (possibly private) ASN, a couple bgp peers, and the frrouting suite. ACME is not difficult either.


But I want to be able to update my haproxy config with a git push, and roll it back with a single command, without sshing into anything, if something goes wrong. I want my everyday administration to be simple. Not the initial setup.


k8s did not invent gitops.


No but it sure as hell made it a lot easier and straightforward.


Now set it up in 30 data centers around the world, with the ability for dozens of different teams to add and change their applications, and across multiple staging and QA environments.


Why do I need 30?

1 rack in a datacenter is plenty for a database backed web app with a million users.


That is going to be killer latency for people in other parts of the world.

In my case, I work for a CDN, so we need to have data centers all around the world.


My what and what? :P I do get your point, it is "easy" for some definition of such, but to be fair, k8s would automatically put the ip and port in for my part of it all at least.


I never knew about this github feature. Nice!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: