Use ClusterIP for our monitoring services so we can still access them…

… using kubectl proxy (knative#7867)

* Revert "Remove NodePort exposure from Grafana, Prometheus and Kibana (knative#7640)"

This reverts commit 6ec7f43.

* use clusterIP to expose monitoring services

config/monitoring/metrics/prometheus/100-grafana.yaml

@@ -118,6 +118,22 @@ data:
       options:
         path: /grafana-dashboard-definition/scaling
 ---
+apiVersion: v1
+kind: Service
+metadata:
+  name: grafana
+  namespace: knative-monitoring
+  labels:
+    app: grafana
+    serving.knative.dev/release: devel
+spec:
+  ports:
+  - port: 30802
+    protocol: TCP
+    targetPort: 3000
+  selector:
+    app: grafana
+---
 apiVersion: apps/v1
 kind: Deployment
 metadata:

config/monitoring/metrics/prometheus/300-prometheus.yaml

@@ -219,6 +219,20 @@ subjects:
   name: prometheus-system
   namespace: knative-monitoring
 ---
+apiVersion: v1
+kind: Service
+metadata:
+  name: prometheus-system-np
+  namespace: knative-monitoring
+  labels:
+    serving.knative.dev/release: devel
+spec:
+  selector:
+    app: prometheus
+  ports:
+    - port: 8080
+      targetPort: 9090
+---
 apiVersion: apps/v1
 kind: StatefulSet
 metadata:

third_party/config/monitoring/logging/elasticsearch/kibana.yaml

@@ -1,3 +1,20 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: kibana-logging
+  namespace: knative-monitoring
+  labels:
+    app: kibana-logging
+    kubernetes.io/cluster-service: "true"
+    kubernetes.io/name: "Kibana"
+spec:
+  selector:
+    app: kibana-logging
+  ports:
+  - port: 5601
+    protocol: TCP
+    targetPort: ui
+---
 apiVersion: apps/v1
 kind: Deployment
 metadata: