search

kubernetes / kube-state-metrics

Add-on agent to generate and expose cluster-level metrics.
https://kubernetes.io/docs/concepts/cluster-administration/kube-state-metrics/
Apache License 2.0
5.2k stars 1.92k forks source link

K-S-M job stops when all (*) Label and annotations are allowed #2399

Open Sohamdg081992 opened 1 month ago

Sohamdg081992 commented 1 month ago

What happened: K-S-M job stops working when all Label and annotations are allowed when we upgraded ksm from 2.9.2 to 2.12.0. This below setting is used. --metric-labels-allowlist=asterix=[asterix] --metric-annotations-allowlist=asterix=[asterix]

What you expected to happen: The job should continue working and labels and annotations should flow. They are working in ksm version 2.9.2 with same label and annotation settings.

How to reproduce it (as minimally and precisely as possible):

# An example: https://github.com/kubernetes/kube-state-metrics/issues/2223#issuecomment-1792850276
minikube start
...
go run main.go --custom-resource-state-only --custom-resource-state-config-file ksm-2223/custom-resource-config-file.yaml --kubeconfig ~/.kube/config

Anything else we need to know?:

Environment:

k8s-ci-robot commented 1 month ago

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.