migrate kubernetes/node-feature-discovery jobs to eks cluster

[iftachk]

jobs: migrate kubernetes/node-feature-discovery jobs to eks cluster

• Add missing resource blocks
  /priority important-longterm
  /area jobs

Part of #29722

[k8s-ci-robot]

Hi @iftachk. 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/test-infra repository.

[rjsadow]

/ok-to-test

[marquiz]

Thanks @iftachk for the patch.

Is there a reason to only convert some of the jobs and not all of them?

We also need to think about the resource requirements. Some of the jobs might want more than one cpu.

/cc @ArangoGutierrez

[iftachk]

@marquiz Thank you for your feedback

Regarding the per-resource definitions, feel free to review the PR and let me know which jobs might need more resources.

For the reason why I only changed some jobs and not all - please review this issue|29722 which includes some specific details on which jobs needs to be migrated eg (kubernetes-sigs/node-feature-discovery | Prow Results | Search Results)

For any follow-up questions, I would recommend reaching out to sig-k8s-infra or sig-testing

[rjsadow]

There are a few jobs listed here that we wont be able to migrate quite yet.

[ArangoGutierrez]

Thanks @iftachk for the patch.

Is there a reason to only convert some of the jobs and not all of them?

We also need to think about the resource requirements. Some of the jobs might want more than one cpu.

/cc @ArangoGutierrez

Agree @iftachk NFD could crash with just 1 CPU, for the rest it looks ok to me

[iftachk]

@ArangoGutierrez, as requested I've updated the resource blocks for the migrated NFD jobs
Would appreciate your feedback and approval in case it looks good to you.
Thanks,

[ArangoGutierrez]

@ArangoGutierrez, as requested I've updated the resource blocks for the migrated NFD jobs Would appreciate your feedback and approval in case it looks good to you. Thanks,

going to test the full e2e run with the given resources and reply back shortly after

[marquiz]

Thanks for the update @iftachk. While you're at it, could you convert all presubmit jobs (not just the most recently run, or I don't know how you picked these ones) so that all jobs would be consistently run on the same cluster?

[iftachk]

/retest

[ameukam]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameukam, iftachk

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-sigs/node-feature-discovery/OWNERS [ameukam]

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]

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

• key node-feature-discovery-presubmits-generic.yaml using file config/jobs/kubernetes-sigs/node-feature-discovery/node-feature-discovery-presubmits-generic.yaml
• key node-feature-discovery-presubmits-master.yaml using file config/jobs/kubernetes-sigs/node-feature-discovery/node-feature-discovery-presubmits-master.yaml

In response to this:

jobs: migrate kubernetes/node-feature-discovery jobs to eks cluster

• Add missing resource blocks
  /priority important-longterm
  /area jobs

Part of #29722

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.