Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kubernetes Home – what do you do if your ISP changes your IP addresses?

vegard.blog.engen.priv.no

Post reply on HN
Print view View original

91–100 of 105 posts

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#91

Post by _cenw »

TZubiri wrote: post #86
_cenw wrote: post #82

Earlier quoted context omitted.

I wish Happy Eyeballs worked better or let me absolutely prefer IPv4, because every time I set up a free v6 tunnel I get banned about 2 days layer for pushing a few terrabytes over it, when all I wanted was to be able to SSH into every one of my containers on a cheap VPS separately. Or the tunnel is so slow, I'm degrading my entire internet connectivity.

>free v6 tunnel There's your problem. You need some form of cost attached to some identity assets, anything under the IANA umbrella, ips/domain names. This is in order to prevent sybil attacks. This is all well studied under he hashcash bitcoin era as PoW. So yeah, you actually need to spend some money not in exchange of something here, but as the very thing you need, you need to distinguish yourself from those that…

Unfortunately there's quite a market gap if you need bandwidth. I can't just pay HE 10 bucks a month, their service doesn't work that way. Hetzner would work, but their IP space is very often randomly blocked from lots of things.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#93

Post by taskforcegemini »

mystified5016 wrote: post #64
deathanatos wrote: post #10

> 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,…

My ISP lets me have an IP for as long as my ONT is online. If it reboots, I'm likely to get a new address if it's offline long enough. So my ONT is on a UPS. We only get power outages once or twice a year, but I havent had my IP change in two years now. And yeah, when it changes I just go into my DNS and update the records. It's like a five minute job. I could probably automate it if I cared to figure out Hover's API…

most likely not DOCSIS related, as my ISP behaves with it just like you described your current ISP

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#94

Post by vegarde »

deathanatos wrote: post #10

> 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,…

Author here. A few decades in IT, but still like to learn new things at home.

I do port forwarding for IPv4. But port forwarding on IPv6? You must be kidding me, the /56 I get from my ISP is meant to be used on the inside. It hasn't changed yet, and maybe it never will.

I am running Unifi as router, and they are claiming that the prefix IDs assigned to the networks won't change. But I have had it happen - probably through my own fault. Wish I could just hardcode the prefix. As for the metalLB IP addresses, since writing this I have done away with hardcoding the actual IP addresses and just let the pool assign them. It still means I need to update the firewall rules on my router, though, should they change. And my metalLB range would of course need to be updated.

The IPv4 is still hardcoded due to the port forwarding, and since it's private space that I won't change anyhow.

As for why I don't do it manually, you must be kidding me. You are. reading hacker news, and you question why people tinker with complex automations and just don't do it manually? Because I can of course, and that's the only reason I need.

I like to pretend like my home network matter, that I run a mission critical service.

I run services at home. Multiple. Because I can, and I like to learn. The blog runs at home, of course, even though hosted blog services have existed for years now. I also run Nextcloud. It saves me the cost of extra storage on Dropbox and/or Google Cloud, I do it to my home network instead. Then there's plex, home assistant plus all the other services a geek would like to run. They all run in my K8s cluster now. I was served well by docker for years, but I wanted to test K8s, and that was the only reason I needed.

And a cluster? Well, it's called that in Kubernetes. But in reality, it's only one node. Because two would be overkill for home usage.

To sum it up:

I did it because

1) I wanted to 2) I could 3) I would learn something from it 4) It would give a modest benefit.

It's all the reason I needed to.

As for why automating things I could do it manually should it happen, see 1, 2, 3 and 4 above.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#95

Post by vegarde »

mystified5016 wrote: post #64
deathanatos wrote: post #10

> 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,…

My ISP lets me have an IP for as long as my ONT is online. If it reboots, I'm likely to get a new address if it's offline long enough. So my ONT is on a UPS. We only get power outages once or twice a year, but I havent had my IP change in two years now. And yeah, when it changes I just go into my DNS and update the records. It's like a five minute job. I could probably automate it if I cared to figure out Hover's API…

OP here.

Yeah, I don't expect this to really change, either, in normal operations. But I'm a home user, I don't pay for a static IP address or a static IPV6 prefix.

But I'm a geek/hacker by heart, so curiosity sometimes get to me.

I did it because there was things to learn from it.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#96

Post by vegarde »

TZubiri wrote: post #26
robertlagrant wrote: post #21

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…

OP here.

Of course I haven't mastered he fundamentals of K8s yet, I am just beginning to learn it.

Like you, I have been using docker for years, and to be honest it served me very well - and would probably continue to do so. But as a geek, I have a natural curiosity, sometimes just the curiosity of whether or not something can be done, and how it works, is enough justifications to do it.

As you probably read, this is in my home services. Which is where I am free to do exactly these experiments before I know the inns and outs of it.

Some of what I wrote in the blog post, I have already ditched. I am no longer hardcoding the ipv6 addresses from the pools, for example, but I still need to change my pool ip addresses if my ISP changes the range. I am not sure if my way is the correct one. I could do it manually, but what's the fun in that ?

There will be more blog posts as I learn, you be sure (there already is). I have more coming up, but one of my current projects will take a bit of time, as I have decided that writing a Unifi Operator for managing firewall rules is a better way to do it :)

Now, for home use? Whoever does that, write K8s Operators?

If you're on hacker news then you should understand that the goal isn't necessarily the result, it's the learning experience.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#97

Post by vegarde »

npodbielski wrote: post #28
TZubiri wrote: post #6

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

Probably he is not a newbie entirelly since he was able to run kebernetes. 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.

Exactly (OP here).

The goal wasn't necessarily the result.

I like to tinker.

And well...my K8s cluster is only one node so far, so there's limits to what I can play with.

And please: No comments that K8s is overkill. I know, and I don't care :) There's things to learn from it, and that's good enough reason for me.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#98

Post by vegarde »

_cenw wrote: post #20
yjftsjthsd-h wrote: post #14

Earlier quoted context omitted.

What defeats what purpose? I don't run k8s out of some love of ... managing external IPs?

Are you even running a real homelab if you're not running MetalLB in BGP mode?! Sarcasm obviously, but it's a fun exercise, especially if you get a real (v6, probably) net to announce.

It's on my bucket list.

My Unifi Cloud Gateway Max doesn't (yet) support BGP, but other Unifi devices do, so I do hope that it'll come to my device to. If not, I'll have to think of other ways to test it. But in the meantime, there's plenty of other stuffs to learn.

I have a real, ISP-routed IPv6 net to play with.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#99

Post by vegarde »

davkan wrote: post #75

I have one A record for my home ip address. This is dynamically updated by my router whenever the public IP address changes. Everything else is a CNAME pointing at the A record. Completely set and forget and supported by most of the shelf consumer routers or router OS like vyos. This is a much preferable solution to me as there are no changes to external-dns resources when the public IP changes. Granted, i don’t run…

I run dual-stack.

I used to run a dynamic DNS service, but these days I prefer to do it myself towards the API of my DNS provider. External-DNS in k8s is pretty neat that way.

Changing the K8s resources automatically is not really a big deal. It's a fun exercise.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#100

Post by vegarde »

from-nibly wrote: post #51

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.

It would if you are running your IPv6 and real IPv6 addresses on your K8s ingress adresses.

And I do.

Post reply on HN