helm: remove defaults CPU limits

[budimanjojo]

Fixes: https://github.com/kubernetes-sigs/node-feature-discovery/issues/1724

Having defaults CPU limits set is causing high CPU throttling on at least the gc pod. Memory and CPU are two different resources and having CPU limits configured is actually causing more problem than solving problem.

This is a good read: https://home.robusta.dev/blog/stop-using-cpu-limits

[linux-foundation-easycla[bot]]

• :white_check_mark:login: budimanjojo / (3d62382cd1b62db1b3c048afede728fb82d687cf)

The committers listed above are authorized under a signed CLA.

Welcome @budimanjojo!

It looks like this is your first PR to kubernetes-sigs/node-feature-discovery 🎉. 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-sigs/node-feature-discovery 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. :smiley:

[k8s-ci-robot]

Hi @budimanjojo. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[netlify[bot]]

✅ Deploy Preview for kubernetes-sigs-nfd ready!

Name	Link
🔨 Latest commit	3d62382cd1b62db1b3c048afede728fb82d687cf
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-nfd/deploys/66580b7c241b730008a7b5f4
😎 Deploy Preview	https://deploy-preview-1728--kubernetes-sigs-nfd.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: budimanjojo, marquiz

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: - ~~[OWNERS](https://github.com/kubernetes-sigs/node-feature-discovery/blob/master/OWNERS)~~ [marquiz] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[marquiz]

/lgtm /cherry-pick release-0.16

[k8s-infra-cherrypick-robot]

@marquiz: once the present PR merges, I will cherry-pick it on top of release-0.16 in a new PR and assign it to you.

In response to [this](https://github.com/kubernetes-sigs/node-feature-discovery/pull/1728#issuecomment-2154303694): >/lgtm >/cherry-pick release-0.16 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: c7f82178a38b36d39e6c8686c856b610c5326e2c

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.55%. Comparing base (560905f) to head (3d62382). Report is 2 commits behind head on master.

Additional details and impacted files

[](https://app.codecov.io/gh/kubernetes-sigs/node-feature-discovery/pull/1728?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kubernetes-sigs) ```diff @@ Coverage Diff @@ ## master #1728 +/- ## ======================================= Coverage 39.54% 39.55% ======================================= Files 80 80 Lines 7153 7173 +20 ======================================= + Hits 2829 2837 +8 - Misses 4064 4074 +10 - Partials 260 262 +2 ``` [see 1 file with indirect coverage changes](https://app.codecov.io/gh/kubernetes-sigs/node-feature-discovery/pull/1728/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kubernetes-sigs)

[k8s-infra-cherrypick-robot]

@marquiz: new pull request created: #1736

In response to [this](https://github.com/kubernetes-sigs/node-feature-discovery/pull/1728#issuecomment-2154303694): >/lgtm >/cherry-pick release-0.16 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.