This primarily just updates the grafana chart version, but doing so adds some new features and a README has been added to give a quick run down of how to use them. This turns the grafana dashboard into a stateless application loading the datasources and dashboards on each startup. This is to try and make the dashboard easier to use in GitOps.
There is probably some more work that can be done to this chart to make things a little easier further.
For example the datasources and dashboards can be loaded via configmap completely as opposed to be defined in the values file (the config for each), and loaded through the various sides cars. Also I think we might be able to remove the nginx from the side car completely and run nginx alongside grafana in a separate pod. Right now you must know how the release name will be constructed in the value files to correctly mount the nginx configmap into the grafana container. Knowing the release name is a bit tricky with fluxcd.
This also strips the internal routing. This isn't really required any longer because everything that was done through logging into the dashboard is now done automatically. However, there are some details about how to port-forward and get access to the username/password. This removes an extra bit of secret juggling that was previously a value in the chart.
ognots
commented
1 year ago
This primarily just updates the grafana chart version, but doing so adds some new features and a README has been added to give a quick run down of how to use them. This turns the grafana dashboard into a stateless application loading the datasources and dashboards on each startup. This is to try and make the dashboard easier to use in GitOps.
There is probably some more work that can be done to this chart to make things a little easier further.
For example the datasources and dashboards can be loaded via configmap completely as opposed to be defined in the values file (the config for each), and loaded through the various sides cars. Also I think we might be able to remove the nginx from the side car completely and run nginx alongside grafana in a separate pod. Right now you must know how the release name will be constructed in the value files to correctly mount the nginx configmap into the grafana container. Knowing the release name is a bit tricky with fluxcd.
This also strips the
internalrouting. This isn't really required any longer because everything that was done through logging into the dashboard is now done automatically. However, there are some details about how to port-forward and get access to the username/password. This removes an extra bit of secret juggling that was previously a value in the chart.