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

OpenShift operator: using multiple namespace arguments is not supported #3573

Open
alonsocamaro opened this issue Sep 25, 2024 · 2 comments
Open
Labels
awaiting response Awaiting response bug

Comments

@alonsocamaro
Copy link

alonsocamaro commented Sep 25, 2024

Setup Details

Orchestration: OSCP
Orchestration Version: 4.12
Operator Version: 3.18.0

Description

When specifying multiple namespace arguments, the syntax checker complains as shown in the next screenshot:

Screenshot 2024-09-25 at 09 29 26

Steps To Reproduce

  1. Fill a F5BigIpCtlr with more than one namespace
  2. Click create
@alonsocamaro alonsocamaro added bug untriaged no JIRA created labels Sep 25, 2024
@alonsocamaro
Copy link
Author

alonsocamaro commented Oct 17, 2024

In a 2 tier deployment/multi-cluster deployment, typically it is needed to specify the namespaces:

  • openshift-ingress
  • the namespace where CIS is installed, in order to reload the settings in case these change

That is even for simple scenarios, we need to be able to specify multiple namespaces in the Operator. Maybe customers will not like to use namespace-label in namespaces such as openshift-ingress?

@vklohiya
Copy link
Contributor

@alonsocamaro , please try using the namespaces as follows:

namespaces: ["foo", "bar"]

Note: Only single namespace is supported with the namespace parameter due to this limitation. We should improve the documentation for this use-case.

@trinaths trinaths added awaiting response Awaiting response and removed untriaged no JIRA created labels Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting response Awaiting response bug
Projects
None yet
Development

No branches or pull requests

3 participants