[
https://issues.apache.org/jira/browse/CAMEL-15275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-15275:
--------------------------------
Fix Version/s: 3.15.0
(was: 3.14.0)
> Create camel-knative component in main Camel components based on
> camel-knative for camel-k
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-15275
> URL: https://issues.apache.org/jira/browse/CAMEL-15275
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 3.4.0
> Reporter: Omar Al-Safi
> Priority: Major
> Fix For: 3.15.0
>
>
> Currently we have [{{camel-knative}}
> component|https://github.com/apache/camel-k-runtime/tree/master/camel-knative]
> in camel-k that enables camel routes deployed in with camel-k to interact
> with knative components like eventing. However, currently it is only
> exclusive to camel-k, hence it will make sense to bring/create this component
> as part of the main Camel components in order in order to enable non-camel-k
> routes that deployed with knative (e.g: camel-quarkus, camel-spring-boot) to
> utilize and interact in kantive.
> FYI [~davsclaus] [~lb]] thoughts on this? I recall there was some discussion
> on brining this component to main Camel components.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
