Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ Workqueue: Add controller label #2895

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

alvaroaleman
Copy link
Member

Currently, all controller-related metrics use the controller label to identity the controller. The workqueue metrics however use the name label instead. This is very confusing and unintuitive. Add the controller label to the workqueue as well with the same value as the existing name label. This keeps the cardinality the same, is backwards-compatible and allows using one label throughout for filtering.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 31, 2024
@k8s-ci-robot
Copy link
Contributor

[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

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 31, 2024
Currently, all controller-related metrics use the `controller` label to
identity the controller. The workqueue metrics however use the `name`
label instead. This is very confusing and unintuitive. Add the
`controller` label to the workqueue as well with the same value as the
existing `name` label. This keeps the cardinality the same, is
backwards-compatible and allows using one label throughout for
filtering.
@troy0820
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 31, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 7c2129bf55a96eb0cd1ddc3d1a083f4c0829950a

@k8s-ci-robot k8s-ci-robot merged commit 8d55456 into kubernetes-sigs:main Jul 31, 2024
9 checks passed
@sbueringer
Copy link
Member

Thx!

/lgtm

(cc @fabriziopandini @chrischdi should allows us to simplify our dashboards a bit, I'll make a note in CAPI to adjust once we bumped to the next CR release)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants