-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Cleanup: remove prometheus dependencies for volume #98729
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
Conversation
@@ -50,7 +50,7 @@ var storageOperationMetric = metrics.NewHistogramVec( | |||
[]string{"volume_plugin", "operation_name", "status"}, | |||
) | |||
|
|||
var storageOperationStatusMetric = metrics.NewCounterVec( | |||
var StorageOperationStatusMetric = metrics.NewCounterVec( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not found any criterion to decide the package visibility of such metric variables. But this should be OK according to similar ones in kubelet and scheduler.
kubernetes/pkg/kubelet/metrics/metrics.go
Lines 86 to 94 in bff6452
NodeName = metrics.NewGaugeVec( | |
&metrics.GaugeOpts{ | |
Subsystem: KubeletSubsystem, | |
Name: NodeNameKey, | |
Help: "The node's name. The count is always 1.", | |
StabilityLevel: metrics.ALPHA, | |
}, | |
[]string{NodeLabelKey}, | |
) |
kubernetes/pkg/scheduler/metrics/metrics.go
Lines 98 to 107 in bff6452
PodSchedulingDuration = metrics.NewHistogramVec( | |
&metrics.HistogramOpts{ | |
Subsystem: SchedulerSubsystem, | |
Name: "pod_scheduling_duration_seconds", | |
Help: "E2e latency for a pod being scheduled which may include multiple scheduling attempts.", | |
// Start with 10ms with the last bucket being [~88m, Inf). | |
Buckets: metrics.ExponentialBuckets(0.01, 2, 20), | |
StabilityLevel: metrics.ALPHA, | |
}, | |
[]string{"attempts"}) |
/triage accepted |
/assign @RainbowMango |
9a18ade
to
13b8b4f
Compare
/retest |
/lgtm |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@gavinfish can you perhaps rebase the PR. I am sorry that it we did not review this, but I will take a look. |
13b8b4f
to
995e976
Compare
New changes are detected. LGTM label has been removed. |
@gnufied rebased. |
/approve for /hack owners. Others will have to review & lgtm. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gavinfish, lavalamp 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 |
@gavinfish: PR needs rebase. 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/test-infra repository. |
Is this PR still needed, please rebase if so (or we can close it?) |
This PR is older than 4 weeks and needs as rebase. Please rebase the PR against latest master and reopen if still needed. /close |
@dims: Closed this PR. In 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/test-infra repository. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
remove prometheus dependencies for volume
Which issue(s) this PR fixes:
Xref #89267
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: