© Sir John Soane’s Museum London Apache Camel community is happy to announce the general availability of Camel K 2.3.0. This release version contains several fix which are increasing the operator stability and a few hidden changes which are making the software more modular, therefore future feature development quicker and independent from the Camel runtime chosen. First of all, we have changed the default runtime to Camel K Runtime version 3.
In the last 2.2.0 version release, Camel K added an interesting feature that gave the users the possibility to build their Camel application externally and run via the operator with certain limitations. In this blog we’re trying to analyze those limitations and provide some example that will show you how to possibly leverage this feature. What is a “sourceless” Integration? With a great effort of creativity (sarcasm), we have named this feature as “sourceless” Integration.
Apache Camel 4.5 has just been released. This release introduces a set of new features and noticeable improvements that we will cover in this blog post. Camel Core When using Kamelets and/or Rest DSL then Camel will now hide their intermediate routes and only show user routes. The number of routes that Camel logs on startup is thus only the number of user routes. This also avoids cluttering up the list of routes in monitoring and management tools.