Skip to content

Support ignoring specific pods when calculating consolidateAfter #1921

Open
@rkilingr

Description

@rkilingr

Description

Observed Behavior:
We have a bunch of cronjobs running on a namespace with a maximum frequency of every 15m. Karpenter seems to be taking that into account on field lastPodEventTime preventing the node to be considered as Consolidatable

Expected Behavior:
CronJobs and ephemeral pods should not prevent node consolidation

Reproduction Steps (Please include YAML):
Have a nodepool with a spec.disruption.consolidateAfter field set to a duration longer than cronjob frequency, example 60m

Versions:

  • Chart Version: v1.0.6
  • Kubernetes Version (kubectl version): Server Version: version.Info{Major:"1", Minor:"30+", GitVersion:"v1.30.8-eks-2d5f260", GitCommit:"3c9802b10b3530b22ddb4727e2931f6b89bbb760", GitTreeState:"clean", BuildDate:"2024-12-12T23:09:04Z", GoVersion:"go1.22.9", Compiler:"gc", Platform:"linux/amd64"}
  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Activity

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

Metadata

Metadata

Assignees

Labels

consolidationkind/featureCategorizes issue or PR as related to a new feature.priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.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