🌱 metrics: use v1beta2 for condition metrics and add metrics for dockercluster devcluster dockermachine devmachine extensionconfig ipaddressclaim and crs

[chrischdi]

What this PR does / why we need it:

Changes all condition metrics to expose metrics from v1beta2 structs.

Adds new metrics for (only condition metrics for v1beta2):

• dockercluster
• devcluster
• dockermachine
• devmachine
• extensionconfig
• ipaddressclaim
• clusterresourceset

Generated via #9347

/area devtools

Generated via:

git checkout chrischdi/pr-update-crd-metrics-config
make generate-metrics-config
cp config/metrics/metrics.yaml config/metrics/crd-metrics-config.yaml
cp config/metrics/rbac.yaml config/metrics/crd-clusterrole.yaml

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[sbueringer]

I wonder if we should just only emit v1beta2 conditions without a v1beta2 string in the metric name.

This gives us future proof metrics from now onwards

(we also know that v1beta1 conditions are not exactly perfect)

[sbueringer]

In general seems fine. Obviously did not review the diff of the metrics config. I'll do that eventually on 9347.

Did you check that our Grafana dashboards still work? (specifically the ones using conditions)

[chrischdi]

In general seems fine. Obviously did not review the diff of the metrics config. I'll do that eventually on 9347.

Did you check that our Grafana dashboards still work? (specifically the ones using conditions)

checked and adjusted dashboards a bit. Hope I catched all cases.

[sbueringer]

Thank you very much!

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: 16c2f03c9bc03fef869e3fd61c44cd9af631c3de

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

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

[chrischdi]

/cherry-pick release-1.10

[k8s-infra-cherrypick-robot]

@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.10 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-1.10

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.

[k8s-infra-cherrypick-robot]

@chrischdi: new pull request created: #12041

Details

In response to this:

/cherry-pick release-1.10

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.