Bump prometheus to 2.0.0, prometheus-operator to 0.15.0, alertmanager to 0.12.0 and node-exporter to 0.15.1, grafana to 4.6.3
migrate prometheus alerts to yaml notation

Fix cluster:container_cpu_usage:ratio rule

kube-prometheus: Add Prometheus 2.0 rules

NAMESPACE feature in scripts implies it works. warnning ensures
that users are aware that its use requires further changes.

Alleviates #765

Per issue 593, append .yml to each filename used in the generated con…

Signed-off-by: Xabier Larrakoetxea <slok69@gmail.com>

Per issue 593, append .yml to each filename used in the generated configmap. I wasn't able to see alerts in the Prometheus UI until I did this

* Documentation: Added kubeadm documentation #618

This getting started guide covers a simple deployment of kube-prometheus
and assumes you have deployed using kubeadm.

Hopefully this helps clears up #618

* Moved documentation to appropriate folder, updated links.

* Minor documentation editing

Fixed referneces to Alertmanager.
Slightly stronger wording on changing grafana user/pass

Update rules

After cloning the repo I wanted to deploy kube-prometheus into my running minikube. I did the steps mentioned in the docu which brought me to the following exception:

namespace "monitoring" created
error: the path "manifests/prometheus-operator" does not exist
Waiting for Operator to register custom resource definitions.................................................................................................................^C

Fixing #751 K8SApiServerLatency always triggering

Metrics servers

* Generated by `make generate` in `contrib/kube-prometheus`

* If any of the rules is active > 10m
* If all daemonsets are not ready
* If all daemonsets are not scheduled
* If some are miss scheduled

kube-prometheus: add stateful sets dashboard

Convert Grafana dashboards to grafanalib scripts

Omit static compute resource requests and limits from deployment