Latter versions of the operator seem to have an issue where when they create the HPA, it gets deleted again by the operator instantly, atleast for the vminsert and vmselect HPA's defined in a VMCluster. I can see the HPA's that the operator creates by using "kubectl watch" to catch the HPA before it gets deleted, and the spec is as expected. I have confirmed via the k8s auditlog that it is indeed the operator itself deleting the HPA and not some other component interfering.
I've gone back to version victoria-metrics-k8s-stack-0.62.2 (operator version 0.64.1 I believe), and here the HPA's are created and remain in place as expected.
Latter versions of the operator seem to have an issue where when they create the HPA, it gets deleted again by the operator instantly, atleast for the vminsert and vmselect HPA's defined in a VMCluster. I can see the HPA's that the operator creates by using "kubectl watch" to catch the HPA before it gets deleted, and the spec is as expected. I have confirmed via the k8s auditlog that it is indeed the operator itself deleting the HPA and not some other component interfering.
I've gone back to version victoria-metrics-k8s-stack-0.62.2 (operator version 0.64.1 I believe), and here the HPA's are created and remain in place as expected.