-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat: add support for metricRelabelings #5124
Conversation
|
Welcome @omerlh! |
/easycla |
|
charts/cluster-autoscaler/Chart.yaml
Outdated
@@ -11,4 +11,4 @@ name: cluster-autoscaler | |||
sources: | |||
- https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler | |||
type: application | |||
version: 9.20.0 | |||
version: 9.20.1 |
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.
This is a new feature, please make this a minor version bump.
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.
fixed
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.
Couple of changes required.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gjtempleton, omerlh 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 |
feat: add support for metricRelabelings
Which component this PR applies to?
Helm chart for cluster autoscaler
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add support for metricRelabelings in the service monitor in the helm chart, so we could drop metrics we don't care about - to reduce costs
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: