Live data from Hacker News

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

vegard.blog.engen.priv.no

41–50 of 105 posts

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

#41

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…

"Exposing your IP address to the world" seems like such an arbitrary thing to care about when you're opening a tunnel with the express intention of letting people in. No NAT bs, but you've got magic tunnel bs instead that you have no control over. And of course you're still "exposed to the world". Your IP address is public. That's the whole point. So you're going to be using a firewall regardless, what difference does one rule make really?

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

#42
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

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.

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

#43
My 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.

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

#44
post #29

Earlier 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 does not virtualize the kernel, in fact the kernel version “inside” Docker is the same as the host.

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

#46
post #39
post #33

Earlier quoted context omitted.

> If you can't shell a buck or persuade your isp to reserve a static ip for you. Try to persuade their dhcp server. My ISP offers either a home contract, where the IP forcefully changes every 24h and I can't pay for static IP, or they offer business contracts for businesses with minimum 10 employees, but that contract requires proving you're a registered as business with the local chamber of commerce & have the tax p…

> My ISP offers either a home contract, where the IP forcefully changes every 24h and I can't pay for static IP, or they offer business contracts for businesses with minimum 10 employees, but that contract requires proving you're a registered as business with the local chamber of commerce & have the tax paperwork. Wow, and I thought Comcast was customer hostile, this is just bonkers.

German ISPs are kinda weird like that. Unmetered gigabit FTTH for $70/month, no CGNAT, and open peering. 3 phone numbers and 2 phone lines included. But static IP isn't even an option.

I've built custom dyndns scripts to automate everything away, so nowadays it's only a second of interruption (thanks to some DNS TTL trickery), but it's nonetheless really annoying to deal with.

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

#47
post #24

Earlier quoted context omitted.

Tunneling through a single external node defeats the purpose of hosting k8s in home server. 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

> Tunneling through a single external node defeats the purpose of hosting k8s in home server. How so? You can just rent a cheap server to tunnel through, while having the benefits of your home machine(s) for compute. > 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 Do you mean that you wo…

>how so?

SPOF

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

#48
post #39
post #33

Earlier quoted context omitted.

> If you can't shell a buck or persuade your isp to reserve a static ip for you. Try to persuade their dhcp server. My ISP offers either a home contract, where the IP forcefully changes every 24h and I can't pay for static IP, or they offer business contracts for businesses with minimum 10 employees, but that contract requires proving you're a registered as business with the local chamber of commerce & have the tax p…

> My ISP offers either a home contract, where the IP forcefully changes every 24h and I can't pay for static IP, or they offer business contracts for businesses with minimum 10 employees, but that contract requires proving you're a registered as business with the local chamber of commerce & have the tax paperwork. Wow, and I thought Comcast was customer hostile, this is just bonkers.

>Wow, and I thought Comcast was customer hostile, this is just bonkers.

It's caused (magnified by upstream requirements by the RIR due to ipv4 exhaustion and possibly reputation mgmt.

In order to get a block isps need to provide a plan on how they will put the ips to good use for the benefit of society.

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

#49
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

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.

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

#50
post #47

Earlier quoted context omitted.

> Tunneling through a single external node defeats the purpose of hosting k8s in home server. How so? You can just rent a cheap server to tunnel through, while having the benefits of your home machine(s) for compute. > 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 Do you mean that you wo…

>how so? SPOF

And having a single IP address, with one ISP at home isn't a SPOF?
Post reply on HN