Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is target namespace for DWO? #475

Closed
sleshchenko opened this issue Jul 1, 2021 · 0 comments
Closed

What is target namespace for DWO? #475

sleshchenko opened this issue Jul 1, 2021 · 0 comments
Assignees
Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Milestone

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Jul 1, 2021

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;
@sleshchenko sleshchenko self-assigned this Jul 1, 2021
@sleshchenko sleshchenko added the sprint/current Is assigned to issues which are planned to work on in the current team sprint label Jul 1, 2021
@sleshchenko sleshchenko added this to the v0.7.0 milestone Jul 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Projects
None yet
Development

No branches or pull requests

1 participant