We’re happy to announce Camel K 1.6 version release. About two months after releasing the previous version (1.5), we’re now glad to provide you some new exciting features and a few fixes on bugs that we discovered along the way. This is the new set of technologies on which Camel K 1.6 is depending: Apache Camel K Runtime 1.9.0 Apache Camel Quarkus 2.2.0 Apache Camel 3.11.1
A new release of VS Code Tooling support for Apache Camel K 0.0.26 is available. It notably includes compatibility with Camel K 1.5.0 and Code Lenses. Compatibility with Camel K 1.5.0 The Camel K binary provided by default is now 1.5.0. The commands are using the new API. Note: It is working too with Camel K 1.4.0 productized by Red Hat. The needed features were backported. Code Lenses A Code Lens is an information provided inside text editor.
Camel K version 1.5 is out. And with it, a new way of providing configuration and resources to your Integration. We have worked on a deep code refactoring in order to harmonize the existing configuration settings and add new ones to exploit the power of camel-quarkus runtime, which has become the main way to materialize an Integration. We added new features that will simplify your developer life. We also added new checks that will give you useful tips when using a feature in a wrong way.
Camel K 1.5 version is public since a few days. We’re proud to announce this new release containing enhancements and fixes. We’ve worked hard to fix the most important issues discovered with an eye on stabilization and performances. This new release is based on Camel Quarkus 2.0 and Apache Camel 3.11. Let’s find out what’s new in Camel K 1.5! New Camel Quarkus and Quarkus versions Camel Quarkus runtime has become the building block on which the Integration is materialized.
Kamelets (Kamel route snippets) are a new concept introduced in Camel K that allow users to connect to external systems via a simplified interface, hiding all the low level details about how those connections are implemented. There are several ways to consume them. One of them is as standard Camel Components. In this case, completion is provided to fill the template id and the parameter names. It is currently based on a fixed set of Kamelets provided by a snapshot of the kamelet catalog.
Camel K is providing a new feature to Java debug deployed integrations. Before VS Code Tooling for Apache Camel K 0.0.25, more complex steps were required to leverage the VS Code Java debugging capabilities as explained in this previous blogpost. I recorded a video which is following the steps in this blogpost. Requirements VS Code Extension Pack for Apache Camel with VS Code Tooling for Apache Camel K 0.
New Camel K Logging Features for Camel K 1.5
Apache Camel K 1.4.0 has just been released! This is a new major release of Camel K with an improved stability over previous versions, but also adding new features that simplify the overall user experience. It is based on Camel 3.9.0 and Camel-Quarkus 1.8.1, providing all improvements that they bring, plus much more. In this blog post, we’re going to describe the most important changes. Embedded Kamelet catalog Camel K 1.
We’re starting a new initiative at Apache Camel to create a community-driven catalog of reusable Kamelets (Camel route snippets, i.e. connectors) that can be used to stream data from/to external systems into any platform powered by Apache Camel. The “Apache Camel Kamelet catalog” is available here and it already contains a collection of useful Kamelets: we would like to extend it with help of the community. Kamelets are currently supported out-of-the-box by the Apache Camel K project and we’re working to support them also in Camel core, so that they can run eventually in any Apache Camel subproject, like Camel Kafka Connector (but also camel-quarkus, camel-spring-boot, …).
UPDATED ON 17 May 2021: More recent related content available in this blogpost. Camel K 1.3.0 is providing a new feature to Java debug deployed integrations. Even if Camel K 1.3.0 is not fully compatible with VS Code Tooling for Apache Camel K extension, it remains possible to leverage the VS Code Java debugging capabilities. I recorded a video which is following the steps in this blogpost. I let you choose your preferred way to discover how to java debug your Camel K integration in VS Code.
Apache Camel K 1.2.0 has been released! This version introduces some important features that will play an increasingly bigger role in future releases of Camel K. Quarkus as default runtime Camel K 1.2.0 uses camel-quarkus 1.1.0 (Quarkus 1.8.0.Final) as runtime, but Quarkus is no longer an optional runtime for Camel K: Quarkus is now the default runtime. This means that users no longer need to enable Quarkus explicitly when running their integrations (using kamel run -t quarkus.
Apache Camel K has made a lot of progress since its inception and we’re now proud to announce the 1.0 release. We’ve been working hard in the past months to add more awesome features to Camel K, but also to improve stability and performance. This post contains a list of cool stuff that you’ll find in the 1.0 GA release. First of all, if you’re living under a rock and it’s the first time you hear about Camel K, you can read some introductory blog posts here (1 - introducing camel k, 2 - camel k on knative) or look at the Apache Camel website that contains a Camel K section with a lot of material that is automatically generated from the Github repository.