Migrate remaining `sig-node` jobs to community clusters

[rjsadow]

The following jobs still run on the default google owned cluster and need to be migrated to a community cluster

node-problem-detector

• [ ] pull-npd-e2e-node | Search Results |
• [ ] pull-npd-e2e-kubernetes-gce-gci | Search Results |
• [ ] pull-npd-e2e-kubernetes-gce-gci-custom-flags | Search Results |
• [ ] pull-npd-e2e-kubernetes-gce-ubuntu | Search Results |
• [ ] pull-npd-e2e-kubernetes-gce-ubuntu-custom-flags | Search Results |
• [ ] ci-npd-build | Search Results |

containerd

• ~~pull-containerd-build | Search Results |~~
• ~~pull-containerd-node-e2e | Search Results |~~
• ~~pull-containerd-node-e2e-1-7 | Search Results |~~
• ~~pull-containerd-node-e2e-1-6 | Search Results |~~

[rjsadow]

/sig testing /sig k8s-infra /sig node

[kannon92]

/help wanted /good-first-issue

[k8s-ci-robot]

@kannon92: 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:

/help wanted /good-first-issue

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.

[Bharadwajshivam28]

Hey @rjsadow and @kannon92 I would like to work on this

[SD-13]

/assign I can work on node-problem-detector @Bharadwajshivam28 would you like to work on the containerd jobs?

[Bharadwajshivam28]

/assign I can work on node-problem-detector @Bharadwajshivam28 would you like to work on the containerd jobs?

Ya works for me 😀

[Bharadwajshivam28]

/assign

Working on containerd one

[SD-13]

@rjsadow FYI, node-problem-detector is migrated in this issue https://github.com/kubernetes/kubernetes/issues/119211

[SD-13]

@Bharadwajshivam28 Are you working to migrate containerd jobs? If not, I can help with that.

[wangzhen127]

I tried to migrate the NPD tests but still saw the 403 Forbidden error. I am not sure why the same tests can work in CI, but not in presubmits, or vice versa. My PRs have been reverted. @SD-13 if you have time to investigate more, it would be really appreciated.

[Bharadwajshivam28]

@Bharadwajshivam28 Are you working to migrate containerd jobs? If not, I can help with that.

Hey you can go ahead with it

[SD-13]

/unassign @Bharadwajshivam28

[SD-13]

@wangzhen127 I will dig into this issue!

ERROR: failed to solve: failed to push gcr.io/node-problem-detector-staging/ci/node-problem-detector:v0.8.16-14-gb48e438-20240311.1409: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://gcr.io/v2/token?scope=repository%3Anode-problem-detector-staging%2Fci%2Fnode-problem-detector%3Apull%2Cpush&service=gcr.io: 403 Forbidden

Will start from these logs. Initially seems like, it didn't have necessary permissions or a good credential...

[endocrimes]

https://github.com/kubernetes/test-infra/pull/32261#issuecomment-1997960257

@ameukam do we have those documented anywhere? (if yes and they're solvable, point me in the right direction and i'll take a look in the next couple of weeks)