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

61–70 of 105 posts

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

#61

Post by anonfordays »

Spivak wrote: post #60
anonfordays wrote: post #54

Earlier quoted context omitted.

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.

>That isn't even true

You are incorrect, this is true:

"OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances, including containers (LXC, Solaris Containers, AIX WPARs, HP-UX SRP Containers, Docker, Podman)..."[0].

>you share your host kernel

Kernel != OS

>There are parts of the kernel that aren't namespaced as well. The kernel keyring is probably the big one.

Immaterial.

[0] https://en.m.wikipedia.org/wiki/OS-level_virtualization

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

#62

Post by advisedwang »

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.

In the opening sentence the author says they are using external-dns to set outside DNS to point to their cluster. You need the IP address for that.

(although they'd be better served by just using dynamic DNS rather than this complexity)

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

#63

Post by Spivak »

anonfordays wrote: post #61
Spivak wrote: post #60

Earlier quoted context omitted.

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.

>That isn't even true You are incorrect, this is true: "OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances, including containers (LXC, Solaris Containers, AIX WPARs, HP-UX SRP Containers, Docker, Podman)..." [0]. >you share your host kernel Kernel != OS >There are parts of the kernel that aren't namespaced as w…

You can call it what you want but absolutely no one considers chroot virtualization in any meaningful sense. Nothing is being virtualized, containers are just regular processes on the host system.

"OS Virtualization" != "OS" "Virtualization"

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

#64

Post by mystified5016 »

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. It'd take probably a dozen resets to get a return on that time investment so I just haven't bothered.

I'm not sure if this is a regular feature of fiber networks or just that my ISP is nice. So much better than DOCSIS when I'd randomly get booted off and given a new address.

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

#65

Post by dddw »

Aachen wrote: post #57
TZubiri wrote: post #12

Earlier quoted context omitted.

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…

For cheap storage at hetzner you could add a storagebox (not fast, but fine), or now even objecstorage.

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

#66

Post by from-nibly »

advisedwang wrote: post #62
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.

In the opening sentence the author says they are using external-dns to set outside DNS to point to their cluster. You need the IP address for that. (although they'd be better served by just using dynamic DNS rather than this complexity)

But why would you expose your cluster directly to the internet in the first place?

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

#69

Post by Daviey »

Daviey wrote: post #50
TZubiri wrote: post #47

Earlier quoted context omitted.

>how so? SPOF

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

@TZubiri, Then if that is a risk you accept, you could have multiple VPS's and load balance back to your home network, eliminating the new SPOF.

(@'ing because we reached the maximum reply limit)

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

#70

Post by TZubiri »

Spivak wrote: post #63
anonfordays wrote: post #61

Earlier quoted context omitted.

>That isn't even true You are incorrect, this is true: "OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances, including containers (LXC, Solaris Containers, AIX WPARs, HP-UX SRP Containers, Docker, Podman)..." [0]. >you share your host kernel Kernel != OS >There are parts of the kernel that aren't namespaced as w…

You can call it what you want but absolutely no one considers chroot virtualization in any meaningful sense. Nothing is being virtualized, containers are just regular processes on the host system. "OS Virtualization" != "OS" "Virtualization"

1st of all yes, many people consider not only chroot to be virtualization (of the file system). Yes it is arguable as it is the birth of lightweight virtualization. But you were wrong in saying no one does.

https://papers.freebsd.org/2000/phk-jails/

https://youtu.be/hgN8pCMLI2U?si=CH-Fpyj16bEWDZzc

2nd containers go farther and virtualize network, and other resources.

Post reply on HN