epic(prometheus): Always use Prometheus #85
Merged
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 of Changes
This branch is an epic branch for the "Always Use Prometheus" effort. It is safe to merge
It contains the following commits:
It contains the following approved pull requests:
NOTE: I went back and built
bindplane-prometheus
images for every release (v1.37.0 through current) to make sure anyone on older bindplane versions can still leverage the latest Prometheus options and expectations in this chart.Release Notes (will be included in this repos release, and bindplane's release notes)
As of Chart version
1.2.0
, Prometheus will be used as BindPlane's measurement backend. Prometheus is used to store historical throughput data gathered from your managed agents.Upgrade Procedure
Prometheus Not Previously Configured
If you do not have Prometheus configuration in your values file, no action is needed. Once upgraded, you will see
a new Prometheus StatefulSet in your BindPlane namespace.
Prometheus Side Car Configured
If you have
prometheus.enableSideCar
set, no action is needed. You can removeprometheus.enable
as this option has been removed.Self Managed Prometheus
If you have
prometheus.host
set, pointing to a self managed Prometheus instance, you must setprometheus.remote: true
in your values file. You can removeprometheus.enable
as this option has been removed.Please check that the PR fulfills these requirements