Hui Wang

@PawlikMateusz Do you see any error messages when doing helm upgrade, or did you edit the secret by hand before, those could also lead to incomplete helm upgrade. In this...

I think you should add them under https://github.com/VictoriaMetrics/helm-charts/blob/659a1d6d4eb35f5dbdd8c539c376cdbcbc60b1c9/charts/victoria-metrics-alert/values.yaml#L267-L268 There will be a [generated configmap](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-alert/templates/server-alerts-configmap.yaml) in the end

Hello all! It will be a problem when you already have k8s chart installed under one namespace, and reinstalled under other namespace. Because helm will add key "meta.helm.sh/release-name" and "meta.helm.sh/release-namespace"...

Hello, can you elaborate what url is this? Seems like it's generated by alertmanager.

> Can we use `--set-file` with this implementation? Hello! I think using `-promscrape.config` to file mounted by configmap should work, no? https://github.com/VictoriaMetrics/VictoriaMetrics/blob/70773f53d75fc7f0589f464381c37826ed1b0912/README.md?plain=1#L2407

Closed as completed)

@micw Hello, have you try [vmauth](https://docs.victoriametrics.com/vmauth.html)?

@sachinm24 Hello, looks like it's caused by crd upgrade, some field breaking change maybe. I'd suggest using the latest one and check changelog in [operator](https://github.com/VictoriaMetrics/operator) to see if upgrade can...

close this as completed.

> @Haleygo @Amper should we adopt this patch? I'm not sure we should do this patch now, since we already changed our [compatibility versions](https://github.com/VictoriaMetrics/helm-charts#kubernetes-compatibility-versions) claim from `1.13 to 1.22` to...