fix: move ResourceMetricsPolicies out of services component

config/resources-metrics/kustomization.yaml

@@ -5,3 +5,9 @@ components:
   - iam/
   - identity/
   - resources-manager/
+  # ResourceMetricsPolicy resources for each service. These are owned exclusively
+  # by the milo-resource-metrics Kustomization and must not be included in any
+  # other path (e.g. crd/overlays/core-control-plane via the services component).
+  - ../services/iam/telemetry/metrics
+  - ../services/quota/telemetry/metrics
+  - ../services/resourcemanager/telemetry/metrics

config/services/iam/kustomization.yaml

@@ -1,5 +1,2 @@
 apiVersion: kustomize.config.k8s.io/v1alpha1
 kind: Component
-
-components:
-  - telemetry/metrics

config/services/kustomization.yaml

@@ -5,10 +5,13 @@ kind: Component
 # Add new service directories here as they are created.
 
 components:
-  - iam
-  - resourcemanager
   - quota
   # identity is intentionally excluded here — it contains ActivityPolicy resources
   # which require the activity.miloapis.com CRDs to be installed. Those CRDs are
   # provided by the activity service, which is not deployed in the milo test cluster.
   # Deploy config/services/identity/ separately once the activity service is present.
+  #
+  # iam and resourcemanager are intentionally excluded here — their only content was
+  # ResourceMetricsPolicy resources, which are now owned exclusively by the
+  # resources-metrics component. Including them here would create Flux ownership
+  # conflicts with the milo-resource-metrics Kustomization.

config/services/quota/kustomization.yaml

@@ -3,6 +3,5 @@ kind: Component
 
 components:
   - iam
-  - telemetry/metrics
   - registrations
   - claim-policies

config/services/resourcemanager/kustomization.yaml

@@ -1,5 +1,2 @@
 apiVersion: kustomize.config.k8s.io/v1alpha1
 kind: Component
-
-components:
-  - telemetry/metrics