Alexander Greene

This PR has been open for over a year and seems stale. I am going to close this PR for now, but if the suggested features are still desired, please...

@anik120 could you point to the specific test you were writing when you encountered the issue that encouraged you to open this ticket? It may be nice to use it...

In order to support different architectures in our release builds, OLM is fed information from the environment when choosing which image to use in the unpacker pod, something seems to...

Hello @lagivan, it seems as though there has been some drift in the documentation and the code, as shown in [this search](https://github.com/operator-framework/operator-lifecycle-manager/search?q=catalogNamespaceEnvVarName), the environment variable you've set is never used....

Good morning @chenzhiwei, Thank you for using OLM and submitting this issue. The OLM team views the installation of an operator as a highly privileged workflow that modifies the control...

In the OLM Dev WG meeting, @njhale brought up that it is possible to specify a ServiceAccount's RBAC to install an Operator, preventing privilege escalation beyond the scope of the...

Do you think it's worth removing the two merge commits we've added @timflannagan?

Hello @terenceq, thanks for submitting this issue and for using OLM. >For some reason, installplan status field is showing a replaces field pointing to the same CSV name, causing it...

Pushed a rebase. /lgtm /unhold

After thinking about this a bit more, I'm not sure that we want to grant all users the ability to view existing `operators` as it could bleed information between tenants,...