From 97017dbdec09435e01d95d54dc5109dcaac5731f Mon Sep 17 00:00:00 2001
From: Akos Eros <aeros@redhat.com>
Date: Thu, 16 Apr 2026 15:02:25 +0200
Subject: [PATCH] fix: Pin down servicemesh3 operator version

If we do not pin this down, the version skew eventually break the isto.
The istio resource's version, that is created in the servicemesh chart
is tied together with the operator version
---
 values-global.yaml | 1 +
 values-hub.yaml    | 6 ++++++
 2 files changed, 7 insertions(+)

diff --git a/values-global.yaml b/values-global.yaml
index c464fb01..401ecd57 100644
--- a/values-global.yaml
+++ b/values-global.yaml
@@ -6,6 +6,7 @@ global:
     useCSV: false
     syncPolicy: Automatic
     installPlanApproval: Automatic
+    autoApproveManualInstallPlans: true
 
 main:
   clusterGroupName: hub
diff --git a/values-hub.yaml b/values-hub.yaml
index 39d5b22a..b5d1ba9e 100644
--- a/values-hub.yaml
+++ b/values-hub.yaml
@@ -43,6 +43,9 @@ clusterGroup:
   subscriptions:
     servicemesh:
       name: servicemeshoperator3
+      channel: stable-3.2
+      csv: servicemeshoperator3.v3.2.3
+      installPlanApproval: Manual
     servicemesh-console:
       name: kiali-ossm
     distributed-tracing:
@@ -100,6 +103,9 @@ clusterGroup:
       project: servicemesh
       chart: servicemesh
       chartVersion: 0.1.*
+      overrides:
+        - name: servicemesh.version
+          value: v1.24.3
     temposttack:
       name: tempostack
       namespace: tempo