I recently upgraded from v0.60.2 to v0.63.0 and the operator now seems to do something between minimum and no time downtime strategy when performing vmcluster changes.

It will update the vmstorage and vmselect STS in parallel. And then once the vmselect STS rollout is complete, it will update the vminsert deployment. This makes for a very noisy rollout and cluster availability that gets worse the larger the cluster is.

I much prefer the old behavior of doing the equivalent to No Downtime Strategy. We have tuned many aspects of the VictoriaMetrics components and k8s to have little or no interruptions when rollouts are performed in that manner.