Skip to content

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

Open
@jonathan-innis

Description

@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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.performanceIssues relating to performance (memory usage, cpu usage, timing)priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions