[bitnami/kube-prometheus] kube-prometheus kubelet.serviceMonitor.relabelings not applying the target_label key into prometheus config about charts HOT 7 CLOSED

$ helm template kube-prometheus oci://registry-1.docker.io/bitnamicharts/kube-prometheus -f custom-values.yaml -s templates/exporters/kubelet/servicemonitor.yaml
Pulled: registry-1.docker.io/bitnamicharts/kube-prometheus:9.2.1
Digest: sha256:61e0fcee27d9f84a7beb25b33d459eef104ef2e806c180cc7e5b3aad3f610cd4
---
# Source: kube-prometheus/templates/exporters/kubelet/servicemonitor.yaml
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: kube-prometheus-kubelet
  namespace: "default"
  labels:
    app.kubernetes.io/instance: kube-prometheus
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: kube-prometheus
    app.kubernetes.io/version: 0.74.0
    helm.sh/chart: kube-prometheus-9.2.1
    app.kubernetes.io/component: kubelet
spec:
  jobLabel: k8s-app
  selector:
    matchLabels:
      k8s-app: kubelet
  namespaceSelector:
    matchNames:
      - kube-system
  endpoints:
    - port: https-metrics
      scheme: https
      tlsConfig:
        caFile: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
        serverName: kubernetes
        insecureSkipVerify: true
      bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
      honorLabels: true
      relabelings:
        - action: replace
          replacement: ${labelCluster}
          target_label: cluster
    - port: https-metrics
      scheme: https
      path: /metrics/cadvisor
      honorLabels: true
      tlsConfig:
        caFile: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
        serverName: kubernetes
        insecureSkipVerify: true
      bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token