cancel the per sig nodepool experiment

[upodroid]

We conducted a nodepool per sig experiment and we decided to not proceed with it. So I'm reverting the jobs using this nodepool back to using the main GKE nodepools. They are more performant and faster than the current N4 instances used by this node pool.

xref: kubernetes/k8s.io#8004

Part of kubernetes/k8s.io#8672

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: upodroid

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:

• config/jobs/kubernetes/sig-node/OWNERS [upodroid]
• config/jobs/kubernetes/sig-release/OWNERS [upodroid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ameukam]

/lgtm

[k8s-ci-robot]

@upodroid: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key node-kubelet.yaml using file config/jobs/kubernetes/sig-node/node-kubelet.yaml
• key sig-node-presubmit.yaml using file config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml
• key 1.34.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.34.yaml

In response to this:

We conducted a nodepool per sig experiment and we decided to not proceed with it. So I'm reverting the jobs using this nodepool back to using the main GKE nodepools. They are more performant and faster than the current N4 instances used by this node pool.

xref: kubernetes/k8s.io#8004

Part of kubernetes/k8s.io#8672

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-sigs/prow repository.