-
Notifications
You must be signed in to change notification settings - Fork 345
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
Automatic installation when creating a Knative Camel Source #568
Comments
Is it something managed by the operator lifecycle manager? |
I think we should explore also the option to have an operator that handles multiples namespaces |
Yes, our operator works oob if you specify We can:
Which one is best? |
The described scenario is exactly what OLM with Operator Hub as config source configured is supposed to provide. Besides, operator groups now provide tenancy support for operators installed via OLM: An operator can have any combination of installation modes, so the Camel K operator could support both Then from the developer catalog UI, user would browse the Camel-based sources and have the ability the instantiate any of them from the UI. This relates to #523. I'm not 100% sure yet what that means in term of code change and operator execution model. Someone (no name ;)) told me that the |
I think we should support both, but I personally won't go to the path of having an additional controller written by us that does the installation & set-up so IMHO:
|
Sounds good to me. |
This has been implemented. Additionally, platforms are auto-created on OpenShift by the platform trait. |
The ideal scenario for Knative users (imo) should be:
Currently this does not work this way, because the user needs to install the Camel K operator in each namespace where he plans to use sources.
Can we improve this?
How good is the option of creating a master-controller in a
camel-k
namespace that instantiate the operator and related resources when a Camel-based source is added to a namespace?@astefanutti , @lburgazzoli
The text was updated successfully, but these errors were encountered: