Assigned
Status Update
Comments
ji...@google.com <ji...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
he...@ard-poc.de <he...@ard-poc.de> #3
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
fu...@google.com <fu...@google.com> #4
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
fu...@google.com <fu...@google.com> #5
This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)
go...@google.com <go...@google.com> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
sa...@google.com <sa...@google.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
iv...@google.com <iv...@google.com> #8
Any progress in here?
de...@keybank.com <de...@keybank.com> #9
I would like this feature as well.
ba...@google.com <ba...@google.com>
ab...@google.com <ab...@google.com> #10
Hello, any progress in here? Please is very frustrating.
nc...@google.com <nc...@google.com> #11
Hi, open request for more than 3 years for a simple change. Please proceed that.
sa...@google.com <sa...@google.com> #12
+1. :(
Description
Assign a new static internal IP address to a running VM instance.
How this might work:
Log in into a VM and assign a new static internal IP address using a traditional way.
If applicable, reasons why alternative solutions are not sufficient:
There is no alternative solution. You can, promote the ephemeral internal IP address of a resource to a static internal IP.
Other information (workarounds you have tried, documentation consulted, etc):