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.

Sign up for GitHub

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

Jump to bottom

As the admin, I would like to have a possibility to install operator in the fixed namespace (with the fixed set of labels) #1597

Closed
ibuziuk opened this issue Jun 24, 2020 · 4 comments
Closed

As the admin, I would like to have a possibility to install operator in the fixed namespace (with the fixed set of labels) #1597

ibuziuk opened this issue Jun 24, 2020 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@ibuziuk
Copy link

ibuziuk commented Jun 24, 2020 •
edited
Loading

Feature Request

Currently, OLM supports two installation modes - all namespaces & a specific namespace:

image

As the admin, I would like to have a possibility to install operator in the fixed namespace (with the fixed set of labels)

image

At this point in time in order to achieve this behavior, one should use the 'All namespaces' strategy and handle the installation on the operator end (pre-create namespace and labels) which looks wrong by design. A particular example of the 'fixed namespace' requirement in the real project - eclipse-che/che#17187
@ibuziuk ibuziuk changed the title As an admin, I would like to have a possibility to install operator to the fixed namespace (with the fixed set of labels) As the admin, I would like to have a possibility to install operator to the fixed namespace (with the fixed set of labels) Jun 24, 2020
@ibuziuk ibuziuk changed the title As the admin, I would like to have a possibility to install operator to the fixed namespace (with the fixed set of labels) As the admin, I would like to have a possibility to install operator in the fixed namespace (with the fixed set of labels) Jun 24, 2020
@exdx exdx added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 24, 2020
@stale
Copy link

stale bot commented Aug 23, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 23, 2020
@openshift-ci-robot openshift-ci-robot added triage/unresolved Indicates an issue that can not or will not be resolved. and removed wontfix labels Aug 24, 2020
@stale
Copy link

stale bot commented Oct 23, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Oct 23, 2020
@stale
Copy link

stale bot commented Dec 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 22, 2020
@dinhxuanvu
Copy link
Member

You can use MultipleNamespace mode. Please take a look at this doc: https://olm.operatorframework.io/docs/concepts/crds/operatorgroup/#target-namespace-selection

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ibuziuk @dinhxuanvu @openshift-ci-robot @exdx