4 ms·
Ohh thats interesting
by kristianpaul 5y ago
Ohh thats interesting
- ggm 5y agoYes. When I get a clear signal this is in GKE (I believe there is some lag between the k8s release and adoption in public service) I'd be very keen to try it. (selfish observation: I'm mostly hands-off so the pain will be felt by others) I also believe the blocker(s) on this were both k8s and the Google infrastructure. its possible GKE can host dualstack but the network can't forward it painlessly and its still edge proxied in over 4. Always made me wonder why they didn't do ULA internally and avoid some issues. I guess its the hidden painpoints on the traefik or other visible boundary which got in the way, although things other people say suggest the kubernetes people just didn't even think V6 when they designed their initial network stack. It always felt to me (as a non implementer) like the obvious fit. Guaranteed unique, private address space which can handle billions of addressed things on the "inside"
- dilyevsky 5y agoGCP still doesn’t support support ipv6 except on external interface in like four small regions and only as primary interface afaik so gke unlikely getting this any time soon
- ggm 5y agoPlus ça change.
- nijave 5y agoIt was only in the last few weeks AWS announced IPv6 only VPCs (although they've supported dual stack for a while)