astefanutti commented on issue #568: Automatic installation when creating a Knative Camel Source URL: https://github.com/apache/camel-k/issues/568#issuecomment-474394092 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: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/Documentation/design/operatorgroups.md#installmodes-and-supported-operatorgroups An operator can have any combination of installation modes, so the Camel K operator could support both `OwnNamespace` and `AllNamespaces`. 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 `AllNamespaces` mode just instantiate the operator in each namespace. To be investigated.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
