-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
📖 Sync cluster-api-state-metrics proposal to match implementation state. #7183
📖 Sync cluster-api-state-metrics proposal to match implementation state. #7183
Conversation
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.
last nit from my side. otherwise lgtm pending squash
lgtm pending squash |
This also removes the `_labels` metric references. There are kube-state-metrics specific flags regarding these metric which won't affect custom resource configuration (allow/deny-list). Exposing all metrics would lead increase the cardinality without being worth it. Use-case specific configuration should be added by the user if required.
2474963
to
91ed330
Compare
/lgtm |
/lgtm it would be great if @tobiasgiese (co-author on this proposal) could take a quick look, otherwise, I will approve in a couple of days |
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.
/lgtm
/lgtm |
/approve |
[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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Syncs the cluster-api-state-metrics proposal to match implementation state.
Implementation was mostly done in #7095
This also removes the
_labels
metric references. There are kube-state-metrics specific flags regarding these metric which won't affect custom resource configuration (allow/deny-list). Exposing all metrics would lead increase the cardinality without being worth it. Use-case specific configuration should be added by the user if required.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #6458