-
Notifications
You must be signed in to change notification settings - Fork 2k
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
customresource GitRepo cannot be scraped #2051
Comments
This issue is currently awaiting triage. If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the The 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. |
This may not be related to kube-state-metrics but might be an issue in your CRD. |
I am using rancher fleet based on version 0.4.0 and 0.5.3.
|
It looks like client-go makes guesses at the plural kubernetes/client-go#1082 |
ok. Thanks. |
Can you try the following CRM: (it's the same with
|
Thanks, this work. |
What happened:
I try to get metrics for the following custom resources:
During the execution the kind "GitRepo" is replaced for the kube api call with "gitrepoes", for which the api call fails as this kind does not exists.
There is an "e" too much in gitrepoes.
Here the logs
and the scrape is empty.
with "Kind: gitrepos" I get
metrics scrape:
But this will never be updated as the watch runs into an error, which skips the processing of the result according to the source code.
What you expected to happen:
kind "GitRepo" is replace for the kube api call with "gitrepos"
kubectl work correctly for GitRepo:
How to reproduce it (as minimally and precisely as possible):
Install fleet helm chart in Kubernetes from https://github.com/rancher/fleet/tree/master/charts/fleet-crd
The kube-state-metrics pod uses a serviceaccount with cluster-admin role.
Here is the custom-resource-state-config setting to use.
Anything else we need to know?:
Environment:
kubectl version
): v1.24.8+rke2r1The text was updated successfully, but these errors were encountered: