-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
False
-
False
-
Undefined
-
-
-
-
1. Proposed title of this feature request
Hide the ElasticSearch Operator from users that should not be able to use it.
2. What is the nature and description of the request?
Customer is having trouble with users who are asking a lot of questions and even tries to deploy the ElasticSearch operator. As the ElasticSearch operator is only meant to be used with cluster logging and jaeger they think it is bad design to make it visible to every user in the cluster.
3. Why does the customer need this? (List the business requirements here)
Users are asking a lot of questions and/or tries to deploy EO and fail. In turn that also adds to the support burden of the operations team.
Also even the first OCP 4 onboarded developers team managed to try to deploy a ElasticSearch Operator that failed and generated a lot of confusion.
4. List any affected packages or components.
OLM, Console or just ElasticSearch Operator. It is unclear to me were is the best fit
- is related to
-
OPRUN-2366 Discrete operator tenant visibility control for global operators
- Closed
-
OCPSTRAT-879 [PRD scope] OLM 1.0 - Installed Extension Discoverability and Access Management (F12)
- New
- relates to
-
RFE-1278 prevent non-admins from seeing all operator in a namespace
- Accepted