You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@f41gh7 Where is this configured? I've installed v0.21.0 from OperatorHub in OpenShift and the only option provided is "all namespaces" and the CSV looks like below. I'm not too sure how to use WATCH_NAMESPACE with an OLM install?
My goal is to deploy VM without users/tenants from other namespaces being able to access cluster level resources & metrics (e.g. by deploying their own VM instance, I am not sure if they are still restricted due to RBAC of the VM deployments in their namespace or the operator running globally from my namespace is going to allow them to do that kind of thing). Also if I use same namespace deploy is it still possible to scrape metrics from services in other namespaces?
Currently, when I try to install operator into the same namespace using operatorhub - I receive an error:
Question: can we update install modes if there is no any technical restriction for doing it?
Refs:
https://gist.github.com/afoninsky/213f36581e22656bb6c7cda5ccfa2e5e
https://operator-framework.github.io/olm-book/docs/operator-scoping.html#targetnamespaces-and-their-realationship-to-installmodes
The text was updated successfully, but these errors were encountered: