Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[kube-prometheus-stack] Grafana crd datasources #5240
base: main
Are you sure you want to change the base?
[kube-prometheus-stack] Grafana crd datasources #5240
Changes from 7 commits
18aa477
1fe6a1d
bc4bf65
ea377b5
31ab216
272eaab
fb66609
2acb139
88c1641
2d425af
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This is a suggestion which can be considered as alternative. It's just an option to discuss about if possible and it's not indented as "please use this".
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.
@jkroepke the main problem here, that if we take your approach we loose the possibility to add comments, because any comments between dict keys break the formatting. At the beginning I implemented it in a way you suggested but later I realized that I cannot make nice conditionals with comments, so I switched to this version.
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.
@dzirg44 what the downside of just using plain templating instead put everything logic into the templating syntax?
I still feel not happy, it feel like an unnatural helm template.
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.
@jkroepke Can you take a look at the refactored version?
In essence I:
created 3 functions
kube-prometheus-stack.grafana.datasourceUrl.defaultPrometheus
kube-prometheus-stack.grafana.datasourceUrl.replica
kube-prometheus-stack.grafana.datasourceUrl.alertmanager
Converted urlDisplayLabel in exemplarTraceIdDestinations
used coalesce instead of default (can be reverted back) in some cases
timeout
- removed (i don't see this parameter in the values or in grafana prometheus datasource api)Some potential issues:
{{- $scrapeInterval := .Values.grafana.sidecar.datasources.defaultDatasourceScrapeInterval | default .Values.prometheus.prometheusSpec.scrapeInterval | default "30s" }}
would it be better to set scrapeInterval to 30s in values and remove default?
Check failure on line 1022 in charts/kube-prometheus-stack/values.yaml
Check failure on line 1028 in charts/kube-prometheus-stack/values.yaml