tree de459e5d0ee5ec7ee247b9b1252da644bcab374b
parent 30f9d03106e65ede9c54f84463999fc09700860e
author Sergiusz Bazanski <q3k@hackerspace.pl> 1591439706 +0200
committer Sergiusz Bazanski <q3k@hackerspace.pl> 1591451770 +0200

ops/metrics: basic cluster setup with prometheus

We handwavingly plan on implementing monitoring as a two-tier system:

 - a 'global' component that is reponsible for global aggregation,
   long-term storage and alerting.
 - multiple 'per-cluster' components, that collect metrics from
   Kubernetes clusters and export them to the global component.

In addition, several lower tiers (collected by per-cluster components)
might also be implemented in the future - for instance, specific to some
subprojects.

Here we start sketching out some basic jsonnet structure (currently all
in a single file, with little parametrization) and a cluster-level
prometheus server that scrapes Kubernetes Node and cAdvisor metrics.

This review is mostly to get this commited as early as possible, and to
make sure that the little existing Prometheus scrape configuration is
sane.

Change-Id: If37ac3b1243b8b6f464d65fee6d53080c36f992c