-
Notifications
You must be signed in to change notification settings - Fork 828
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
prow: match prow-build-trusted nodepool to prow-build #2479
Conversation
the motivating factor here is trying to run the triage job on this cluster, which asks for more memory than an n1-standard-8 can provide but in general I can't think of a good reason to restrict this cluster to less resources than the regular prow-build cluster, while having it match the cluster would create less surprises when transferring a job from one to the other for whatever reason
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
FYI #2438. |
I'd rather tackle changing instance type later, achieving parity is my goal for now |
/hold cancel |
Uh... why did it not change any of the nodepool settings?
|
OK, I figured out why, PR is here: #2480 Going to apply with that change
|
|
💸 💸 |
the motivating factor here is trying to run the triage job on this
cluster, which asks for more memory than an n1-standard-8 can provide
but in general I can't think of a good reason to restrict this cluster
to less resources than the regular prow-build cluster, while having it
match the cluster would create less surprises when transferring a job
from one to the other for whatever reason