review: Don't add ServiceMonitors in values.yaml, we already have them

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

docs/howtos/telemetry/30-metrics-qs.md

@@ -31,36 +31,7 @@ that allows us to define Prometheus' Targets intuitively.
 There are many ways to install and set up Prometheus. For ease of deployment, we will use the
 Prometheus community Helm chart.
 
-Let's create a `kube-prometheus-stack-values.yaml` file with the
-following contents:
-
-```yaml
----
-prometheus:
-  additionalServiceMonitors:
-    - name: kubewarden
-      selector:
-        matchLabels:
-          app: kubewarden-policy-server-default
-      namespaceSelector:
-        matchNames:
-          - kubewarden
-      endpoints:
-        - port: metrics
-          interval: 10s
-    - name: kubewarden-controller
-      selector:
-        matchLabels:
-          app.kubernetes.io/name: kubewarden-controller
-      namespaceSelector:
-        matchNames:
-          - kubewarden
-      endpoints:
-        - port: metrics
-          interval: 10s
-```
-
-Now, let's install the Prometheus stack Helm Chart:
+Let's install the Prometheus stack Helm Chart:
 
 :::note
 At time of writing the latest chart version is `51.5.3`
@@ -252,4 +223,3 @@ variable to match the name of the desired policy.
 You should be able to see the dashboard similar to this:
 
 ![Dashboard](/img/grafana_dashboard.png)
-