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

# Allow Prometheus to discover service endpoints
apiVersion: v1
kind: Service
metadata:
  name: kube-scheduler
  namespace: kube-system
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    k8s-app: kube-scheduler
  ports:
    - name: metrics
      protocol: TCP
      port: 10259
      targetPort: 10259
Update Prometheus discovery of kube components * Kubernetes v1.22.0 disabled kube-controller-manager insecure port, which was used internally for Prometheus metrics scraping * Configure Prometheus to discover and scrape endpoints for kube-scheduler and kube-controller-manager via the authenticated https ports, via bearer token * Change firewall ports to allow Prometheus (on worker nodes) to scrape kube-scheduler and kube-controller-manager targets that run on controller(s) with hostNetwork * Disable the insecure port on kube-scheduler 2021-08-11 06:08:49 +02:00			`# Allow Prometheus to discover 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`
			`spec:`
			`type: ClusterIP`
			`clusterIP: None`
			`selector:`
			`k8s-app: kube-scheduler`
			`ports:`
			`- name: metrics`
			`protocol: TCP`
Update Prometheus discovery of kube components * Kubernetes v1.22.0 disabled kube-controller-manager insecure port, which was used internally for Prometheus metrics scraping * Configure Prometheus to discover and scrape endpoints for kube-scheduler and kube-controller-manager via the authenticated https ports, via bearer token * Change firewall ports to allow Prometheus (on worker nodes) to scrape kube-scheduler and kube-controller-manager targets that run on controller(s) with hostNetwork * Disable the insecure port on kube-scheduler 2021-08-11 06:08:49 +02:00			`port: 10259`
			`targetPort: 10259`