Allow tenant specification in jsonnet ScaledObjects

CHANGELOG.md

@@ -270,6 +270,7 @@
 
 ### Jsonnet
 
+* [CHANGE] Allow tenant configuration in ScaledObject spec for metric queries. #13750
 * [CHANGE] Removed etcd-operator from the Jsonnet configuration. Users can still use etcd as a KV store for rings, but need to deploy and manage etcd themselves rather than via the operator. #13049
 * [CHANGE] Distributor: Reduce calculated `GOMAXPROCS` to be closer to the requested number of CPUs. #12150
 * [CHANGE] Query-scheduler: The query-scheduler is now a required component that is always used by queriers and query-frontends. #12187

operations/mimir/autoscaling.libsonnet

@@ -1,6 +1,7 @@
 {
   _config+:: {
     autoscaling_prometheus_url: 'http://prometheus.default:9090/prometheus',
+    autoscaling_prometheus_tenant: '',
 
     // If true, compute the scaling metric using irate(), otherwise, use rate()
     autoscaling_cpu_hpa_use_irate: false,
@@ -125,6 +126,7 @@
           type: 'prometheus',
           metadata: {
             serverAddress: $._config.autoscaling_prometheus_url,
+            [if $._config.autoscaling_prometheus_tenant != '' then 'customHeaders']: 'X-Scope-OrgID=%s' % $._config.autoscaling_prometheus_tenant,
             query: trigger.query,
 
             // The metric name uniquely identifies a metric in the KEDA metrics server.