Closed jichenjc closed 3 years ago
@seanschneeweiss can you help to provide some comments?
I think that most metrics were migrated to legacyregistry
as part of the KEP-1209: Metrics Stability Framework.
As far as I understand it, we are already using Prometheus wrapped behind the k8s.io/component-base/metrics
package.
Most other cloud providers are also creating metrics similar to us.
E.g. this PR moves from Prometheus to k8s.io/component-base/metrics
.
Not sure if we should move "back".
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
@jichenjc Can we close this?
ok, let's close this
Is this a BUG REPORT or FEATURE REQUEST?:
What happened: https://github.com/kubernetes/cloud-provider-openstack/blob/master/pkg/metrics/metrics_reconcile.go#L23 is using legacy metrics, can we move to prometheus (more up-to-date)
What you expected to happen:
How to reproduce it:
Anything else we need to know?:
Environment: