please consider e2 instead of n1 for builds

[BenTheElder]

Should be cheaper with comparable performance https://cloud.google.com/blog/products/compute/google-compute-engine-gets-new-e2-vm-machine-types

https://github.com/search?q=repo%3Akubernetes%2Fingress-nginx%20n1_highcpu&type=code

ref: kubernetes/test-infra#29195

I need to do this in KIND as well :-)

/sig k8s-infra
/sig network
/kind cleanup

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[longwuyuan]

/assign

[BenTheElder]

re: priority kubernetes/k8s.io#5059

sigh, not actually cheaper, oh well! still seems best to switch as these are the default documented etc, and I feel like it wouldn't be surprising if the pricing eventually updated or they were no longer offered since N1 is the oldest? GCE type