rancher-charts

History

Julia Bier e59801f9a6 [dev-v2.10] rancher-monitoring support k8s 1.31 (#4450 )		2024-09-20 12:53:18 -04:00
..
templates	[dev-v2.10] Rebase monitoring (#4384 )	2024-09-04 14:40:18 -04:00
Chart.yaml.patch	[dev-v2.10] rancher-monitoring support k8s 1.31 (#4450 )	2024-09-20 12:53:18 -04:00
README.md.patch	[dev-v2.10] Rebase monitoring (#4384 )	2024-09-04 14:40:18 -04:00
values.yaml.patch	[dev-v2.10] rancher-monitoring 105.1.0-rc.3+up61.3.2 bump curl image (#4412 )	2024-09-10 12:37:02 -04:00

README.md.patch

--- charts-original/README.md
+++ charts/README.md
@@ -445,7 +445,6 @@
 data like usernames and passwords. Secrets are the more appropriate cluster resource to manage those.
 
 Example values to add a postgres datasource as a kubernetes secret:
-
 ```yaml
 apiVersion: v1
 kind: Secret
@@ -600,7 +599,6 @@
 and then create a configuration which deletes the alert rule.
 
 Example deletion configuration:
-
 ```yaml
 apiVersion: v1
 kind: ConfigMap
@@ -618,7 +616,6 @@
 ```
 
 ## Statically provision alerting resources
-
 If you don't need to change alerting resources (alert rules, contact points, notification policies and notification templates) regularly you could use the `alerting` config option instead of the sidecar option above.
 This will grab the alerting config and apply it statically at build time for the helm file.