I work for a federal space where IPv6 native is a mandate. As someone who's working on k8s, we often have to build and patch everything ourselves to support that mandate. Want to pull a helm chart from a github repo? Gotta either dual stack the node or run a reverse proxy to make that happen.

I'd love to be at a point where everyone just dual stacked everything so that one day we can flip off the IPv4 switch.

Try NAT64. It'll let v6-only clients reach v4-only websites.

Interesting. I'll take a look! Thanks!

I think major failure of Kubernetes was not being IPv6-only from the beginning. Its model of every pod having own address works much better with IPv6 where addresses are cheap. With IPv4, it needs complicated overlay networks. The cluster boundary would also make a good place for NAT64 proxy.

Kubernetes didn't get IPv6 support until later, and it sounds like it isn't reliable yet.

> I think major failure of Kubernetes was

Heh. Kubernetes as a whole was a failed project at Google that got open sourced.

I was under the impression that Google simply latched onto the project? Doesn't Google still use borg to this day?

Corporate networks are not lagging for being ultra conservative; they lag, because the moment they start thinking about any change, their vendors start pushing all manners of products and licenses on them, that they insist are absolutely necessary for that change and it won't work without it. Sharks feel the blood in the water, and they want to make whatever is possible on it.

So in the end you are looking both at capex, increased opex and for what? You have ipv6? Congratulation, now you go to your C-level bosses and explain to them why it was worth it. Good luck.