5 ms·

AWS is miles ahead in IPv6 adoption though. Why do GCP employees always post in HN articles about how much "better" GCP is than AWS or how GCP "did it first"?

AWS is miles ahead in IPv6 adoption though. Why do GCP employees always post in HN articles about how much "better" GCP is than AWS or how GCP "did it first"? Our company literally can't use GCP, full stop, because Google is completely ignoring IPv6 support. I heard load balancers are now in beta, which just terminates IPv6 and connects to the back end with IPv4. When am I going to be able to make an outbound IPv6 connection from GCP? Specifically the Compute Engine VMs.

boulos 9y ago
The IPv6 termination is now GA, but I agree with your sentiment (we're behind on IPv6). That said, it's a very binary thing: you either have IPv6 throughout the virtual networking stack or you don't. We're not ignoring it, particularly since Google cares so deeply about IPv6 worldwide, but we are behind. Disclosure: I work on Google Cloud. Edit: I'm not sure why you're being downvoted, it's a fair criticism.
samstave 9y ago
Can you ELI5 what we ppl who are deploying to any cloud should have as First Principles WRT IPv6 and why we should be architecting around it? Disclosure: I like turtles.
- blasdel 9y ago
  Apple's App Store review has a hard requirement that everything works on a pure IPv6 network
  - soccerdave 9y ago
    The only thing that you have to do to satisfy this requirement is don’t hardcode IPv4 addresses in your app. If you are using domain names for everything then it doesn’t matter if those are only resolvable to v4 addresses.
    - snuxoll 9y ago
      Correct, using DNS on a IPv6 only network is enough since the point is to use DNS64/NAT64 to handle the transition until services are IPv6-native.
      - samstave 9y ago
        Please unpack this comment...
  - boulos 9y ago
    You don't necessarily need individual VMs to be IPv6 addressable to do this. That is, since our global load balancer already supports IPv6 termination, your app's API or website or whatever will be served as IPv6. Take a look at our announcement from last week for more info: https://cloudplatform.googleblog.com/2017/09/announcing-ipv6-global-load-balancing-ga.html https://cloudplatform.googleblog.com/2017/09/announcing-ipv6... Disclosure: I work on Google Cloud (so I indirectly benefit from you using our services)
oh_sigh 9y ago
Okay, sure, but those two things aren't related. (Disclosure: I'm supposed to be working right now)

boulos 9y ago

The IPv6 termination is now GA, but I agree with your sentiment (we're behind on IPv6). That said, it's a very binary thing: you either have IPv6 throughout the virtual networking stack or you don't. We're not ignoring it, particularly since Google cares so deeply about IPv6 worldwide, but we are behind. Disclosure: I work on Google Cloud. Edit: I'm not sure why you're being downvoted, it's a fair criticism.

samstave 9y ago

Can you ELI5 what we ppl who are deploying to any cloud should have as First Principles WRT IPv6 and why we should be architecting around it? Disclosure: I like turtles.

blasdel 9y ago
Apple's App Store review has a hard requirement that everything works on a pure IPv6 network
- soccerdave 9y ago
  The only thing that you have to do to satisfy this requirement is don’t hardcode IPv4 addresses in your app. If you are using domain names for everything then it doesn’t matter if those are only resolvable to v4 addresses.
  - snuxoll 9y ago
    Correct, using DNS on a IPv6 only network is enough since the point is to use DNS64/NAT64 to handle the transition until services are IPv6-native.
    - samstave 9y ago
      Please unpack this comment...
- boulos 9y ago
  You don't necessarily need individual VMs to be IPv6 addressable to do this. That is, since our global load balancer already supports IPv6 termination, your app's API or website or whatever will be served as IPv6. Take a look at our announcement from last week for more info: https://cloudplatform.googleblog.com/2017/09/announcing-ipv6-global-load-balancing-ga.html https://cloudplatform.googleblog.com/2017/09/announcing-ipv6... Disclosure: I work on Google Cloud (so I indirectly benefit from you using our services)

oh_sigh 9y ago

Okay, sure, but those two things aren't related. (Disclosure: I'm supposed to be working right now)