You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use prometheusOperator option to add scrap configuration to a kube-prometheus placed on a custom namespace.
I set PROMETHEUS_NAMESPACE and PROMETHEUS_NAME in the operator yaml but the operator logs (during tenant creation) return:
E0907 08:34:06.480375 1 main-controller.go:676] error syncing 'minio-storage/minio-storage': More than 1 prometheus found on namespace monitoring. PROMETHEUS_NAME not specified.
Current Behavior
PROMETHEUS_NAMESPACE is correctly handle but PROMETHEUS_NAME seems to not.
Create a tenant with prometheusOperator: true in the corresponding values.yaml. Be sure to have a kube-prometheus operator deployed in the monitoring namesapce
Show logs kubectl logs service/operator -n minio-operator
Your Environment
Version used (minio-operator): 5.0.7
Environment name and version (e.g. kubernetes v1.17.2): v1.26.8
The text was updated successfully, but these errors were encountered:
Expected Behavior
I want to use
prometheusOperator
option to add scrap configuration to a kube-prometheus placed on a custom namespace.I set
PROMETHEUS_NAMESPACE
andPROMETHEUS_NAME
in the operator yaml but the operator logs (during tenant creation) return:E0907 08:34:06.480375 1 main-controller.go:676] error syncing 'minio-storage/minio-storage': More than 1 prometheus found on namespace monitoring. PROMETHEUS_NAME not specified.
Current Behavior
PROMETHEUS_NAMESPACE
is correctly handle butPROMETHEUS_NAME
seems to not.Steps to Reproduce (for bugs)
helm install --namespace minio-operator --create-namespace minio-operator minio/operator -f values.yaml
values.yaml
prometheusOperator: true
in the corresponding values.yaml. Be sure to have a kube-prometheus operator deployed in themonitoring
namesapcekubectl logs service/operator -n minio-operator
Your Environment
minio-operator
): 5.0.7The text was updated successfully, but these errors were encountered: