Overhaul node e2e prow job definitions

[upodroid]

We need to overhaul the sig-node tests to enable testing various permutations of OSes, Architectures and CRIs on AWS and GCP. We can borrow the jobs generator used by kops at https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/kops/build_jobs.py to create these jobs at scale. I'm also going to use this opportunity to fix the following:

Tasks

Beta Give feedback

1. [umbrella issue] arm ci for node e2e testing #29693
   9 of 11
   kind/cleanup kind/failing-test sig/node sig/testing +4
   
2. Running node e2e tests on AWS #28899
   kind/feature lifecycle/stale priority/important-longterm sig/k8s-infra sig/node +5
3. ARM CI on EC2
4. kubetest2 CI migration enhancements#2464
   help wanted kind/kep priority/important-soon sig/release sig/testing stage/beta +6
   
5. Add support for running node-tester against EC2 kubernetes-sigs/kubetest2#230
   approved cncf-cla: yes lgtm size/M +4
   

   
6. Add kubetest2 support kubernetes-sigs/provider-aws-test-infra#39
   cncf-cla: yes size/L +2
7. Migrate jobs away from deprecated bootstrap usage #20760
   area/bootstrap area/jobs area/prow/pod-utilities help wanted kind/cleanup lifecycle/frozen priority/important-longterm sig/testing +8
8. Add node e2e grid tests #29944
   area/config area/jobs area/testgrid cncf-cla: yes lifecycle/rotten sig/node sig/testing size/XXL +8
   

   
9. Use a community-owned bucket k8s-staging-cri-tools instead of cri-containerd-staging #29995
   sig/k8s-infra sig/node sig/testing +3
10. Fix containerd-ci jobs https://prow.k8s.io/?job=ci-containerd-build-* . These jobs should run as post-submits instead of every 30 minutes + a weekly build(the bucket has a lifecycle policy to purge objects older than 60 days)
11. Provision a dedicated AWS account for Node e2e jobs k8s.io#5483
    priority/important-soon sig/k8s-infra +2
12. Adding guidance for test jobs in Sig Node #29969
    approved area/config area/jobs cncf-cla: yes lgtm sig/node sig/testing size/L +8
    

    

/sig node
/sig testing
/sig k8s-infra
/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.