fix: skip provisioning pods already claimed by healthy in-flight NodeClaims - #3243
fix: skip provisioning pods already claimed by healthy in-flight NodeClaims#3243aardbol wants to merge 3 commits into
Conversation
|
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: aardbol The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Welcome @aardbol! |
complexity 14 of func"
Fixes #3121
Description
Karpenter was launching duplicate NodeClaims for the same pending pods while their first NodeClaim was still in-flight (not yet registered/initialized). The pod→NodeClaim mapping existed but was only used for metrics. GetPendingPods now skips pods already claimed by a healthy in-flight NodeClaim, and releases them when that claim goes away (deleted, terminating, launch/registration timeout, or initialized), so no excess nodes are launched during the registration window.
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.