Service and ServiceMonitor target unused exporter port (8888)

[KJone1]

The operator's ServiceMonitor configuration targets two ports (ch-metrics:8888 and op-metrics:9999), but the operator pod only exposes port 9999 if exporter is disabled

ServiceMonitor:

spec:
  endpoints:
    - interval: 30s
      port: ch-metrics
    - interval: 30s
      port: op-metrics

same for the Service:

ports:
    - name: ch-metrics
      port: 8888
      protocol: TCP
      targetPort: 8888
    - name: op-metrics
      port: 9999
      protocol: TCP
      targetPort: 9999

Expected Behavior:
The ServiceMonitor should only target the actively used operator metrics port (9999)

also there are those 2 log line on operator startup:
log 1: start serving metrics at: :9999/metrics
log 2: 2025-09-29T13:05:50Z INFO controller-runtime.metrics Metrics server is starting to listen {"addr": ":8080"}

is there a reason 8080 is not scraped?

[Slach]

8888 is used for ClickHouse metrics, which are scraped by metrics-exporter from clickhouse-operator
9999 is used for Operator metrics, which are exported by clickhouse-operator itself

I don't see any 8080 port mentioned in the repo, only for zookeeper manifest for management console

[KJone1]

@Slach if exporter is disabled in the chart the service monitor still scrapes 8888 even tho there is no such target

[KJone1]

and i meant why are 2 ports for metrics server 9999 and 8080.

[KJone1]

@Slach i think it may come from here https://github.com/kubernetes-sigs/controller-runtime/blob/v0.15.1/pkg/metrics/listener.go#L44

[Slach]

@sunsingerus could you check listen on 8080 port from controller runtime?