typhoon/addons/prometheus/discovery/kube-scheduler.yaml

# Allow Prometheus to scrape service endpoints
apiVersion: v1
kind: Service
metadata:
  name: kube-scheduler
  namespace: kube-system
  annotations:
    prometheus.io/scrape: 'true'
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    k8s-app: kube-scheduler
  ports:
    - name: metrics
      protocol: TCP
      port: 10251
      targetPort: 10251
Enable kube-proxy metrics and allow Prometheus scrapes * Configure kube-proxy --metrics-bind-address=0.0.0.0 (default 127.0.0.1) to serve metrics on 0.0.0.0:10249 * Add firewall rules to allow Prometheus (resides on a worker) to scrape kube-proxy service endpoints on controllers or workers * Add a clusterIP: None service for kube-proxy endpoint discovery 2019-12-29 21:21:49 +01:00			`# Allow Prometheus to scrape service endpoints`
addons: Add better alerting rules to Prometheus manifests * Adapt the coreos/prometheus-operator alerting rules for Typhoon, https://github.com/coreos/prometheus-operator/tree/master/contrib/kube-prometheus/manifests * Add controller manager and scheduler shim services to let prometheus discover them via service endpoints * Fix several alert rules to use service endpoint discovery * A few rules still don't do much, but they default to green 2017-11-08 10:35:56 +01:00			`apiVersion: v1`
			`kind: Service`
			`metadata:`
			`name: kube-scheduler`
			`namespace: kube-system`
			`annotations:`
			`prometheus.io/scrape: 'true'`
			`spec:`
			`type: ClusterIP`
			`clusterIP: None`
			`selector:`
			`k8s-app: kube-scheduler`
			`ports:`
			`- name: metrics`
			`protocol: TCP`
			`port: 10251`
			`targetPort: 10251`