-
Notifications
You must be signed in to change notification settings - Fork 294
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
Create kube-state-metrics configuration for CRD metrics #2061
Comments
/help |
@sbueringer: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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. |
/assign @chrischdi |
/close fixed via #2345 |
@chrischdi: Closing this issue. 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. |
We recently created configuration to expose state metrics for core CAPI CRDs in core CAPI.
We should do the same in CAPV for CRDs for which it makes sense.
Then we should find a pragmatic way how we can use CAPI + CAPV state-metrics via core CAPI
tilt up
at the same time (currently kube-state-metrics only supports a single metrics configThe generated crd-config of core CAPI can be seen here: https://github.com/kubernetes-sigs/cluster-api/blob/main/hack/observability/kube-state-metrics/crd-config.yaml
The text was updated successfully, but these errors were encountered: