UPDATE: IPv6 load balancer endpoints are now GA.1 However, we continue to work on instance-level v6 addressing. Since I believe that at least some votes on this issue are for v6 all the way to the instance, I am leaving this issue open.
It is possible to partially solve the problem by implementing allow IP protocol 41 on the firewall.
This solution is easier to implement, it seems.
Vote for that, too
Ben Sjoberg commented
This is more relevant than ever now that GCE is going to start charging for public IPv4 addresses. Most of our backend servers don't need public IPv4 at all - users reach them via load balancer. Many (most?) of the 3rd party APIs we talk to support IPv6, so that traffic could avoid going through Cloud NAT. (Saving 4.5 cents per GB, which really adds up.)
We'd like to switch our Startup's servers from a German On-Premise Server to GCE, but we can't, since many of our clients are connected to their ISPs via IPv6, and we'd have to introduce additional infrastructure (in the form of a load balancer) just to provide the same functionality we're offering now.
Jon Cutting commented
AWS allows us to configure IPv6 to their EC2 instances, and it rocks. I was really surprised to see that GCP does not yet support this feature. And a bit disappointed in truth, as it means we can't use GCP for a particular use case.
Erica turner commented
You have posted a fantastic blog! This is the best blog, most concise step by step guide. For any issue regarding canon printer visit our blog
Excellent and nice post. This is such a great resource that you are providing and you give it away for free. I love seeing that understands the value. I'm glad to have found this post as its such an interesting one! I have also something very interesting for you. Visit our blog post- http://www.applesupport247.com/blog/how-to-fix-mac-error-code-1407/
Excellent and nice post. This is such a great resource that you are providing and you give it away for free. I love seeing that understands the value. I'm glad to have found this post as its such an interesting one! I have also something very interesting for you. Visit our blog post-
brother printer commented
Hello, it is a great post. It's been such a wonderful experience while reading your blog.
If facing any problem related to a printer please visit https://www.brotherprintersupport247.com/blog/how-to-fix-error-code-e52-in-brother-printer/
and call us on toll-free no. USA: +1-888-633-7151; UK: +44-808-164-5280 for any technical support assistance.
HP Support Assistant commented
Thank for this awesome blog with great content, which I found very useful. Your blog will be very beneficial for everyone. I have bookmarked your website. Please keep your effort continuous and keep providing us your valuable information and suggestions.
Also, visit blog posted by John Brown.Dial+18886337151 (Toll-Free) for the USA, and Dial +448081645280 for the UK.
">Visit Now HP Support Assistant</a>
Fabien Lescelliere-Dumilly commented
No IPv6 at VM level (for UDP services), reason why my company remains on AWS
Net Hunter commented
too bad no ipv6
Most of the other cloud platforms fully support IPv6. this is a huge let down for me.
Christian Hujer commented
Wow. I just migrated to GCP CE and I am surprised that there is no proper IPv6 support yet. For me, that's a downgrade from my previous hoster who already supported IPv6 when I moved there in 2014. I'll move away from GCP CE just two days after setting up everything now that I've discovered that GCP CE does not have proper IPv6 support.
Should I have checked this beforehand? NO! Not in 2019! The IPv6 draft is from 1998!
I agree that this issue should be kept open until there is proper instance-level IPv6 access.
Bruno Rijsman commented
+1 for instance level IPv6 (I need IPv6 support in Travis-CI and it runs on GCE).
Steven Hartland commented
IPv6 support at the instance level is requirement for hosting mobile games, ATM we'll be forced to use AWS for this due to the lack of GCE support for it.
+1 level IPv6
Randall Mason commented
I am also interested in instance level IPv6. Thanks for a great product.
lynn wilkins commented
Instance ipV6 will be useful.
My home machine is ipV6, thank you Comcast.
But my google compute engine can't scp a result file to my home machine.
Yes I can use scp to pull a file from the compute engine. That is awkward when I just want to
have the file show up in my results directory after a nights run.
So, yes, we need ipV6 to and from the compute engine.
+1 for instance level IPv6.
Adam Ierymenko commented
IPv6 through to compute engine is critical for things other than just HTTP. The entire Internet is not HTTP. There's VoIP, P2P protocols, game protocols, DNS, and numerous other things. There are also protocols that want to see the inbound IP of connections and load balancers hide that.