Migrate current NPD CI Build job to k8s-infra-prow-build

[DigitalVeer]

This PR seeks to replicate the 403 error first encountered by @wangzhen127, as detailed here: #32222 (comment)

By reproducing this error, we aim to identify and address any underlying issues as we continue transitioning NPD CI jobs to community clusters. This is related to NPD jobs failing during migration, see: kubernetes/kubernetes#119211

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: DigitalVeer / name: Veer (cf6e5c3, 44940f6, 3fe1e78)

[k8s-ci-robot]

Welcome @DigitalVeer!

It looks like this is your first PR to kubernetes/test-infra 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/test-infra has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @DigitalVeer. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[wangzhen127]

/assign @wangzhen127

[wangzhen127]

Can you update your description with why we are doing this now?

[DigitalVeer]

Can you update your description with why we are doing this now?

Updated.

[wangzhen127]

/lgtm

[dims]

/ok-to-test
/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DigitalVeer, dims

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 [dims]

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]

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

In response to this:

This PR seeks to replicate the 403 error first encountered by @wangzhen127, as detailed here: #32222 (comment)

By reproducing this error, we aim to identify and address any underlying issues as we continue transitioning NPD CI jobs to community clusters. This is related to NPD jobs failing during migration, see: kubernetes/kubernetes#119211

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.