Skip to content
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

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

Open
Sohamdg081992 opened this issue May 24, 2024 · 1 comment
Open
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Sohamdg081992
Copy link

Sohamdg081992 commented May 24, 2024

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:

  • kube-state-metrics version: 2.12.0
  • Kubernetes version (use kubectl version): 1.27.9
  • Cloud provider or hardware configuration: Azure
  • Other info:
@Sohamdg081992 Sohamdg081992 added the kind/bug Categorizes issue or PR as related to a bug. label May 24, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 24, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants