✨ Export DepthMetricWithPriority - #3597
alvaroaleman wants to merge 1 commit into
Conversation
Currently, it is impossible to get the priority dimension with a custom metric provider, because the internal MetricsProviderWithPriority references the internal DepthMetricWithPriority, making it impossible to implement the whole thing outside of controller-runtime itself.
|
@alvaroaleman: GitHub didn't allow me to assign the following users: sburinger. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Currently, it is impossible to get the priority dimension with a custom metric provider, because the internal MetricsProviderWithPriority references the internal DepthMetricWithPriority, making it impossible to implement the whole thing outside of controller-runtime itself.
/assign sburinger
/hold