karpenter_scheduler_unfinished_work_seconds is not registered with the Prometheus Registry

[jonathan-innis]

Description

Observed Behavior:

The karpenter_scheduler_unfinished_work_seconds metric is never registered with the metric registry which means that we aren't emitting it from our metrics endpoint like we'd intended to

Expected Behavior:

karpenter_scheduler_unfinished_work_seconds should be properly emitted from the metrics endpoint

Reproduction Steps (Please include YAML):

➜  karpenter git:(main) ✗ curl localhost:8080/metrics -s | grep operator | head
controller_runtime_active_workers{controller="operatorpkg.ec2nodeclass.status"} 0
controller_runtime_active_workers{controller="operatorpkg.node.status"} 0
controller_runtime_active_workers{controller="operatorpkg.nodeclaim.status"} 0
controller_runtime_active_workers{controller="operatorpkg.nodepool.status"} 0
controller_runtime_max_concurrent_reconciles{controller="operatorpkg.ec2nodeclass.status"} 10
controller_runtime_max_concurrent_reconciles{controller="operatorpkg.node.status"} 10
controller_runtime_max_concurrent_reconciles{controller="operatorpkg.nodeclaim.status"} 10
controller_runtime_max_concurrent_reconciles{controller="operatorpkg.nodepool.status"} 10
controller_runtime_reconcile_errors_total{controller="operatorpkg.ec2nodeclass.status"} 0
controller_runtime_reconcile_errors_total{controller="operatorpkg.node.status"} 0

➜  karpenter git:(main) ✗ curl localhost:8080/metrics -s | grep karpenter_scheduler_unfinished_work_seconds | head

Versions:

• Chart Version: 1.2.1
• Kubernetes Version (kubectl version): v1.32.2

• 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

[jonathan-innis]

/help
/good-first-issue
/triage accepted

[k8s-ci-robot]

@jonathan-innis:
This request has been marked as suitable for new contributors.

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-good-first-issue command.

In response to this:

/help
/good-first-issue
/triage accepted

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.

[manalilatkar]

/assign