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: charts/victoria-metrics-distributed/_index.md.gotmpl
+58Lines changed: 58 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,64 @@ First, performing update on availability zone `zone-eu-1`:
132
132
133
133
Then, perform update on availability zone `zone-us-1` with the same steps1~4.
134
134
135
+
### Upgrade to 0.24.0
136
+
137
+
Starting this release first item of `*.vmauth.spec.unauthorizedUserAccessSpec.url_map` is no longer merged with default backend configuration.
138
+
Custom settings for default backend should now be defined using `defaultUrlMapItem.<accessType>.<backendType>`:
139
+
140
+
For global read VMAuth:
141
+
142
+
```
143
+
read:
144
+
global:
145
+
vmauth:
146
+
spec:
147
+
unauthorizedUserAccessSpec:
148
+
url_map:
149
+
- load_balancing_policy: first_available
150
+
retry_status_codes: [500, 502, 503]
151
+
```
152
+
is now
153
+
```
154
+
defaultUrlMapItem:
155
+
read:
156
+
vmsingle: # if you're using VMSingle
157
+
load_balancing_policy: first_available
158
+
retry_status_codes: [500, 502, 503]
159
+
vmcluster: # if you're using VMCluster
160
+
load_balancing_policy: first_available
161
+
retry_status_codes: [500, 502, 503]
162
+
```
163
+
164
+
For global write VMAuth:
165
+
166
+
```
167
+
write:
168
+
global:
169
+
vmauth:
170
+
spec:
171
+
unauthorizedUserAccessSpec:
172
+
url_map:
173
+
- load_balancing_policy: first_available
174
+
retry_status_codes: [500, 502, 503]
175
+
```
176
+
is now
177
+
```
178
+
defaultUrlMapItem:
179
+
write:
180
+
vmagent: # if you have VMAgents queue enabled
181
+
load_balancing_policy: first_available
182
+
retry_status_codes: [500, 502, 503]
183
+
vmsingle: # if you're using VMSingle without VMAgents enabled
184
+
load_balancing_policy: first_available
185
+
retry_status_codes: [500, 502, 503]
186
+
vmcluster: # if you're using VMCluster without VMAgents enabled
187
+
load_balancing_policy: first_available
188
+
retry_status_codes: [500, 502, 503]
189
+
```
190
+
191
+
Same is for per zone VMAuth proxy `zoneTpl.read.vmauth`.
192
+
135
193
### Upgrade to 0.13.0
136
194
137
195
Introduction of VMCluster's [`requestsLoadBalancer`](https://docs.victoriametrics.com/operator/resources/vmcluster/#requests-load-balancing) allowed to simplify distributed chart setup by removing VMAuth CRs for read and write load balancing. Some parameters are not needed anymore:
You can use `{{ include "vm.url" $ctx }}/select/<accountID>/prometheus/<suffix>` as datasource of vmalert or grafana, check more supported APIs [here](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#url-format).
13
13
{{- end }}
14
+
{{ if (((.Values.mixed).global).vmauth).enabled }}
- `{{ include "vm.url" $ctx }}/select/<accountID>/prometheus/<suffix>` as datasource of vmalert or grafana, check more supported APIs [here](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#url-format).
19
+
- `{{ include "vm.url" $ctx }}/prometheus/api/v1/write` as write destination for your client like vmagent, check more supported APIs [here](https://docs.victoriametrics.com/victoriametrics/vmagent/#how-to-push-data-to-vmagent).
0 commit comments