feat(nodeclaim): use PodScheduled's status for lastPodEventTime

[flavono123]

Fixes #1965

Description

use PodScheduled's lastTransitionTime for NodeClaim.LastPodEventTime
actually, only for the pod is bound to node so it still has same timestamp value for terminal and terminating
(should we follow deletionTimestamp or some risks are if then?)
the mitigations by dedupeTimestamp are removed
filter for registering more precise only for the PodScheduled has changed

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]

Hi @flavono123. 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[coveralls]

Pull Request Test Coverage Report for Build 15176079615

Details

• 19 of 31 (61.29%) changed or added relevant lines in 2 files are covered.
• 11 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.07%) to 81.918%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pkg/controllers/nodeclaim/podevents/controller.go	18	30	60.0%

Files with Coverage Reduction	New Missed Lines	%
pkg/controllers/disruption/consolidation.go	4	85.55%
pkg/controllers/provisioning/scheduling/preferences.go	7	88.76%

Totals
Change from base Build 15175060207:	-0.07%
Covered Lines:	10189
Relevant Lines:	12438

---

💛 - Coveralls

[jonathan-innis]

/assign @jonathan-innis

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: flavono123
Once this PR has been reviewed and has the lgtm label, please ask for approval from jonathan-innis. For more information see the 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

[flavono123]

https://github.com/kubernetes-sigs/karpenter/actions/runs/14214081694/job/39826657535?pr=2054#step:5:642
the failure of ci seems to be flaky but no idea why

[jonathan-innis]

This needs to be max otherwise it's going to oscillate around as different pods get reconciled. Also, I think still applying a dedupe timeout makes sense -- basically, if the current stored time is within (say 10s) of the new time, then don't update it

[flavono123]

ammended

[jonathan-innis]

@flavono123 Just checking in on this one!