-
Notifications
You must be signed in to change notification settings - Fork 418
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
✨ metrics: add generator for kube-state-metrics customresource configuration #1043
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: chrischdi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
9e798ce
to
3b209a2
Compare
@@ -0,0 +1,122 @@ | |||
/* |
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.
If wanted, I can volunteer to maintain this part of controller-gen (and/or also help on other parts of controller-tools) :-)
9b0a996
to
f7862f4
Compare
f7862f4
to
28f149a
Compare
…tion and a clusterrole
28f149a
to
8fe2d86
Compare
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-sigs/prow repository. |
We'll get back to this eventually, just low bandwith at the moment |
This adds a generator to generate a customresource configuration file for kube-state-metrics from markers.
With that configuration it is possible to get metrics for CRs like kube-state-metrics exposes for core resources.
(xref)
Example usage:
controller-gen metrics output:metrics:stdout \ paths=./api/...\ > crd-config.yaml
Introduced markers:
Example usage: kubernetes-sigs/cluster-api#9347