Switch NPD jobs to GCP-hosted clusters

[mmiranda96]

What does this PR do?

Update the cluster for NPD jobs to k8s-infra-prow-build, which is community-owned (some jobs can run in EKS-hosted cluster, but I think it's better to have them all in the same GCP-hosted cluster for consistency reasons).

The only exception is for jobs that require to upload files to a GCS bucket. These jobs will remain on Google-owned cluster default until we are able to grant all the missing permissions to cluster k8s-infra-prow-build:

• ci-npd-build
• pull-npd-e2e-node
• pull-npd-e2e-kubernetes-gce-gci
• pull-npd-e2e-kubernetes-gce-gci-custom-flags
• pull-npd-e2e-kubernetes-gce-ubuntu
• pull-npd-e2e-kubernetes-gce-ubuntu-custom-flags

/assign @SergeyKanzhelev
/cc @MartinForReal

[SergeyKanzhelev]

/lgtm
/approve

let's revert for now

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mmiranda96, SergeyKanzhelev

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/node-problem-detector/OWNERS [SergeyKanzhelev]

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

[k8s-ci-robot]

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

• key node-problem-detector-ci.yaml using file config/jobs/kubernetes/node-problem-detector/node-problem-detector-ci.yaml
• key node-problem-detector-presubmits.yaml using file config/jobs/kubernetes/node-problem-detector/node-problem-detector-presubmits.yaml

In response to this:

What does this PR do?

Update the cluster for NPD jobs to k8s-infra-prow-build, which is community-owned (some jobs can run in EKS-hosted cluster, but I think it's better to have them all in the same GCP-hosted cluster for consistency reasons).

The only exception is for jobs that require to upload files to a GCS bucket. These jobs will remain on Google-owned cluster default until we are able to grant all the missing permissions to cluster k8s-infra-prow-build:

• ci-npd-build
• pull-npd-e2e-node
• pull-npd-e2e-kubernetes-gce-gci
• pull-npd-e2e-kubernetes-gce-gci-custom-flags
• pull-npd-e2e-kubernetes-gce-ubuntu
• pull-npd-e2e-kubernetes-gce-ubuntu-custom-flags

/assign @SergeyKanzhelev
/cc @MartinForReal

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.

[rjsadow]

The only exception is for jobs that require to upload files to a GCS bucket. These jobs will remain on Google-owned cluster default until we are able to grant all the missing permissions to cluster k8s-infra-prow-build:
* ci-npd-build
* pull-npd-e2e-node
* pull-npd-e2e-kubernetes-gce-gci
* pull-npd-e2e-kubernetes-gce-gci-custom-flags
* pull-npd-e2e-kubernetes-gce-ubuntu
* pull-npd-e2e-kubernetes-gce-ubuntu-custom-flags

@SergeyKanzhelev @ameukam do you see any reason these jobs can't be moved now? I'm not sure what the original issue with uploading to GCS buckets was but there's nothing that stands out to me about these jobs now that should prevent a migration.