[GitHub] [camel-k-runtime] nicolaferraro opened a new issue #150: Support explicit source/target in knative endpoint

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-k-runtime] nicolaferraro opened a new issue #150: Support explicit source/target in knative endpoint

GitBox
nicolaferraro opened a new issue #150: Support explicit source/target in knative endpoint
URL: https://github.com/apache/camel-k-runtime/issues/150
 
 
   Currently Camel K 1.0.0-M2 has a pre-baked list of allowed endpoints that can be used as start or end of a route.
   
   E.g.
   
   ```
   from('knative:channel/xx`)
   ```
   
   The Knative trait looks for:
   - `eventing.knative.dev/v1alpha1 -> Channel`
   - `messaging.knative.dev/v1alpha1 -> Channel`
   - `messaging.knative.dev/v1alpha1 -> InMemoryChannel`
   - `messaging.knative.dev/v1alpha1 -> KafkaChannel`
   - ...
   
   A similar thing happen for the `knative/endpoint`.
   
   It would be better if a user can explicitly set the target, like:
   
   ```
   from('knative:channel/xx?kind=InMemoryChannel')
   ```
   
   or even:
   ```
   from('knative:channel/xx?kind=InMemoryChannel&apiVersion=messaging.knative.dev/v1')
   ```
   
   Same also for `endpoint`. In the case of channel, the operator creates also a subscription.
   
   The resolution of the apiVersion and kind will happen at operator level, but those properties need to be accepted by the runtime.
   
   Wdyt @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:
[hidden email]


With regards,
Apache Git Services