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

Set namespace of the example OperatorPipelines resource to oco #146

Open
itroyano opened this issue Jun 7, 2023 · 1 comment · May be fixed by #147
Open

Set namespace of the example OperatorPipelines resource to oco #146

itroyano opened this issue Jun 7, 2023 · 1 comment · May be fixed by #147
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@itroyano
Copy link
Contributor

itroyano commented Jun 7, 2023

Bug Description

Since the operator bundle is installed in "all namespaces" mode, OCO is running on the openshift-operators namespace.
If the user clicks create OperatorPipeline from here, the default namespace for this CR is openshift-operators too.
Form View UI doesn't allow changing that. only yaml view does.
It's easy to make the mistake here and proceed to create all tasks and pipelines in operators namespace, while the secrets and configs are in oco NS per documentation.

putting explicitly

namespace: oco

in the sample resource of CSV, should resolve this.

image
@itroyano itroyano added the kind/bug Categorizes issue or PR as related to a bug. label Jun 7, 2023
@itroyano
Copy link
Contributor Author

itroyano commented Jun 7, 2023

image

@itroyano itroyano linked a pull request Jun 7, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant