chore: Concurrency acceleration updateNodeClaimHash

[helen-frank]

Fixes #N/A

Description
Concurrency acceleration updateNodeClaimHash
How was this change tested?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: helen-frank
Once this PR has been reviewed and has the lgtm label, please assign njtran for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[coveralls]

Pull Request Test Coverage Report for Build 11357490965

Details

• 8 of 8 (100.0%) changed or added relevant lines in 1 file are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.04%) to 80.947%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/scheduling/requirements.go	2	98.01%

Totals
Change from base Build 11332670114:	0.04%
Covered Lines:	8493
Relevant Lines:	10492

---

💛 - Coveralls

[njtran]

I'm not sure I understand why this needs to change. How does this speed up performance? Also, is this not something you can do with workqueue.ParallelizeUntil?

[helen-frank]

I'm not sure I understand why this needs to change. How does this speed up performance? Also, is this not something you can do with workqueue.ParallelizeUntil?

Asynchronously to use kubeClient.Patch

I went and read the code for workqueue.ParallelizeUntil, and it's really better than what I was doing, thanks for the guidance!

[github-actions]

This PR has been inactive for 14 days. StaleBot will close this stale PR after 14 more days of inactivity.