4 Commits

Author SHA1 Message Date
Max Leonard Inden
310f471cf6 contrib/kube: Add rbac role to discover prometheus
The current example-app setup in the kube-prometheus project is able to
discover scraping targets in the default namespace. It is not able to
discover the configured Alertmanager in the monitoring namespace.

This patch adds an alertmanager-discovery rbac role, to permit the
above described action. In addition it does the following cleanups:

- Remove kubeconfig configuration in deploy and teardown script. kubectl
chooses .kube/config whenever KUBECONFIG is not set by default

- Remove namespace specification option via NAMESPACE env var. In most
of the manifests the metadata/namespace was hardcoded anyways, in
addition in the promtheus frontend role binding the service account
namespace is hardcoded to default as well.

- Instead of `kubectl {apply,delete}` individual manifests, the deploy
and teardown shell scripts {apply,delete} on the entire folder.
2018-03-19 17:13:33 +01:00
Francisco Ripoli
5d33cbb166 example service monitoring updated with missing config
added service account, role and role binding for the prometheus frontend
example, also updated prometheus to use the correct service account

fixes #1049
2018-03-08 17:36:05 +00:00
Tapani Moilanen
6a12f669f7 Use kubectl apply in custom service example deploy
https://github.com/kubernetes/kubernetes/issues/29542 has been fixed,
use apply instead of create to create third party resources in custom service
monitoring example.
2017-05-03 20:02:22 +03:00
Frederic Branczyk
89ed6773e7 Add 'contrib/kube-prometheus/' from commit '81c0d2f4d30f63a4e274c2870c5afc89241827b0'
git-subtree-dir: contrib/kube-prometheus
git-subtree-mainline: 050ca21276696c8603375c699513ec487301ed62
git-subtree-split: 81c0d2f4d30f63a4e274c2870c5afc89241827b0
2017-03-06 09:55:36 +01:00