SYS-652 Grafana helm chart, with prometheus and alertmanager#203
Merged
instantlinux merged 2 commits intomainfrom May 21, 2025
Merged
SYS-652 Grafana helm chart, with prometheus and alertmanager#203instantlinux merged 2 commits intomainfrom
instantlinux merged 2 commits intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary of Changes
A straightforward helm chart to deploy grafana, with prometheus and alertmanager. Grafana with prometheus is a huge, poorly-documented beast, and most published helm charts for it are hugely complex. This one makes no attempt to handle complexity, and most pointedly it will NOT use operators or CRDs: it will create a running grafana instance, with prometheus and a few basic alerts. Updates to future versions will be no-brainer version-bumps, without the need for manual steps like all the other charts that I've run into.
This also adds
kube-state-metricsand removesmetrics-serverwhich I haven't used in years.Why is this change being made?
I want to see node metrics (RAM, disk space, network traffic) on the k8s cluster and its NAS storage servers, and I don't want headaches every time an update comes out. That's it.
How was this tested? How can the reviewer verify your testing?
Local testing.
Completion checklist