Skip to content

Service monitor fails when enabled in Helm chart #10303

@larsskj

Description

@larsskj

What happened?

I have just migrated a dashboard install from the old manifest to a Helm setup.

I decided to enable the service monitor mentioned under the extras settings. It works in the respect that the service monitor is created, however, it doesn't work as it doesn't resolve to an endpoint Prometheus can scrape.

The problem is the /spec/endpoints/0/port settings: No matter what I do the port is hardcoded to https. But none of the services created by the Helm chart has an endpoint of this name - hence Prometheus fails scraping the target.

The proper value appears to be api rather than https, but I couldn't find a way to override this wrong default. Doing it by hand - or in my case: Using a postRenderer from FluxCD - makes the setup work.

What did you expect to happen?

I expected a setup that worked by default.

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

Try installing the latest Helm chart - currently 7.13.0 - and enable the service monitor. Check that the port points to an existing port.

Anything else we need to know?

No response

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.13.0

Kubernetes version

1.32.3

Dev environment

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions