From 342870fa033e0531f25bb48498690ef840e5e879 Mon Sep 17 00:00:00 2001
From: Martin McCaffery <martin.mccaffery@think-ahead.tech>
Date: Tue, 2 Jun 2026 09:30:24 +0100
Subject: [PATCH] fix(vm-client): add cluster external label for dashboard
 variable resolution

---
 .../stacks/observability-client/vm-client-stack/values.yaml | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/otc/observability.buildth.ing/stacks/observability-client/vm-client-stack/values.yaml b/otc/observability.buildth.ing/stacks/observability-client/vm-client-stack/values.yaml
index 7bd29da..723d36c 100644
--- a/otc/observability.buildth.ing/stacks/observability-client/vm-client-stack/values.yaml
+++ b/otc/observability.buildth.ing/stacks/observability-client/vm-client-stack/values.yaml
@@ -791,11 +791,9 @@ vmagent:
     port: "8429"
     selectAllByDefault: true
     scrapeInterval: 20s
-    externalLabels: 
+    externalLabels:
       cluster_environment: "observability"
-      # For multi-cluster setups it is useful to use "cluster" label to identify the metrics source.
-      # For example:
-      # cluster: cluster-name
+      cluster: observability
     extraArgs:
       promscrape.streamParse: "true"
       # Do not store original labels in vmagent's memory by default. This reduces the amount of memory used by vmagent