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.

Sign up for GitHub

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

add prometheus service monitor migration to UPGRADE.md #1042

Merged
merged 1 commit into from
Mar 7, 2022
Merged

add prometheus service monitor migration to UPGRADE.md #1042

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions UPGRADE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,12 @@ tenant has a specific MinIO Image specified in `.spec.log.image` you need to upd
minio/operator image or your private registry image.


v4.3.9 - v4.4.0
---
Support for Prometheus ServiceMonitor is removed. Using ServiceMonitor to configure prometheus endpoints will lead to duplicate metrics. The alternate approach is to use Prometheus [AdditionalScrapeConfigs] https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/additional-scrape-config.md. This can be enabled by setting `prometheusOperator: true` on the tenant.
Once this is configured, MinIO Operator will create the additional configuration for the tenant.
If the prometheus is running on a particular namespace, `PROMETHEUS_NAMESPACE` can be set accordingly.

v4.2.3 - v4.2.4
---
In this version we started running the MinIO pods as `non-root` to increase security in the MinIO deployment, however
Expand Down Expand Up @@ -40,3 +46,4 @@ This scenario is automatically handled by the operator, however if the tenant is
a yaml file) which is missing the added `securityContext` this problem may arise again, so update your stored yamls
respectively.