Skip to content

Add karpenter_pods_disrupted_total when NodeClaims are disrupted #2020

Open
@jonathan-innis

Description

@jonathan-innis

Description

What problem are you trying to solve?

It's useful to know how many pods are disrupted by a particular reason in the same way it's useful to know how many NodeClaims are disrupted by a particular reason -- this update would also require an update to the CloudProviders. We basically need to look-up the count of reschedulable pods that we are disrupting right next to the call that we make to increment the karpenter_nodeclaims_disrupted_total metric

How important is this feature to you?

Brings more visibility to the impact of the different disruption reasons across the system

  • 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

No one assigned

    Labels

    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.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