Changing the namespace for the pod monitors as gateway-namesapce is n…

…o longer created with istio being installed by sail

Signed-off-by: R-Lawton <[email protected]>

config/observability/kustomization.yaml

@@ -4,12 +4,8 @@ kind: Kustomization
 resources:
   - github.com/prometheus-operator/kube-prometheus?ref=release-0.13
   - github.com/Kuadrant/gateway-api-state-metrics/config/kuadrant?ref=0.5.0
-# To scrape istio metrics, 3 configurations are required:
-# 1. Envoy metrics directly from the istio ingress gateway pod
-  - prometheus/monitors/pod-monitor-envoy.yaml
-# 2. Istiod metrics via the istiod service
   - prometheus/monitors/service-monitor-istiod.yaml
-# 3. Istio metrics exposed via envoy on 15020 in each application.
+
 # We're using the additionalScrapeConfigs field of the Prometheus CR
 # here to read existing prometheus scrape annotations on pods.
 # Ideally this would be done via another PodMonitor or ServicMonitor,

config/observability/openshift/telemetry.yaml

@@ -2,7 +2,7 @@ apiVersion: telemetry.istio.io/v1alpha1
 kind: Telemetry
 metadata:
   name: namespace-metrics
-  namespace: gateway-system
+  namespace: istio-system
 spec:
   metrics:
   - providers:

config/observability/prometheus/monitors/service-monitor-istiod.yaml

@@ -2,10 +2,11 @@ apiVersion: monitoring.coreos.com/v1
 kind: ServiceMonitor
 metadata:
   name: istiod
+  namespace: istio-system
 spec:
   namespaceSelector:
     matchNames:
-    - gateway-system
+    - istio-system
   selector:
     matchLabels:
       app: istiod

config/observability/prometheus/telemetry.yaml

@@ -2,7 +2,7 @@ apiVersion: telemetry.istio.io/v1alpha1
 kind: Telemetry
 metadata:
   name: namespace-metrics
-  namespace: gateway-system
+  namespace: istio-system
 spec:
   metrics:
   - providers: