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

Service monitor checks wrong port name #9968

Open
rataja opened this issue Feb 14, 2025 · 0 comments
Open

Service monitor checks wrong port name #9968

rataja opened this issue Feb 14, 2025 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@rataja
Copy link

rataja commented Feb 14, 2025

What happened?

Kubernetes dashboard 7.10.4

Servicemonitor by default checks port name https and cannot be changed via values.yaml

Port name https by default belongs to service kubernetes-dashboard-metrics-scraper which doesnt return any metrics and that is problem for prometheus.

Test commands for returned values from each service

curl -I   kubernetes-dashboard-api:8000/metrics
curl -I   kubernetes-dashboard-auth:8000/metrics
curl -I   kubernetes-dashboard-kong-proxy:80/metrics
curl -I   kubernetes-dashboard-metrics-scraper:8000/metrics
curl -I   kubernetes-dashboard-web:8000/metrics

What did you expect to happen?

Servicemonitor port to be scraped should be configurable or by default should be either name: kong-proxy or name: auth

In this case it will return metrics and prometheus will be "happy"

How can we reproduce it (as minimally and precisely as possible)?

1st step
Install helm chart with values.yaml edited

  serviceMonitor:
    # Whether to create a Prometheus Operator service monitor.
    enabled: true

2nd step:
Prometheus application -> Target health
Result: Error scraping target: strconv.ParseFloat: parsing "/metrics": invalid syntax while parsing: "URL: /metrics"

Anything else we need to know?

No response

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.10.4

Kubernetes version

1.31.4

Dev environment

No response

@rataja rataja added the kind/bug Categorizes issue or PR as related to a bug. label Feb 14, 2025
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.
Projects
None yet
Development

No branches or pull requests

1 participant