bootkube starts two replicas of the scheduler and controllers manager

correctly discover the Alertmanager cluster and ServiceMonitors

use prometheus-operator v0.1.0

v0.1.0 introduced handling Alertmanager clusters.

Fixed docker image tag for "quay.io/prometheus/node-exporter". 

The tag did not exist for "prometheus/node-exporter". So I have changed it to a valid value of "v0.13.0"

Update manifests to latest version of Prometheus Operator

The ports reflect the upstream kube-dns manifests of bootkube and
kubernetes/kubernetes.

The latest version of the Prometheus Operator requires Prometheus
>=v1.4.0 for the Alertmanger discovery feature.

These annotations made sense in pre v1.3.0 Prometheus releases, however,
with >=v1.3.0 and the Prometheus Operator these annotations are more
confusing then helpful.

Spleling

Fix broken kubernetes.rules

Fix always firing alerts

Scrape Prometheus service itself

This replaces the cluster overview dashboards with new dashboards
for a cluster-wide overview and inspecting single nodes.

Extract prometheus.yaml into assets

It's a lot easier to show and explain the Prometheus config if available
in the standard yaml format. The Kubernetes ConfigMap specs can always
be auto-generated.

add explanation and guide on prerequisites

add etcd2 alerts

monitor and alert on k8s components