-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[helm] Support for Servicemonitor #1402
Conversation
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
@nlamirault Thanks for the PR! I'll let one of the maintainers that are more familiar with helm handle this one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First of all thanks for the PR.
We have metricsService https://github.com/grafana/grafana-operator/blob/master/deploy/helm/grafana-operator/values.yaml#L53-L57 since earlier. In retrospect I probably picked a rather bad name for that value. So it could potentially be good to use that.
At the same time we have metrics name hard coded
targetPort: metrics |
So lets skip that, but take a look at the comment and add namespace.
{{- end }} | ||
{{- with .Values.serviceMonitor.additionalLabels }} | ||
{{- toYaml . | nindent 4 }} | ||
{{- end }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Due to earlier PR we set namespace in all templates, so please add that to this one as well.
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
No description provided.