Ship Grafana dashboards with the chart #1035
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Question
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Help wanted
Status
In progress
Status
Need More Info
Status
Needs feedback
No milestone
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
forgejo-helm/forgejo-helm#1035
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I would like to be able to enable dashboards in the Helm chart and get a
ConfigMapwith the Forgejo dashboards from the forgejo/contrib/gitea-monitoring-mixin, similar to how other Helm charts ship dashboards (ie Kyverno).I belive with focus on the grafanaOperator we should support both:
my suggestion is to render the json beside the helm templates and use
.Files.Getto put in in ConfigMap and/or GrafanaDashboard.I'm not sure if this is in scope of this chart or if it should be another new chart like the runner chart which is coming soon.
@pat-s opinions?
A separate chart would surely be cleaner.
I wouldn't add it as a sub-chart anyhow, if at all then as an optional
configMapand a distinct values section.However, users might prefer to update these resources independently from Forgejo itself, and this would be much easier with a dedicated chart.