I don't need to build a datacenter, i'm fine with building a rack myself in my garage.
During the last GPU mining craze, I helped build a 3-rack mining operation. Gpus are unregulated pieces of power-sucking shit from a power management perspective. You do not have the power requirements to do this on residential power, even at 300amp service.
Think of a microwave's behaviour ; yes, a 1000w microwave pulls between 700 and 900w while cooking, but the startup load is massive, almost 1800w sometimes, depending on how cheap the thing is.
GPUs also behave like this, but not at startup. They spin up load predictively, which means the hardware demands more power to get the job done, it doesn't scale down the job to save power. Multiply by 58 rx9070. Now add cooling.
K3s (and k8s for that matter) expect you to build a hierarchy of yaml configs, mostly because spinning up docker instances will be done in groups with certains traits applying to whole organization, certain ones applying only to most groups, but not all, and certain configs being special for certain services (http nodes added when demand is higher than x threshold).
But I wonder why you want to cluster navidrome or pihole? Navidrome would require a significant load before service load balancing is required (and non-trivial to implement), and pihole can be put behind a round-robin DNS forwarder, and also be weird to implement behind load balancing.
I don't think anyone here disagrees that port scanning is bad, nor that you even filed an aws ticket. And congrats on your live service.
But your answers to comments are weird, like this is not only your first server or vps experience with a public interface, but your first time exposing anything to the public web. And even if that's true, there's a first time for everyone.
But man, doubling down and insisting that "port scanning is unauthorized traffic" betrays a certain naivete about how tcpip works.
What you are seeing is not only normal, but AWS can't do anything about it because that's how IP source and destination sockets work.
You obviously weren't actually around when he was granted mini-king status and acted like a jackass to literally anyone who objected to pulse or systemd. As a result, redhat, canonical, and Debian had to eat criticism over pushing these before they were ready... because of "superstar" poettering.
At the time, canonical was throwing its weight around and essentially bullying Debian upstream repos. Around this time, there was a mass exodus of the Debian leadership over this kind of thing.
The old guard of Debian wasn't as... enthusiastic about systemd either, but look what they use now.
I think so. I lost count of the little things, it really was death by a thousand paper cuts.
I was a pretty rabid fan of Ubuntu, still have an x86 and ppc CD of 5.04 somewhere.
But by the time snaps started appearing, and then Ubuntu pro, Ubuntu decided to revert some of my customized configs in /etc after an upgrade, I had had enough. When snaps were reinstalled after an upgrade in 2021, I just flipped over to Debian, which has come a long way in being usable out of the box.
During the last GPU mining craze, I helped build a 3-rack mining operation. Gpus are unregulated pieces of power-sucking shit from a power management perspective. You do not have the power requirements to do this on residential power, even at 300amp service.
Think of a microwave's behaviour ; yes, a 1000w microwave pulls between 700 and 900w while cooking, but the startup load is massive, almost 1800w sometimes, depending on how cheap the thing is.
GPUs also behave like this, but not at startup. They spin up load predictively, which means the hardware demands more power to get the job done, it doesn't scale down the job to save power. Multiply by 58 rx9070. Now add cooling.
You cannot do this.