DRAFT: Add jsonnet lib for Perses Operator and Perses community dashboards
Description
Addresses https://github.com/prometheus-operator/kube-prometheus/issues/2654.
This PR introduces Perses Operator into kube-prometheus, including a Perses object, and community PersesDashboards. Uses jsonnet libs from https://github.com/perses/perses-operator/pull/140 and https://github.com/perses/community-dashboards/pull/87 (pending merge, right now pulling from my fork).
Some open questions,
- Should this be an addon?
- Probably needs some sane way with default Grafana install, and optional one line change to get Perses?
cc: @simonpasquier @nexucis @nicolastakashi
Some todos, and testing pending! :)
Type of change
What type of changes does your code introduce to the kube-prometheus? Put an x in the box that apply.
- [ ]
CHANGE(fix or feature that would cause existing functionality to not work as expected) - [X]
FEATURE(non-breaking change which adds functionality) - [ ]
BUGFIX(non-breaking change which fixes an issue) - [X]
ENHANCEMENT(non-breaking change which improves existing functionality) - [ ]
NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)
Changelog entry
Add Perses Operator to kube-prometheus
Some of the failures are due to breaking changes on perses-operator, will fix!
Sorry for the delay on this, will try to complete this now, was waiting for the latest Perses operator+Perses releases to make CRDs consistent + allow for some formatting