Bug 1926182

Summary:	[RFE] Support disabling reconciliation of monitoring related resources using a dedicated reconcile strategy flag
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Ohad <omitrani>
Component:	ocs-operator	Assignee:	Jose A. Rivera <jarrpa>
Status:	CLOSED ERRATA	QA Contact:	Elad <ebenahar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.7	CC:	ebenahar, ekuric, etamir, madam, muagarwa, ocs-bugs, owasserm, puebele, sostapov
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	OCS 4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.7.0-307.ci	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1926274 (view as bug list)		Environment:
Last Closed:	2021-05-19 09:19:00 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:
Bug Depends On:
Bug Blocks:	1926274

Description Ohad 2021-02-08 12:22:09 UTC

Description of problem (please be detailed as possible and provide log
snippests):

In order to support metrics collection and alerts OCS deploys a nubmer of monitoring resources, including but not limited to, ServiceMonitors, PodMontiors, and PrometheusRules

These resources trigger scraping and other monitoring tasks on the monitoring stack deployed in the openshift-monitoring namespace.

On openshift dedicated clusters OCS should not use the clusters monitoring stack and it seems that the current proposed solution (not final) direct us to provide all monitoring resource as a separate bundle to be deployed by a 3rd party agent. 

As such we need the ability to specify that we would like OCS to not deploy or reconcile all monitoring related resources. OCS already has a mechanism that allows it to disable reconcile for specific parts of the product, reconcileStrategy flags, so we could extend this mechanism to also control the reconciliation of monitoring resources by introducing such a flag.


Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, I cannot deploy OCS on openshift-dedicated clausters


Is there any workaround available to the best of your knowledge?
No 


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


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 3 Jose A. Rivera 2021-02-08 14:52:06 UTC

Giving devel_ack+. This should be relatively simple to implement. Since this is only for OpenShift Dedicated his does not require explicit QE testing, it is sufficient to simply verify the normal regression testing is not affected.

Comment 4 Elad 2021-02-08 20:29:08 UTC

For QE - verification to be based on regression testing results of monitoring

Comment 6 Mudit Agarwal 2021-03-16 15:39:10 UTC

Required for Openshift dedicated.

Comment 8 Elad 2021-03-25 22:55:42 UTC

Moving to VERIFIED based on regression testing using v4.7.0-318.ci

Comment 10 errata-xmlrpc 2021-05-19 09:19:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2041