Hacker News Reader

you'd think such a project so heavily supported by Google would have IPv6 support. Hell, you'd think it'd be native/first-class.

View on HN

Yes, it's a known issue. Pull requests welcome. https://github.com/kubernetes/kubernetes/issues/1443#issueco...

Yes, please! It's a pretty deep problem, so we'd love the help.

Disclosure: I work at Google on Kubernetes.

Isn't IPv6 mostly for internet traffic, where 32 bits of address space isn't enough? Why not just route IP6 traffic to a Kubernetes cluster, and have that cluster use IPv4 internally? Is there something more to IPv6 than the increased address space that I'm missing?

Then you need gateways that keep track of and translate every connection, and special ways to tell your backends the client IP (e.g. for logging, fraud detection, ...). Dealing with IPv4 to clients with an IPv6 backend is easier than the other way around.

This recent discussion had more comments on that: https://news.ycombinator.com/item?id=13085941

Reply on news.ycombinator.com