small changes in k8s/minikube and example-app (#392)

* namespace has to be kube-system

In order for this service to be discovered by ServiceMonitor k8s-apps-http, it should belong to namespace kube-system.

* namespace has to be kube-system

* namespace has to be kube-system

for service discovery to work within prometheus configuration (ServiceMonitor k8s-app) these service and endpoints should belong to kube-system namespace. Otherwise the service monitor won't fetch it.

* selector was incorrect

selector prometheus: prometheus-frontend is incorrect, the name of the Prometheus resource in the example is "frontend", not "prometheus-frontend"

manifests/examples/example-app/prometheus-frontend-svc.yaml

@@ -11,4 +11,4 @@ spec:
     protocol: TCP
     targetPort: web
   selector:
-    prometheus: prometheus-frontend
+    prometheus: frontend

manifests/k8s/minikube/kube-controller-manager.yaml

 apiVersion: v1
 kind: Service
 metadata:
+  namespace: kube-system
   name: kube-controller-manager-prometheus-discovery
   labels:
     k8s-app: kube-controller-manager
@@ -16,6 +17,7 @@ spec:
 apiVersion: v1
 kind: Endpoints
 metadata:
+  namespace: kube-system
   name: kube-controller-manager-prometheus-discovery
   labels:
     k8s-app: kube-controller-manager

manifests/k8s/minikube/kube-scheduler.yaml

 apiVersion: v1
 kind: Service
 metadata:
+  namespace: kube-system
   name: kube-scheduler-prometheus-discovery
   labels:
     k8s-app: kube-scheduler
@@ -16,6 +17,7 @@ spec:
 apiVersion: v1
 kind: Endpoints
 metadata:
+  namespace: kube-system
   name: kube-scheduler-prometheus-discovery
   labels:
     k8s-app: kube-scheduler