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
Is your feature request related to a problem? Please describe.
On version 0.3.0, Nexus Operator is a namespaced operator, meaning that it needs to be installed on every namespace in a cluster or in the same namespace where the Nexus CR is deployed. We would leverage from the new SDK upgrade if Nexus Operator could be installed in one namespace, let's say operators and would watch every namespace for Nexus CRs.
Besides the new SDK format we could also create SCCs automatically on OpenShift, since it's a cluster scope resource (see #51).
Describe the solution you'd like
The operator to be installed in one single namespace and watch all namespaces in a given cluster.
Describe alternatives you've considered
Right now the operands must coexist in the same namespace as the operator.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
On version 0.3.0, Nexus Operator is a namespaced operator, meaning that it needs to be installed on every namespace in a cluster or in the same namespace where the Nexus CR is deployed. We would leverage from the new SDK upgrade if Nexus Operator could be installed in one namespace, let's say
operators
and would watch every namespace for Nexus CRs.Besides the new SDK format we could also create SCCs automatically on OpenShift, since it's a cluster scope resource (see #51).
Describe the solution you'd like
The operator to be installed in one single namespace and watch all namespaces in a given cluster.
Describe alternatives you've considered
Right now the operands must coexist in the same namespace as the operator.
The text was updated successfully, but these errors were encountered: