You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-2Lines changed: 22 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,11 +90,13 @@ Secure Grafana by configuring credentials:
90
90
```yaml
91
91
grafana:
92
92
credentials:
93
+
# Directly set these for quick setups
93
94
adminUser: "admin"
94
95
adminPassword: "<your-secure-password-here>"
96
+
97
+
# For production, use a Kubernetes secret to manage credentials securely
95
98
existingSecretName: "<your-secret-here>"
96
99
```
97
-
> **_NOTE:_** Consider using Kubernetes secrets for dynamic credential management.
98
100
99
101
#### Expose Grafana Externally
100
102
@@ -118,7 +120,25 @@ grafana:
118
120
enabled: true
119
121
storageClass: <your-custom-storage-class>
120
122
```
121
-
> **_NOTE:_** Use a custom storage class with a 'Retain' policy to secure data integrity.
123
+
> **_NOTE:_** Use a custom storage class with a 'Retain' policy to allow for data retention even after uninstalling the chart.
124
+
125
+
### 8. Modifying or Adding Grafana Dashboards
126
+
127
+
The default dashboards are located in the `dashboards` directory of the reference chart. To add new dashboards or modify existing ones, follow these steps.
128
+
129
+
Dashboards are provisioned directly from CRDs, which means any manual edits will be lost upon a refresh. As such, the workflow outlined below is recommended for making changes:
130
+
131
+
1. Create a copy of the dashboard by selecting **Edit** in the upper right corner, then **Save dashboard** -> **Save as copy**. After saving, navigate to the copy.
132
+
2. Make your edits to the copy and exit edit mode.
133
+
3. Select **Export** in the upper right corner and then **Export as JSON**. **Ensure that `Export the dashboard to use in another instance` is toggled on.**
134
+
4. Download the file and replace the `./dashboards/server-slis.json` file with the updated copy. Ensure to update the title and UID of the updated dashboard to match the original:
135
+
```json
136
+
{
137
+
"title": "Server SLIs",
138
+
"uid": "beg3u6ond4ydcb"
139
+
}
140
+
```
141
+
5. Commit the result and open a PR for the On-Prem team to review.
Copy file name to clipboardExpand all lines: README.md.gotmpl
+22-2Lines changed: 22 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -84,11 +84,13 @@ Secure Grafana by configuring credentials:
84
84
```yaml
85
85
grafana:
86
86
credentials:
87
+
# Directly set these for quick setups
87
88
adminUser: "admin"
88
89
adminPassword: "<your-secure-password-here>"
90
+
91
+
# For production, use a Kubernetes secret to manage credentials securely
89
92
existingSecretName: "<your-secret-here>"
90
93
```
91
-
> **_NOTE:_** Consider using Kubernetes secrets for dynamic credential management.
92
94
93
95
#### Expose Grafana Externally
94
96
@@ -112,7 +114,25 @@ grafana:
112
114
enabled: true
113
115
storageClass: <your-custom-storage-class>
114
116
```
115
-
> **_NOTE:_** Use a custom storage class with a 'Retain' policy to secure data integrity.
117
+
> **_NOTE:_** Use a custom storage class with a 'Retain' policy to allow for data retention even after uninstalling the chart.
118
+
119
+
### 8. Modifying or Adding Grafana Dashboards
120
+
121
+
The default dashboards are located in the `dashboards` directory of the reference chart. To add new dashboards or modify existing ones, follow these steps.
122
+
123
+
Dashboards are provisioned directly from CRDs, which means any manual edits will be lost upon a refresh. As such, the workflow outlined below is recommended for making changes:
124
+
125
+
1. Create a copy of the dashboard by selecting **Edit** in the upper right corner, then **Save dashboard** -> **Save as copy**. After saving, navigate to the copy.
126
+
2. Make your edits to the copy and exit edit mode.
127
+
3. Select **Export** in the upper right corner and then **Export as JSON**. **Ensure that `Export the dashboard to use in another instance` is toggled on.**
128
+
4. Download the file and replace the `./dashboards/server-slis.json` file with the updated copy. Ensure to update the title and UID of the updated dashboard to match the original:
129
+
```json
130
+
{
131
+
"title": "Server SLIs",
132
+
"uid": "beg3u6ond4ydcb"
133
+
}
134
+
```
135
+
5. Commit the result and open a PR for the On-Prem team to review.
0 commit comments