Assigned
Status Update
No update yet.
Comments
ts...@google.com
Thanks for your report.
I will forward this feature request to our engineering team for review. Any updates about it will be posted here as well.
I will forward this feature request to our engineering team for review. Any updates about it will be posted here as well.
ts...@google.com
Currently, ‘gcr.io ’ hosts the images in the US. However, you can specify different registry hostname when creating a build [1]:
-us.gcr.io hosts your images in the United States
-eu.gcr.io hosts your images in the European Union
-asia.gcr.io hosts your images in Asia
Let me know if the above was able to address your request.
[1] Choosing a registry name:https://cloud.google.com/container-registry/docs/pushing-and-pulling#choosing_a_registry_name
-
-
-
Let me know if the above was able to address your request.
[1] Choosing a registry name:
ma...@gmail.com
Thank you for your reply,
That is I'm using right now. However, it seems that container registry perform the image push quite slowly when pushing toasia.gcr.io . So, if I could run the build closer to the storage region it would be faster.
I've submitted this feature request via the in-console suggestion system around April 14 and received a reply already, but I figured that a public status page would be better.
That is I'm using right now. However, it seems that container registry perform the image push quite slowly when pushing to
I've submitted this feature request via the in-console suggestion system around April 14 and received a reply already, but I figured that a public status page would be better.
ts...@google.com
Thank you for providing more details.
I have filed a feature request to our engineering team, but there is no guarantee that this feature will be implemented, and the ETA cannot be provided. Rest assured that your feedback is always taken into account, as it allows us to improve the platform.
Any future updates to this feature will be posted here.
I have filed a feature request to our engineering team, but there is no guarantee that this feature will be implemented, and the ETA cannot be provided. Rest assured that your feedback is always taken into account, as it allows us to improve the platform.
Any future updates to this feature will be posted here.
[Deleted User] <[Deleted User]>
Any news on this subject? This is not only an issue with pushing images, but maybe even more so for pulling images of custom build steps.
[Deleted User] <[Deleted User]>
As part of a cloud build we are calling third party APIs and being closer to them really speeds up build
[Deleted User] <[Deleted User]>
I can't use Resource Location Restriction for US because Cloud Build runs there. Possibility to define a region for a build would be great.
[Deleted User] <[Deleted User]>
Not being able to host images in the same region also incurs lots of network charges for transferring the images between Cloud Build and App Engine, for example.
We are located in South America and our bill has increased noticeably because of these charges.
We are located in South America and our bill has increased noticeably because of these charges.
[Deleted User] <[Deleted User]>
Is there already an update on this feature request? The issue still persists.
[Deleted User] <[Deleted User]>
Cloud build submit creates a [PROJECT_ID]_cloudbuild bucket in the US. This will ofcourse not work when resource restrictions apply. What you can do as a workaround is to create that bucket yourself in another location. You should do this before your first cloud build submit. I posted an explanation here: https://stackoverflow.com/questions/53206667/cloud-build-fails-with-resource-location-constraint/61269496#61269496
me...@kieranbenton.com
That doesn't help. You're then locating the storage bucket in a region different to where the builds are run which a) adds lots of latency to builds and b) adds egress cost as data gets moved between regions. This issue still stands and I think I'm not the only one who is beginning to lose faith that Google actually recognises the importance any of these real world problems.
[Deleted User] <[Deleted User]>
I don't say this is a perfect solution, it is a workaround. This at least enables you to put a resource restriction in place. Not putting a resource restriction in place because of one single faulty service is not an option for us. I feel the same frustration, this issue has been open for almost 3 years. Google does not seem to understand the issue, because they always respond that you can put container images in other regions than the US, which is totally irrelevant. Cloud build needs to be able to run in any region.
pe...@flunder.io
This is really needed. We almost double the cost of our Cloud Build (we're using a 32-core-machine) because of network traffic costs. We host everything inside the EU and have to transfer GBs upon GBs to the US on each and every build.
It would be much cheaper to just add a node pool to one of our GKE clusters, use preemptible machines and run `cloud-build-local`. But that's nothing we want to build or maintain, of course.
Is there an ETA when more regions will become available for Cloud Build?
It would be much cheaper to just add a node pool to one of our GKE clusters, use preemptible machines and run `cloud-build-local`. But that's nothing we want to build or maintain, of course.
Is there an ETA when more regions will become available for Cloud Build?
gr...@ottogroup.com
- there is an alpha feature that allows you to define worker pool for Cloud Build [1] - however you will get increase of cost due to paying for compute instances.
- I think that this feature is coming soon as "gcloud build submit" offers flag --region that currently need a GCP employee action to be able to use it [2] - try to use it and you will get instruction.
[1]
[2]
ju...@gmail.com
The instruction is useless since the provided contact e-mail address in the instruction is out of service. I think we just have to wait and see what happens.
ak...@gmail.com
What is the status of this request (the --region) flag in particular?
My costs are minuscule but I see the same problems already described above. Would like to participate in an alpha if also hobbyist/maker level participation is okay.
ERROR: (gcloud.builds.submit) PERMISSION_DENIED: project is not on the allowlist for Regional Cloud Build, please contact Google Cloud Support at
https://cloud.google.com/support-hub
er...@retailnext.net
Note: Despite the launch of Private pools, we still want this feature.
Private pools incur a price markup and impose a configuration maintenance burden that is not warranted when there is no need to allow access to resources in a private network.
For circumstances where where the only concern is network latency to resources that are not geographically distributed, we still need the ability to specify what region a build happens in. (Such resources might not be within GCP at all!)
cb...@ztb.icb.commerzbank.com
We are also requiring the build region feature, adding the same arguments as #18.
What is the roadmap on this one?
What is the roadmap on this one?
be...@google.com
cb...@ztb.icb.commerzbank.com
@#20: Private Pools require a configuration for Hard Disk size, network, and CPU type. What we actually need is a seamless, cloud-native solution as Cloud Build, with a location drop-down added. Havin additional configurations may help, but in this case it is a priori not known, which values are good to choose, let alone that this is obviously not required for Cloud Build without Private Pools.
So the feature request would still hold.
So the feature request would still hold.
Description
However, as our servers are in the SEA region we would use