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
This issue is about collecting inputs we have for choosing target namespace for DWO.
The target namespace we're going to use is openshift-operators. It should be target namespace for DWO, WTO, Che, CRW. The main cause - we don't have enough time to adapt openshift console and WTO to be suitable for any namespace.
In addition:
since all of the are all-namespaces scoped, UI will support only openshift-operators. If another namespace is needed: OperatorGroup should be precreated in the target namespace, and then it's needed to apply Subscription in that namespace. UI does not work well there;
it's difficult to find a good common namespace for all of them;
we need openshift- prefixed namespace if we would like to benefit from openshift monitoring.
P.S. CheCluster CR can be created anywhere as it's used to be.
Drawbacks:
operator maintainers won't be able to get permissions only to their Operator related objects, like install plan;
openshift-operators namespace does not have a proper label that can be used for NetworkPolicy, we can reuse scc: anyuid and operators will get network access to user's namespaces;
The text was updated successfully, but these errors were encountered:
This issue is about collecting inputs we have for choosing target namespace for DWO.
The target namespace we're going to use is openshift-operators. It should be target namespace for DWO, WTO, Che, CRW. The main cause - we don't have enough time to adapt openshift console and WTO to be suitable for any namespace.
In addition:
P.S. CheCluster CR can be created anywhere as it's used to be.
Drawbacks:
scc: anyuid
and operators will get network access to user's namespaces;The text was updated successfully, but these errors were encountered: