cilium / hubble-ui

Observability & Troubleshooting for Kubernetes Services

Home Page:https://www.cilium.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Hubble UI does not pick service name correctly

coleenquadros opened this issue · comments

Hi, I am running thanos and prometheus on a kind cluster using the helm chart as described here -> https://github.com/bitnami/charts/tree/main/bitnami/thanos#integrate-thanos-with-prometheus-and-alertmanager
In the hubble UI, how is the naming of the service picked up in the UI? There are different components for thanos like ruler, query, storegateway but all are marked as thanos.

https://github.com/bitnami/charts/blob/9c3dfb522ac8b14c5325c2f4077d171d3d0c84aa/bitnami/thanos/templates/query/service.yaml#L11
there is a service name defined

Screenshot 2023-11-16 at 11 45 26

I have the same problem, I will like to be able to split them visually.

From testing I see that the name is taken from the label app.kubernetes.io/name on the pod.

Although that value is not configurable in some helm charts.

Is there a way to choose which label is to be used for the name displayed in the UI?

Could you guys please post all the labels for those services?

@yandzee I have these labels:

  labels:
    app.kubernetes.io/component: receive
    app.kubernetes.io/name: thanos
    app.kubernetes.io/part-of: hashring

only difference on each service is the component label