-
Notifications
You must be signed in to change notification settings - Fork 85
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Description
OpenShift version
4.10
Problem description
Pelorus insance on 4.10.60 , Pelorus operator version 0.0.8
Pelorus instance on 4.12.29, Pelorus operator version 0.0.7
Since both Pelorus have shared S3 in the backend as the this link mentioned , metrics from both instance will be stored in S3. and the both grafana should display all of the datas.
Steps to reproduce
- install Pelous on OCP1 and configure S3
- install Pelous on OCP2 and configure with the same S3 bucket
- create deployment on both instance
Configure file
Archive.zip
Current behavior
each grafana can display it's own instance metrics and does not display the other's metrics stored in S3
Expected behavior
each grafana can display all the metrics from S3
Code of Conduct
- I agree to follow Pelorus's Code of Conduct
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.