DRAFT: Add jsonnet lib for Perses Operator and Perses community dashboards #2657
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Saswata Mukherjee <[email protected]>
|
Some of the failures are due to breaking changes on perses-operator, will fix! |
Signed-off-by: Saswata Mukherjee <[email protected]>
|
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Addresses #2654.
This PR introduces Perses Operator into kube-prometheus, including a Perses object, and community PersesDashboards.
Uses jsonnet libs from perses/perses-operator#140 and perses/community-dashboards#87 (pending merge, right now pulling from my fork).
Some open questions,
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
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)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