"not ignoring it" .. "actively worked on" .. "for over 3 years" ..
Not to diminish the very real challenges in getting IPv6 implemented, but this is an interesting turn of phrase.. especially because rolling out IPv6 would actually solve a whole class of problems (and I'm not even a particularly big advocate of the need for IPv6, since most things should still be NATed anyway.)
(And especially considering parent's phrase "baked into the DNA" at Azure.)
Comments
They're not ignoring it. It's being actively worked on, and is expected to be in alpha for the 1.9 release [1].
The issue [2] has existed for over 3 years, so it's not a new suggestion.
[1] https://github.com/kubernetes/features/issues/508
[2] https://github.com/kubernetes/kubernetes/issues/1443
Not to diminish the very real challenges in getting IPv6 implemented, but this is an interesting turn of phrase.. especially because rolling out IPv6 would actually solve a whole class of problems (and I'm not even a particularly big advocate of the need for IPv6, since most things should still be NATed anyway.)
(And especially considering parent's phrase "baked into the DNA" at Azure.)
(And especially considering parent's phrase "baked into the DNA" at Azure.)
S/Azure/Microsoft/ -Azure has IPv6 but I think its Immature.
https://azure.microsoft.com/en-au/updates/ipv6-for-azure-vms... Is about the underlying VM architecture, not support for Kubernetes network models.