Assigned
Status Update
Comments
go...@google.com <go...@google.com>
go...@google.com <go...@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
go...@google.com <go...@google.com>
cm...@gmail.com <cm...@gmail.com> #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?
cm...@gmail.com <cm...@gmail.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.
Description
Hello,
This is a reproduction of an issue filed in the Helm repository (in case the issue is actually on the GCP side):https://github.com/helm/helm/issues/11415
Problem you have encountered:
I'm seeing an issue on version 3.10.0 of helm where push/pull to/from GCP Artifact Registry seems to randomly hang. For example, maybe 2 out of 3 times, a pull will work, but then it seems to hang.
When things work, it looks like this:
But then when it hangs, it looks like this:
What you expected to happen: I expect pulls and push with Helm to not hang.
Steps to reproduce: Attempt to pull a chart from a GCP Artifact Registry Helm repository and note that it can hang. E.g. attempting to do something like this a few times usually results in Helm hanging:
helm pull oci://us-west1-docker.pkg.dev/PROJECT_NAME_HERE/REPO_NAME_HERE/CHART_NAME_HERE --version CHART_VERSION_HERE --debug
Other information (workarounds you have tried, documentation consulted, etc): I have been able to work around this by leveraging the
timeout
command in build scripts. e.g.for example: