public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-04 20:23:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

correcting capitalization: helm > Helm (#1018)

Browse Source
This commit is contained in:
Marty Hernandez Avedon
2023-12-06 16:17:31 -05:00
committed by GitHub
parent 3b8defdbb1
commit 437ab199da
75 changed files with 111 additions and 114 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/helm-chart-options.md
+3 -5
View File
@@ -49,13 +49,11 @@ An example of where this might be used is with Istio. For more information, see
## Configuring Applications Packaged within Monitoring v2
We deploy kube-state-metrics and node-exporter with monitoring v2. Node exporter are deployed as DaemonSets. In the monitoring v2 helm chart, in the values.yaml, each of the things are deployed as sub charts.
We deploy kube-state-metrics and node-exporter with monitoring v2. The node exporters are deployed as DaemonSets. Each of these entities are deployed as sub-charts through the monitoring v2 Helm chart, values.yaml.
We also deploy grafana which is not managed by prometheus.
We also deploy Grafana, which is not managed by Prometheus.
If you look at what the helm chart is doing like in kube-state-metrics, there are plenty more values that you can set that aren’t exposed in the top level chart.
But in the top level chart you can add values that override values that exist in the sub chart.
Many values aren’t exposed in the top level chart. However, you can add values to the top level chart to override values that exist in the sub-charts.
### Increase the Replicas of Alertmanager