From 1f20b244c33b351f22c4886c57fa05a255adc7b5 Mon Sep 17 00:00:00 2001
From: scottwilliams <scottwilliams@ucsb.edu>
Date: Fri, 5 Sep 2025 09:36:44 -0700
Subject: [PATCH] Fix customization rule priority

Fleet only applies customizations to the first matching.  This update gives priority to making nginx providers work before applying servicemonitors.  Enabling servicemonitors depends on prometheus already being enabled and setup for it and it's very low priority.

Signed-off-by: scottwilliams <scottwilliams@ucsb.edu>
---
 operator/fleet.yaml | 38 +++++++++++++++++++-------------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/operator/fleet.yaml b/operator/fleet.yaml
index 3c888de..3f955d6 100644
--- a/operator/fleet.yaml
+++ b/operator/fleet.yaml
@@ -11,24 +11,6 @@ helm:
     crds: 
       enabled: true
 targetCustomizations:
-  - name: prod
-    helm:
-      values:
-        prometheus:
-          servicemonitor:
-            enabled: true
-    clusterSelector:
-      matchLabels:
-        env: prod
-  - name: rancher
-    helm:
-      values:
-        prometheus:
-          servicemonitor:
-            enabled: true
-    clusterSelector:
-      matchLabels:
-        env: rancher
   - name: gke
     helm:
       values:
@@ -51,4 +33,22 @@ targetCustomizations:
             ACMEHTTP01IngressPathTypeExact: false        
     clusterSelector:
       matchLabels:
-        provider.cattle.io: rke2
\ No newline at end of file
+        provider.cattle.io: rke2
+  - name: rancher
+    helm:
+      values:
+        prometheus:
+          servicemonitor:
+            enabled: true
+    clusterSelector:
+      matchLabels:
+        env: rancher
+  - name: prod
+    helm:
+      values:
+        prometheus:
+          servicemonitor:
+            enabled: true
+    clusterSelector:
+      matchLabels:
+        env: prod