New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submit Build to Private Worker Pool #210
Comments
I figured it out, and it turns out I actually did ask in the right place, sort of. It turns out the Instead of passing the request to this endpoint:
...you have to pass it to this one:
...and specify a location that matches the location of your private worker pool. I can trick I am SO happy I figured this out. I'd be happy to work on a pull request to adjust |
I'm sorry I've not done this myself before so can't say for sure. The options looks correct - have you need to precreate a worker node pool for the jobs perhaps? (Kubernetes cluster I guess, but a managed one) |
Ah you figured it out, great :) yes a pull request would be much appreciated. |
I'll explore possible changes, but looking at it with fresh eyes today, I think making the entire package work with builds on private worker pools might involve deeper changes than I originally thought. That base API endpoint URL is baked into functions all over the place. For instance, I had to go through quite a few more contortions to get |
A function to make the URL then find/replace the hardcoded strings maybe. I had a similar pattern for using beta versions of the API |
I apologize for asking here, but I've simply hit a wall trying to figure this out from Google's documentation.
I'm trying to submit a build using googleCloudRunner to a private worker pool. I'm doing this by passing the argument:
to
cr_build
. I've checked an double checked that the service account submitting the build has the WorkerPool User role. But I just get a 404 workerpool not found error every time.I feel like I've done all the steps in the Google documentation, but clearly I'm missing something. Again, I realize this isn't a problem with your package, I just feel out of other options at this point.
The text was updated successfully, but these errors were encountered: