Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

epic(prometheus): Always use Prometheus #85

Merged
merged 4 commits into from
Feb 27, 2024
Merged

Conversation

jsirianni
Copy link
Member

@jsirianni jsirianni commented Feb 15, 2024

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:

  • Bump chart version to 1.2.0: d4e45cd
  • Run CI against all PRs: 154eadc

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 remove prometheus.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 set prometheus.remote: true in your values file. You can remove prometheus.enable as this option has been removed.

Please check that the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • CI passes

@jsirianni jsirianni changed the title feat(prometheus): Always use Prometheus epic(prometheus): Always use Prometheus Feb 15, 2024
@jsirianni jsirianni force-pushed the epic/always-on-prometheus branch from e8c0a7c to a1f3583 Compare February 15, 2024 21:20
@jsirianni jsirianni changed the base branch from main to bindplane-sts-volume-reclaim February 15, 2024 21:20
Base automatically changed from bindplane-sts-volume-reclaim to main February 19, 2024 15:23
@jsirianni jsirianni force-pushed the epic/always-on-prometheus branch from 4c2d516 to cf61465 Compare February 19, 2024 15:46
* use bindplane prometheus image and remove configmap

* remove args, they are set in the container image already. updaste volume mount to use /prometheus, the correct path for the bindplane-prometheus image

* pin sidecar test version
@jsirianni jsirianni force-pushed the epic/always-on-prometheus branch from b78b381 to d1ca4f9 Compare February 26, 2024 17:55
* remove sidecar

* rename dev prometheus config

* add prometheus statefulset

* true up securityContext

* add remote option

* regen docs

* remove prom enable from templates

* use generated service name when host is not set

* fix svc name

* re-add sideCar option

* revert size change

* use localhost when sidecar

* Regen docs

* resolve test issues by using newer image

* use ee image

* Remove all test case as it requires a license

* skip if dev prometheus is enabled

* fix condition

* add fsgroup for gke
@jsirianni jsirianni marked this pull request as ready for review February 26, 2024 20:15
@jsirianni jsirianni requested a review from a team as a code owner February 26, 2024 20:15
@jsirianni jsirianni requested review from BinaryFissionGames, shazlehu and dpaasman00 and removed request for shazlehu February 26, 2024 20:15
@jsirianni jsirianni merged commit 0425b88 into main Feb 27, 2024
10 checks passed
@jsirianni jsirianni deleted the epic/always-on-prometheus branch February 27, 2024 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants