Holy cow, I've been doing kubernetes for 8+ years at this point. No idea why your home IP address would change a single thing in kubernetes.
Kubernetes Home – what do you do if your ISP changes your IP addresses?
51–60 of 105 posts
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#52Earlier quoted context omitted.
Well, we've all got to start somewhere, right? But yeah, I'd personally recommend Docker for self-hosting. Kubernetes or Proxmox always end up being too much to handle for personal use - or even small to medium sized companies.
> Proxmox always end up being too much to handle I've been running a 2-node Proxmox cluster for about 3 years with close to no maintenance. What's too much about it? It gives me easy VM and LXC management and very easy declarative networking and firewalling. That alone makes it worth it for me.
Right, proxmox (like k8s) is a huge force multiplier for individuals trying to manage large/diverse surface areas. I run both for my own stuff at home (well k8s in the cloud, but its not work related) precisely because of the power it offers.
Yes they are complicated. Yes, they are still worth learning. And once you learn them they make a lot of sense to use when given the option.
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#53Dealing 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]
Ddns is absolutely the right answer in a lot of cases, and even better that a lot of routers have built-in support for managing the record for you.
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#54Earlier quoted context omitted.
> reached docker in terms of virtualization Except docker, on its own without something else in the stack, isn't Virtualization.
Docker is kernel virtualisation. Are you thinking of OS virtualisation, like a VM?
Docker is OS-level virtualization. VMs are hardware virtualization. Different layers.
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#55My experience is this is no longer a problem. Ever since the US gov legalized data mining/spying/tracking I have not had my residential IP change. I think its more profitable to spy by essentially giving "free" static IPs to all customers.
More likely your ISP uses CGNAT and your router's IP is not a "real" public IP address.
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#56Dealing 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]
>>ddns
>Yeah don't do that if you want to be a professional with pride in their craft
Why? All of the large DNS providers have DDNS functionality. Even AWS has documented methods for DDNS on Route53.
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#57How about a wireguard tunnel from an ingress box? You still pay for one VPS, but can run everything locally and just load balance at the ingress. I just manually add configs to nginx, but there are automated tools too.
Lol, kind of defeats the purpose
I do this for email after I got a new IP address from the shit KPN pool instead of the clean XS4ALL pool. Outgoing email proxies through an IP address at Hetzner. It's not pointless because
- I get specs from an old laptop (that I had laying around anyway) that would probably cost like 50€/month to rent elsewhere. Power costs are much lower (iirc some 2€/month) and it just uses the internet subscription I already had anyway
- When I do hardware upgrades, I buy to own. No profit margin, dedicated hardware, exactly the parts I want
- All data is stored at home so I'm in control of access controls
- Gigabit transfer speeds at home, which is most of the time that I want to do bulk transfers
I see various advantages that still exist when you need to tunnel for IP-layer issues
Edit: got curious. At Hetzner, a shared cpu with 16GB RAM is 30€/month, but storage is way too little so an additional 53€/month just for a 1TB drive needs to be added (at that price, you could buy one of these drives new, every month again and again and still have enough money over to pay for the operating electricity; you'd have a fleet of 60 drives at the expected lifetime of 5 years, or even at triple redundancy you get 20TB for that price). I'll admit the uplink would be significantly better for this system, but then my downlink isn't faster than my uplink so at home I wouldn't even notice. Not sure how much of a difference a dedicated CPU would make
At AWS, I have to guess things like iops (I put in 0 to have a best-case comparison), bandwidth (I guessed 1TB outbound, probably some months is five times more, some months half). It says the cheapest EC2 instance with these specs, shared/virtual again mind you so no performance guarantees, is t4g.xlarge. With storage and traffic, this costs 301$/month which I guess is nearly the same in euros after conversion fees. If I generously pay 3 years up front, it's only 190$ monthly + 2'156$ up front, so across 3 years that's 250$/month (and I'm out of over 2 grand which has an expected average return of 270€ at the typical 4% in an all-world ETF — I could nearly fund the electricity costs of the old laptop just from the money I lose in interest while paying for AWS! Probably 100% if I bought a battery and solar panel to the value of 2150€)
I actually have more than 1TB storage but don't currently use all of it, so figured this is a fair comparison
The proxy I currently have at Hetzner costs me 4€/month, so I save many multiples of my current total cost (including the at-home costs) by self hosting.
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#58> 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,…
Potentially they are doing some hairpin rules that require specific enumeration?
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#59Earlier quoted context omitted.
> T-Mobile Home Internet unfortunately does not Why did they make it so inconvenient?
Home Internet is seemingly far more affordable than their phone plans. So they have other ways of encouraging you to use the phone plans.
Its about the same as my per-line cost. The real reason I suspect is to try to discourage upload usage. T-mobile's main spectrum is deployed with TDD which schedules send and receive on the same frequency. The config they use allocates 80% or 90% of the time to download and is set at network level, not dynamic per device. Basically, they are way more constrained on upload capacity the way things are currently built out.
Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?
#60Earlier quoted context omitted.
Docker is kernel virtualisation. Are you thinking of OS virtualisation, like a VM?
Docker is OS-level virtualization. VMs are hardware virtualization. Different layers.
That isn't even true, you share your host kernel. There are parts of the kernel that aren't namespaced as well. The kernel keyring is probably the big one.