News for hackers. Stuff that matters.

A comment on Kubernetes Networking: Behind the Scenes. Parent comment

Re:Kubernetes Networking: Behind the Scenes by mrweasel on Wednesday October 16, 2019 @04:21PM (#21275069)
IPv6 should not be an addition to Kubernetes, but the default. IPv4 could then be an addition for when you need external communication to IPv4 networks. There's no reason why IPv6 isn't the default for internal communication between containers.

We've been deploying IPv6 for at least 10 years and have hosts that are exclusively IPv6. Then along comes Docker and Kubernetes with their retro IPv4 only stack and now customer wonder why we're struggling to make containers work or suppliers that can't understand why we can't easily deploy the latest version of their software, which is only distributed as a Docker image.

[ Parent | on HN ]
Re:Kubernetes Networking: Behind the Scenes by pas on Wednesday October 16, 2019 @06:14PM (#21276553)
Well, since k8s is developed by mere humans on simple notebooks, and initially it got deployed to stock Linux they started with v4. And they had to start with v4. And to get more contributors they also needed v4.

Yes, the network effects are strong with this one.

But soon. Bit by bit, I hope the true dualstack will come, and then the v4 will fade away over generations.

[ Parent | on HN ]