Add relabelings stanza for ServiceMonitor

[xadcoh]

Is your feature request related to a problem?/Why is this needed
I'd like to enrich metrics with additional labels

/feature

Describe the solution you'd like in detail
In Helm Chart in metrics.yaml modify endpoints:

spec:
  ...
  endpoints:
    - targetPort: 3301
      path: /metrics
      interval: 15s
      {{- if .Values.controller.serviceMonitor.extraRelabelings }}
      relabelings:
      {{- toYaml .Values.controller.serviceMonitor.extraRelabelings | nindent 6 }}
      {{- end }}

Describe alternatives you've considered
None

Additional context
None

[r2ronoha]

This would be great. We are currently having to either patch or override the ServiceMonitor in our infrastructure to be able to add relablings that we need

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[AndrewSirenko]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[r2ronoha]

/remove-lifecycle rotten