-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
speedup builds for core CI images #29195
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder 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 |
images/krte/cloudbuild.yaml
Outdated
@@ -28,6 +28,8 @@ substitutions: | |||
_CFSSL_VERSION: R1.2 | |||
options: | |||
substitution_option: ALLOW_LOOSE | |||
# this is a large and critical CI image, builds are slow on the default 1 core | |||
machineType: N1_HIGHCPU_32 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this takes longer to startup (there's a pre warmed pool of default machines) but is much more powerful
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
machineType: Cloud Build provides four high-CPU virtual machine types to run your builds: two machine types with 8 CPUs and two machine types with 32 CPUs. The default machine type is 1 CPU. Requesting a high-CPU virtual machine may increase the startup time of your build. Add the machineType option to request a virtual machine with a higher CPU:
https://cloud.google.com/build/docs/api/reference/rest/v1/projects.builds#machinetype
TODO: N1 vs E2. e2 are a big cheaper and might be a better choice, currently some project builds use n1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kubernetes/ingress-nginx#9813 and switched to e2 here
/lgtm |
/hold in case anyone has concern on the budget. Please feel free to unhold if it is not an concern. |
i'm going to switch to e2 type |
b5995b5
to
dbf0aa5
Compare
/lgtm |
/hold cancel |
a fix was merged for these images an hour ago and images are still not ready
let's give these a bit more oomph