Status Update
Comments
lb...@google.com <lb...@google.com> #2
To solve this problem, create the two routes with different priorities, like this:
Route1: Destination:0.0.0.0/0<-------> Next hop: ILB(IN us-east1) <------> Priority:950
Route2: Destination:0.0.0.0/0<-------> Next Hop: ILB(IN us-west1) <------> Priority:951
As long as the forwarding rules aren't configured to be
From the perspective of us-west1, this route is available:
Route2: Destination:0.0.0.0/0<-------> Next Hop: ILB(IN us-west1) <------> Priority:951
From the perspective of us-east1, this one is available:
Route1: Destination:0.0.0.0/0<-------> Next hop: ILB(IN us-east1) <------> Priority:950
It doesn't matter that these have different priorities in the route table because only one is "active" in each region (as long as global access isn't configured).
fa...@google.com <fa...@google.com> #3
se...@myrepublic.net <se...@myrepublic.net> #4
Please add the possibility to rename.
It's really not understandable how simple things like changing a name can't be done.
ha...@sap.com <ha...@sap.com> #5
We also affected by this . Kindly check on this with priority and let us know when the feature will be done .
We see on all other Clouds , feature of rename on vpc subnets is available and we can do it without much efforts .
Thanks ,
Harirpasath.N
ha...@sap.com <ha...@sap.com> #6
Kindly let us know , what is the ETA for this request , as this issue is open since 2018 .
Thanks ,
Hariprasath.N
br...@brettjones.com <br...@brettjones.com> #7
br...@cannonballtrading.com <br...@cannonballtrading.com> #8
kt...@google.com <kt...@google.com> #9
Hello everyone,
Thank you for your ongoing patience. We know it's been a while since you don't hear back from us.
Be sure that we hear you, all new reports are being shared with the Product team. The Cloud VPC Engineering team is still working on this issue to provide a resolution.
Further updates, including a possible ETA will be posted in this thread.
to...@maxedadiygroup.com <to...@maxedadiygroup.com> #10
Thanks & regards, Tom
ro...@softchoice.com <ro...@softchoice.com> #11
pi...@gmail.com <pi...@gmail.com> #12
cc...@proveedorexterno.com <cc...@proveedorexterno.com> #13
gu...@ig.com <gu...@ig.com> #14
ch...@rewe-group.com <ch...@rewe-group.com> #15
As said before, naming ressources is a key and we would like to change descriptions without rebuilding everything
Best Regards
Chris
Description