Improve Prometheus and Grafana integration
Bug #1819573 reported by
Kevin W Monroe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes API Load Balancer |
Fix Released
|
Wishlist
|
Cory Johns |
Bug Description
Currently, conjure-up scrapes k8s metrics via prometheus with this:
This could use improvement:
1 - better auth (token or other service account vs admin creds)
2 - scrape via the kubeapi-lb instead of hitting endpoints directly
3 - create prometheus scrape job for k8s automatically via a relation
4 - create grafana dashboard for k8s automatically via a relation
#2 is the reason this bug is filed here. If we find everything we need via the kubeapi-lb proxy, we do not need to expose k8s-[master|worker] units.
Changed in charm-kubeapi-load-balancer: | |
milestone: | none → 1.16 |
summary: |
- better cdk metric scraping via prometheus + Improve Prometheus and Grafana integration |
description: | updated |
Changed in charm-kubeapi-load-balancer: | |
importance: | Low → Wishlist |
Changed in charm-kubeapi-load-balancer: | |
status: | In Progress → Fix Committed |
Changed in charm-kubeapi-load-balancer: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
See https:/ /github. com/juju- solutions/ bundle- canonical- kubernetes/ issues/ 687#issuecommen t-438202521 for context on when certain endpoints need to be exposed.