Also no need to be that scared about servers.
393 karma · joined November 16, 2019
Also no need to be that scared about servers.
This field used to be inspiring, but now I see the ideia of having a server being sold as the plague and lots of negativity towards people who are good at servers. They are not seen as another human being but the "other".
Also I can't understand why one would prefer to pay that much for such complexity.
It seems unsustainable for me, not to mention the new generation being spoon fed that that is way to go makes me concerned about the future of open computing.
Can't wait for codeless, zero code, nocode, whatever name it gets called... something where normal people can build their own ideas without having meaningless discussion about tdd, frameworks and etc, nor the need to maintain codebases, ci/cd and all the jazz
Exactly https://www.theregister.com/AMP/2020/09/15/microsoft_submits...
It is not the first time it happens and people keep buying into it. But hey we have calculator source code, Microsoft loves open source, right? Right?
The navigation system is great to use with keyboards.
I saw you are already implementing some ideas from my inputs, that is great, please keep it going.
Eventually, in notorious systems, you may face issues of having too many /32 rules, a good idea is to implement some mechanism to defragment them into single/bigger contiguous cidr blocks. There are other firewall implementations that can serve as inspiration.
OR
I recommend using ipset with a single iptables rule to match/block from the set. This way you don't need to reload stuff everytime. (Just add the ips into the set)
PS: I hope you don't mind my snark comments, HN is fun.
Wasn't SSH made for that?
This has serious quality issues and any competent and nice sysadmin should say _nope_ to run this in any serious environment, for your own good ;-)
IP addresses are just strings? At least parse/validate for IPv4/IPv6.
Why yet another database? Can't the rules be loaded from the running system?
Why not just ipset-persistent + knockd + portsentry? I know it is easy to get overexcited with a new pet project, but just be careful to not put this kind of stuff in a production system kidos.
Nowadays everything is 10-20x more complicated and expensive than it should be compared to 10 years ago.
Everything is a host and can be used for anything.
And that IaaC is about the I rather than the C.
Give Poettering a break! You have no clue what is to be in his shoes. ;)
Give yourself some time in between too. It is all about the fun.
For example, if you use just kubelet (the main daemon) without the api, drop some static yaml files (ala unit files) under /etc/kubernetes it will be something like systemd is. No big deal so far, but using the kubernetes api (just another daemon) it allows you to run the all the things anywhere.
I mean, you terminate one computer, k8s will figure out that the program should be running and it will be started in another computer. (Including moving detaching/attaching the block device from/into computers, this kind of things)
There is no much secret.
For me it really feels like an (well designed/integrated) API on top of standard Linux technology (ipvs, netfilter, mount, process mgmt, virtual ip, etc) via yaml running your stuff in 1..N computers but you manage it as one big computer :)
EDIT: added more context within "()"
Nothing more than that.
Perhaps the complexity increase when we start giving funny names for simple things, opinions, personal preferences...
Countless hours can be wasted arguing what "deploy" is, what an "artifact" is, "container", etc.
Boring is better.
For people who already know Linux, kubernetes comes naturally because it is pretty obvious.
But indeed, by experience, many companies can go to "unicorn scale" with two or three boxes.
It's basically running a big computer without even trying.