21–30 of 105 posts
Crazy that someone is using something as complex as k8s on a home server and without knowing basics. Newbies are better served starting with the simple stuff and then moving to the complex if needed
> what do you do if your ISP changes your IP addresses? I update the DNS record. Manually. It's a once in a blue moon thing, and I assume the probability of it is low enough that it will not occur when I'm so far from home that "it can wait until I get home" doesn't suffice. 15+ years or so now, and that strategy has worked just fine. … TFA's intro could do with explaining why the IP is so hard coded in the cluster,…
Earlier quoted context omitted.
Lol, kind of defeats the purpose
What defeats what purpose? I don't run k8s out of some love of ... managing external IPs?
Maybe the external ingress node can be a load balancer controlled by the k8 cluster. But then you still have to communicate with the home server and it has no exposed ip address
Crazy that someone is using something as complex as k8s on a home server and without knowing basics. Newbies are better served starting with the simple stuff and then moving to the complex if needed
I think it's good. K8s is well packaged (these days) and quite discoverable. I agree it's likely to throw up some problems, but it's great that it's possible.
But even in those 3 areas I haven't exhausted all the knowledge and features available.
So I'm just skeptical when someone is using k8s and hasn't mastered the fundamentals. How do they know whether they should be using a high level k8 feature or a low level os feature? Happened with docker a lot to me when I didn't know better, I was learning how to set memory limits on containers and reset policies instead of learning to do it on the OS level.
Crazy that someone is using something as complex as k8s on a home server and without knowing basics. Newbies are better served starting with the simple stuff and then moving to the complex if needed
Anyway I agree that there no point in using k8s for home stuff. Single instance of anything should be sufficient for any needs like that.
On the other hand maybe someone just like to tinker with technology.
Earlier quoted context omitted.
I think it's good. K8s is well packaged (these days) and quite discoverable. I agree it's likely to throw up some problems, but it's great that it's possible.
I'll be honest, never learned it, worked up from network protocols, reached docker in terms of virtualization, and of course OS fundamentals. But even in those 3 areas I haven't exhausted all the knowledge and features available. So I'm just skeptical when someone is using k8s and hasn't mastered the fundamentals. How do they know whether they should be using a high level k8 feature or a low level os feature? Happene…
Except docker, on its own without something else in the stack, isn't Virtualization.
Dealing with changing residential ips is nothing new. It's interesting to see how it's still being solved for even in this overly complex k8s landscape we find ourselves in now. Back in the day we'd use free services like https://freedns.afraid.org/ on a cron to refresh the ip every so often. I used afraid to refresh my dial up ip address, for my "hosting service" domain. The "hosting service" was an old tower pc liv…
[flagged]