Pod events controllers should use PodScheduled's lastTransitionTime to mark when pod events occur

[jonathan-innis]

We use our in-memory view of the pod cache right now to mark that pods have been bound to nodes or that they have initiated deletion; however, this is just based on us seeing the events -- it would be nice if we could rely on pod status conditions for this information.

Also, with this change, we should remove our need to watch Create events when Karpenter first starts-up which currently removes the Consolidatable status condition across all NodeClaims across the board due to a reconciliation of the Pod being triggered on Create

[jonathan-innis]

/kind cleanup

[jonathan-innis]

/triage accepted

[jonathan-innis]

/help

[k8s-ci-robot]

@jonathan-innis:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

[jonathan-innis]

/priority important-soon

[flavono123]

/assign

[flavono123]

to clarify the requirement, the cache field, NodeClaimStatus.LastPodEventTime should be deleted right?