[homodyne]

It's really concerning that we have people trying to use tools like Kubernetes without understanding the basics that underlie them, like networking.

Post author should read Beej's Guide to Network Programming and come back when that's comfortable for them.

[vegarde]

All of that is sort of "best effort" when it comes to the home market. While an ISP should honor it and give you the same IP address (or IPv6 range), at home we're in the consumer market where it's good enough if you're able to hit youtube from your browser.

I know my way around networking, I know that my networking equipment will always try to request the same IP address/IPV6 range. But I can't do shit with it if my ISP has lost my reservation and given that to someone else.

And as numerous other comments here have shown, some ISPs are incompetent bordering on malicious, but sometimes, they're the best you have. My ISP is pretty decent, but that doesn't keep me from playing with "what if"-scenarios and solve things that may not ever happen for me.

I learnt something from it - not the core networking stuff, there is nothing in that that was new to me, but I leart a lot about how to do things more dynamically in Kubernetes, and I had to dig into the APIs of my router to achieve what I needed.

However, when I write a blog post, I also try to assume not everyone has a deep understanding of the things. If someone read my blog post and just then learnt about IPv6 addressing, that's great! Then they too would have learnt some things, even if Kubernetes is not for them.