ScrapeClass relabelings/metricRelabelings are added after target-specific relabelings

[fabiobaiao]

According to the prometheus-operator's ScrapeClass api reference, its relabelings and metricRelabelings are added before the target specific relabelings: https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.ScrapeClass

The VictoriaMetrics operator does it the other way around. I suppose this is where it happens:

operator/internal/controller/operator/factory/vmscrapes/vmscrapes.go

Lines 653 to 654 in 87b2d36

	ers.RelabelConfigs = append(ers.RelabelConfigs, scrapeClass.RelabelConfigs...)
	ers.MetricRelabelConfigs = append(ers.MetricRelabelConfigs, scrapeClass.MetricRelabelConfigs...)

[AndrewChubatiuk]

fix will be available in upcoming 0.69.0 and 0.68.4
order of per job and scrape class relabelling rules was changed, but default relabelling configs are still added first