You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by GitBox <gi...@apache.org> on 2019/03/19 14:00:27 UTC

[GitHub] [camel-k] nicolaferraro opened a new issue #568: Automatic installation when creating a Knative Camel Source

nicolaferraro opened a new issue #568: Automatic installation when creating a Knative Camel Source
URL: https://github.com/apache/camel-k/issues/568
 
 
   The ideal scenario for Knative users (imo) should be:
   - A cluster admin enables Camel-based sources and related resources on a cluster
   - A user selects a Camel-based source from a catalog (e.g. operatorhub catalog)
   - A user creates an instance of the Camel-based source into her namespace of preference
   - The Camel-based source is started
   
   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 

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services