Remove kubelet ServiceMonitor about fury-kubernetes-service-mesh

[angelbarrera92]

I think that fury-kubernetes-monitoring kubelet ServiceMonitor needs some improving as also kube-prometheus is doing the same.

Uhmmm i see.

So, i will add this task to my todo list. Thanks @lnovara

[lnovara]

I think it's better to include this patch during the fury-kubernetes-monitoring upgrade.

[angelbarrera92]

Hi Luca. You're right.

I see the kubelet ServiceMonitor inside the istio offering relabels some metrics:

relabelings:
    - sourceLabels: [job]
      action: replace
      replacement: kubernetes-cadvisor
      targetLabel: job
    metricRelabelings:
    - action: drop
      regex: container_(network_tcp_usage_total|network_udp_usage_total|tasks_state|cpu_load_average_10s)
      sourceLabels:
      - __name__

What should we do with this code block? Merge it into the fury-kubernetes-monitoring kubelet ServiceMonitor?

[lnovara]

I think that fury-kubernetes-monitoring kubelet ServiceMonitor needs some improving as also kube-prometheus is doing the same.

[angelbarrera92]

I think that fury-kubernetes-monitoring kubelet ServiceMonitor needs some improving as also kube-prometheus is doing the same.

I found the commit adding that part: prometheus-operator/kube-prometheus@e4991fe

I can apply this git patch. But... i think it's going to be better to fully upgrade the package. What do you think?

EDIT: https://github.com/sighupio/fury-kubernetes-monitoring/compare/feature/git-patch-kube-prometheus-regenerate?expand=1

[angelbarrera92]

I think it's better to include this patch during the fury-kubernetes-monitoring upgrade.

Totally agree!