Bug 1894158

Summary: [RFE] OCS operator should use cluster monitoring by default
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Matthias Muench <mmuench>
Component: management-consoleAssignee: Bipul Adhikari <badhikar>
Status: CLOSED DUPLICATE QA Contact: Elad <ebenahar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.5CC: assingh, jefbrown, madam, mbukatov, mmuench, nthomas, ocs-bugs
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-10 11:01:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthias Muench 2020-11-03 16:51:50 UTC
Description of problem (please be detailed as possible and provide log
snippests):
During the installation of OpenShift Container Storage operator, the user is required to manually select "Enable operator recommended cluster monitoring on this namespace". Since this is required to get proper representation of the information for OCS and MCG on the Overview (dashboard), this should be selected by default. However, there are no obvious reasons to not enable the cluster monitoring, since the dashboard would not display proper information from the OCS cluster nor would the link of the MCG console be displayed. 
In documentation instead, it could be covered as an optional step to deselect this if desired for whatever reason.

Version of all relevant components (if applicable):
OCS 4.5.1


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No


Is there any workaround available to the best of your knowledge?
Follow the documentation step by step exactly. 


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1



Can this issue reproducible?
yes


Can this issue reproduce from the UI?
yes


If this is a regression, please provide more details to justify this:
no regression, only possible pitfall and this could be avoided.


Steps to Reproduce:
1. 
2.
3.


Actual results:
The installation of the OCS operator requires manually selecting the cluster monitoring although it's recommended.


Expected results:
The installation of the OCS operator should have the cluster monitoring enabled by default and optional a deselection is (perhaps) offered.



Additional info:

Comment 2 Sébastien Han 2020-11-04 14:22:10 UTC
Moving to console since this is where the decision is taking place.