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

Add a --global install option #745

Closed
nicolaferraro opened this issue Jun 12, 2019 · 2 comments
Closed

Add a --global install option #745

nicolaferraro opened this issue Jun 12, 2019 · 2 comments
Assignees
Labels
area/core Core features of the integration platform good first issue Does not require full understanding of the codebase kind/feature New feature or request

Comments

@nicolaferraro
Copy link
Member

We have a "--skip-operator-setup" flag to install only the platform resource, but not a "--global" flag to install the operator in a fixed namespace (e.g. "camel-k") and configure it to watch all namespaces.

The setting is only supported on operatorhub for now.

@nicolaferraro nicolaferraro added area/core Core features of the integration platform kind/feature New feature or request good first issue Does not require full understanding of the codebase labels Jun 12, 2019
@jamesnetherton jamesnetherton self-assigned this Jun 13, 2019
@jamesnetherton
Copy link
Contributor

Just want to check that my understanding of what the workflow would look like for this is correct. I was thinking something like:

  1. Install the operator 'globally':
kamel install --global --namespace camel-k
  1. Install platform into secondary namespace(s):
kamel install --skip-operator-setup --namespace namespace-1
kamel install --skip-operator-setup --namespace namespace-2
  1. Create integration(s):
kamel run example-java.java --namespace namespace-1
kamel run example-js.js --namespace namespace-2

@nicolaferraro
Copy link
Member Author

Yes, sounds good.
I think we need also a way to make sure global operator and local operator don't conflict if both are installed, but I'll open another ticket for that.

jamesnetherton added a commit to jamesnetherton/camel-k that referenced this issue Jun 18, 2019
jamesnetherton added a commit to jamesnetherton/camel-k that referenced this issue Jun 18, 2019
@oscerd oscerd closed this as completed in 79eac4e Jun 20, 2019
ipolyzos pushed a commit to ipolyzos/camel-k that referenced this issue Jul 31, 2019
squakez added a commit to squakez/camel-k that referenced this issue Jan 19, 2021
Added a description sentence to explain how to create an IntegrationPlatform after a global installation.

Ref apache#745
nicolaferraro pushed a commit that referenced this issue Jan 19, 2021
Added a description sentence to explain how to create an IntegrationPlatform after a global installation.

Ref #745
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core Core features of the integration platform good first issue Does not require full understanding of the codebase kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants