- Nov 21, 2017
-
-
stroebitzer authored
-
- Nov 17, 2017
-
-
stroebitzer authored
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
-
- Nov 16, 2017
-
-
Frederic Branczyk authored
Fixing #751 K8SApiServerLatency always triggering
-
- Nov 15, 2017
-
-
Frederic Branczyk authored
Metrics servers
-
- Nov 14, 2017
-
-
Cesarini, Daniele authored
-
Cesarini, Daniele authored
-
Aleksandar Topuzovic authored
* Generated by `make generate` in `contrib/kube-prometheus`
-
Aleksandar Topuzovic authored
* 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
-
- Nov 13, 2017
-
-
Frederic Branczyk authored
kube-prometheus: add stateful sets dashboard
-
Frederic Branczyk authored
-
Frederic Branczyk authored
-
- Nov 10, 2017
-
-
Arve Knudsen authored
-
Arve Knudsen authored
-
- Nov 09, 2017
-
-
Konstantinos Natsakis authored
-
Konstantinos Natsakis authored
-
Harry Lee authored
-
- Nov 08, 2017
-
-
Frederic Branczyk authored
-
- Nov 07, 2017
-
-
Konstantinos Natsakis authored
-
- Nov 01, 2017
-
-
Frederic Branczyk authored
Convert Grafana dashboards to grafanalib scripts
-
Frederic Branczyk authored
-
Frederic Branczyk authored
Omit static compute resource requests and limits from deployment
-
- Oct 31, 2017
-
-
Daniel Fenton authored
The AWS CLI SG commands are not necessary, kops creates an SG with these ports open to the correct SG by default
-
- Oct 30, 2017
-
-
Arve Knudsen authored
-
Svend Sorensen authored
Do not specify static resource settings in the kubernetes-deployment to avoid unnecessary replacement of pods when the manifest is reapplied (`kubectl apply`). The addon-resizer will dynamically set the pod compute resource values. If the values are also set statically in the deployment configuration, reapplying the configuration will result in the pods getting replaced. Without the static resource, the deployment configuration can be reapplied, and the pods will not be replaced. This change was also made in the upstream kube-state-metrics example manifests. https://github.com/kubernetes/kube-state-metrics/pull/285
-
- Oct 25, 2017
-
-
xuchenhao001 authored
-
- Oct 22, 2017
-
-
Eduardo Gonzalez authored
-
- Oct 19, 2017
-
-
Frederic Branczyk authored
-
- Oct 17, 2017
-
-
Frederic Branczyk authored
-
Frederic Branczyk authored
-
- Oct 16, 2017
-
-
Frederic Branczyk authored
-
Frederic Branczyk authored
Fix merging of -datasource.json files
-
- Oct 13, 2017
-
-
Valdis Rigdon authored
The merge was missing a new line at the end of the merge, so only the first datasource was being put into the ConfigMap.
-
- Oct 11, 2017
-
-
jordanjennings authored
In the generated version of this file at /contrib/kube-prometheus/manifests/grafana/grafana-deployment.yaml the version was bumped to 4.5.2 but seems it was overlooked in this templated version of the file.
-
- Oct 06, 2017
-
-
Frederic Branczyk authored
kube-prometheus: various version updates
-
Frederic Branczyk authored
-
Alexander Brandstedt authored
-
- Sep 29, 2017
-
-
Giancarlo Rubio authored
-
- Sep 26, 2017
-
-
Frederic Branczyk authored
-
- Sep 22, 2017
-
-
Frederic Branczyk authored
cut 0.13.0 & promote project to beta
-
Giap Tran authored
-