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

31–40 of 105 posts

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

#31

Post by npodbielski »

wutwutwat wrote: post #2

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…

There are more downsides. Instead of maintaining 1 server you have to maintain server and tunnel or 2 servers and tunnel. If someone does not know how to maintain internal network DNS and dhcp then if internet is down then your services are down too, because likely there are only reachable through external domain. I agree though that someone who does know much probably should not do that. If you know what is SSH and root account, probably less is more.

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

#32

Post by TZubiri »

Operyl wrote: post #29
TZubiri wrote: post #26

Earlier quoted context omitted.

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…

> reached docker in terms of virtualization Except docker, on its own without something else in the stack, isn't Virtualization.

Not arguing this again, go edit the wikipedia article if you are so confident

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

#33

Post by kuschku »

TZubiri wrote: post #11

"My ISP is in total control over my external IP addresses. I don’t pay for permanent IP addresses, and while they haven’t so far changed neither my IPv4 address or my IPv6 network, it can happen. Probably by mistake, since I have no kept my current ones for three months" If you can't shell a buck or persuade your isp to reserve a static ip for you. Try to persuade their dhcp server. https://datatracker.ietf.org/doc/h…

> 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 paperwork.

Many people have no easy option to get static IP.

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

#34

Post by winterqt »

TZubiri wrote: post #24
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?

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 wouldn’t be able to access the K8s control plane endpoint then (which you could if configured properly)? Or something else?

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

#35

Post by robertlagrant »

Operyl wrote: post #29
TZubiri wrote: post #26

Earlier quoted context omitted.

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…

> 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?

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

#36

Post by globular-toast »

Uhh. What is all this for? My IP address can change. I just use a dynamic DNS client to update my DNS record using my registrar's API. It's been this way since, like, 2001? (Well, most registrars didn't have APIs back then, but there was dyndns).

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

#37

Post by Timber-6539 »

robertlagrant wrote: post #35
Operyl wrote: 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?

Virtualization usually refers to OS/ device emulation in software. Docker uses kernel namespaces which is an entirely unrelated feature.

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

#38

Post by gsich »

TZubiri wrote: post #7
wutwutwat wrote: post #2

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]

DDNS does not imply foreign domain.

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

#39

Post by voxadam »

kuschku wrote: post #33
TZubiri wrote: post #11

"My ISP is in total control over my external IP addresses. I don’t pay for permanent IP addresses, and while they haven’t so far changed neither my IPv4 address or my IPv6 network, it can happen. Probably by mistake, since I have no kept my current ones for three months" If you can't shell a buck or persuade your isp to reserve a static ip for you. Try to persuade their dhcp server. https://datatracker.ietf.org/doc/h…

> 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.

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

#40

Post by merpkz »

Kubernetes admin here with ~2y experience. Since a lot of you have misconception of what this guy is doing I will try to explain. Author wrote a piece of code which will interact with network gateway to get IPv4/IPv6 network address and then update kubernetes configuration accordingly from within a container running on said cluster. That seems to be needed, because MetalLB component in use exposes kubernetes deployments in cluster via predefined IPv6 network address pool which is given from ISP, so if that changes, cluster configuration should change too. This is one of most bizarre things I have read about kubernetes this year and probably shouldn't exist outside a home testing environment, but hey, props to author for coming up with such idea.
Post reply on HN