In Progress
Status Update
Comments
mo...@google.com <mo...@google.com>
[Deleted User] <[Deleted User]> #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
ha...@digitalis.io <ha...@digitalis.io> #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?
[Deleted User] <[Deleted User]> #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.
va...@google.com <va...@google.com>
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@google.com>
se...@gmail.com <se...@gmail.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)
lo...@google.com <lo...@google.com> #6 Restricted+
Restricted+
Comment has been deleted.
an...@macheye.com <an...@macheye.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
jo...@vsoft.com.br <jo...@vsoft.com.br> #8
Any progress in here?
aa...@virtru.com <aa...@virtru.com> #9
I would like this feature as well.
Description
What you would like to accomplish: Custom Domain Names for Artifact Registry registries.
How this might work: With an option to map a Domain Name to the registries, like in other products.
If applicable, reasons why alternative solutions are not sufficient: The only alternative [1] has two main problems: It is only available for Docker, and it requires the registry to be publicly accessible.
Other information (workarounds you have tried, documentation consulted, etc) [1]https://cloud.google.com/blog/topics/developers-practitioners/hack-your-own-custom-domains-container-registry