2.4 KiB
kube-prometheus
This repository collects Kubernetes manifests, dashboards, and alerting rules combined with documentationa and scripts to deploy them to get full cluster monitoring setup working.
Prerequisites
First, you need a running Kubernetes cluster. If you don't have one, follow the instructions of bootkube or minikube.
etcd is an important component of a working Kubernetes cluster, but it's deployed outside of it. The monitoring setup below assumes that it is made visible from within the cluster through a headless Kubernetes service. An example for bootkube's multi-vagrant setup is here.
Monitoring Kubernetes
The manifests used here use the Prometheus controller, which manages Prometheus servers and their configuration in your cluster. To install the controller, the node_exporter, Grafana including default dashboards, and the Prometheus server, run:
export KUBECONFIG=<path> # defaults to "~/.kube/config"
export KUBE_NAMESPACE=<ns> # defaults to "default"
hack/cluster-monitoring/deploy
After all pods are ready, you can reach:
- Prometheus UI on node port
30900 - Grafana on node port
30902
To tear it all down again, run:
hack/cluster-monitoring/teardown
All services in the manifest still contain the prometheus.io/scrape = true annotations. It is not
used by the Prometheus controller. They remain for convential deployments as in
this example configuration.
Monitoring custom services
The example manifests in /manifests/examples/example-app
deploy a fake service into the production and development namespaces and define
a Prometheus server monitoring them.
kubectl --kubeconfig="$KUBECONFIG" create namespace production
kubectl --kubeconfig="$KUBECONFIG" create namespace development
hack/example-service-monitoring/deploy
After all pods are ready you can reach the Prometheus server monitoring your services
on node port 30100.
Teardown:
hack/example-service-monitoring/teardown