Switch couldbuilds from N1 to E2 Machines

[BenTheElder]

EDIT: These are actually priced the same on cloud build only currently. I suspect we should switch anyhow (N1 type is outdated...), but this lowers the priority further.

https://cloud.google.com/build/pricing

Cloud Build continues to offer n1-highcpu-8 and n1-highcpu-32 machine types. They are offered at the same price as e2-highcpu-8 and e2-highcpu-32.

---

Original Issue:

The E2 machine type should have comparable performance but is newer and cheaper than N1 type. (Cheaper in general, NOT cheaper on cloudbuild, see above)

Many of our existing cloudbuilds for pushing images etc are using N1 type.

We should track these down and help update like kubernetes/ingress-nginx#9813.

This is NOT High priority, but this is simple, low-hanging fruit. Should be a good-first-issue

/good-first-issue
/help-wanted

This search query will locate usage within Kubernetes repos:
https://cs.k8s.io/?q=machineType%3A%20N1_HIGH&i=nope&files=&excludeFiles=&repos=

Currently I see these in:

• kubernetes/ingress-nginx Switch from N1 to E2 machine ingress-nginx#9820
• kubernetes-sigs/security-profiles-operator Switch from N1 to E2 machine for cloudbuild kubernetes-sigs/security-profiles-operator#1596
• kubernetes/release Switched from N1 to E2 machine release#2989
• kubernetes-sigs / etcdadm Switched from N1 to E2 machine kubernetes-retired/etcdadm#369
• kubernetes-sigs/kwok Switch couldbuilds from N1 to E2 Machines #5059
• kubernetes-sigs/promo-tools Switched from N1 to E2 machine kubernetes-sigs/promo-tools#807
• kubernetes-sigs/testgrid-json-exporter Switch from N1 to E2 machine for cloudbuild kubernetes-sigs/testgrid-json-exporter#12
• kubernetes/autoscaler Switched from N1 to E2 machine autoscaler#5641
• kubernetes/publishing-bot Switched from N1 to E2 machine publishing-bot#338

machineType: N1_ should be replaced with machineType: E2_

I've already updated kind and see also kubernetes/test-infra#29195 (comment)

Reference materials:
https://cloud.google.com/build/docs/build-config-file-schema#options
https://cloud.google.com/build/docs/api/reference/rest/v1/projects.builds#machinetype
https://cloud.google.com/blog/products/compute/google-compute-engine-gets-new-e2-vm-machine-types

/sig k8s-infra
/priority backlog

[k8s-ci-robot]

@BenTheElder:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

The E2 machine type should have comparable performance but is newer and cheaper than N1 type.

Many of our existing cloudbuilds for pushing images etc are using N1 type.

We should track these down and help update like kubernetes/ingress-nginx#9813.

This is NOT High priority, but this is simple, low-hanging fruit. Should be a good-first-issue

/good-first-issue
/help-wanted

This search query will locate usage within Kubernetes repos:
https://cs.k8s.io/?q=machineType%3A%20N1_HIGH&i=nope&files=&excludeFiles=&repos=

Currently I see these in:

• kubernetes/ingress-nginx tracked in please consider e2 instead of n1 for builds ingress-nginx#9813
• kubernetes-sigs/security-profiles-operator
• kubernetes/release
• kubernetes-sigs / etcdadm
• kubernetes-sigs/kwok
• kubernetes-sigs/promo-tools
• kubernetes-sigs/testgrid-json-exporter
• kubernetes/autoscaler
• kubernetes/publishing-bot

machineType: N1_ should be replaced with machineType: E2_

I've already updated kind and see also kubernetes/test-infra#29195 (comment)

Reference materials:
https://cloud.google.com/build/docs/build-config-file-schema#options
https://cloud.google.com/build/docs/api/reference/rest/v1/projects.builds#machinetype
https://cloud.google.com/blog/products/compute/google-compute-engine-gets-new-e2-vm-machine-types

/sig k8s-infra
/priority backlog

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sarab97]

/assign

[BenTheElder]

kubernetes-sigs/security-profiles-operator has remaining false-positive search results from vendor/ vendored code.

otherwise all repos have PRs open or merged already, updated the checklist. thanks @sarab97

[sarab97]

All PRs are merged. Closing this issue.
/close

[k8s-ci-robot]

@sarab97: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

All PRs are merged. Closing this issue.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.