-
Notifications
You must be signed in to change notification settings - Fork 303
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
victoria-metrics-k8s-stack: optional allowCrossNamespaceImport in GrafanaDashboard(s) #788
victoria-metrics-k8s-stack: optional allowCrossNamespaceImport in GrafanaDashboard(s) #788
Conversation
…fanaDashboard CRs for Grafana Operator
Thanks for the pull request! |
@Haleygo I see. So the GrafanaDashboard resource template embedded in the python script is rendered with the same "values.yaml" as the dashboard templates in the Helm chart? I can just add the same modifications using same references to .Values dictionary? Out of curiosity, when is this script called? |
…fanaDashboard CRs for Grafana Operator - also add to sync_grafana_dashboards.py
So, here it is, @Haleygo ... I think I understand it now. The python script is used from the top Makefile to generate various Helm template files in the Helm charts from source JSON files located on various other repositories. So for example, if some other source is introduced, its Helm template can be generated by the script. I ran the following command from top dir:
I just had to change the Makefile temporarily since I'm using podman in place of docker and podman, by default, runs rootles containers so:
|
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.
LGTM!
Thanks for contribution!
In victoria-metrics-k8s-stack Helm Chart, when values define
grafanaOperatorDashboardsFormat.enabled=true
, specialGrafanaDashboard
CRs get rendered that provide dashboards to Grafana Operator (https://grafana-operator.github.io/grafana-operator/). But those CRs don't get imported into Grafana instance when the Grafana Operator is not deployed to the same k8s namespace as the victoria-metrics-k8s-stack chart is, sinceGrafanaDashboard
CRs are created in this namespace.The provided patch allows overriding an additional boolean attribute in the chart values:
grafanaOperatorDashboardsFormat.allowCrossNamespaceImport
which is false by default. When set to true, the createdGrafanaDashboard
CRs will also contain this attribute and Grafana Operator will import them from a namespace that is different than the Grafana Operator's namespace.