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. With the new 2.0 version out, there are great improvements which are leveraging the major release of Quarkus 2.0. We’re inheriting all the good stuff in performance and components coverage that is introduced lately in this new version.

Tune your logs

As software developers, we are daily watching logs to discover what’s going on for a piece of software that is failing. Observability and all the activities around that area are needed in order to have a reliable software solution. We know that, and we’ve introduced a new trait that will simplify the work of tuning and integrating the log streams in your logging systems.

You can learn more in a blog dedicated to the topic.

S3 dependencies

S3 protocol is often used as a way to store Maven dependencies. With version 1.5 you will be able to configure your Camel K to retrieve such dependencies.

Configuration refactoring

Prior to this version, we may have found a bit clumsy the work of providing a configuration file to our Integration. As a developer, you will now be able to define in details how and where to load a configuration file, filter a Configmap or a Secret and also distinguish between build-time and runtime properties. An entire blog covering this feature will be soon available, stay tuned!

More Kamelet love

Since their appearence, Kamelets have gained quite a lot of traction. With this new release we’ve introduced new commands in the kamel CLI to help you discovering and managing them. You will have a new command available kamel kamelet that will help you listing and deleting any Kamelet. Also kamel describe kamelet has been introduced to help you analysing the available Kamelets.

We should also mention that we’re having more Kamelets available in the Apache Camel Kamelets Catalog. We are counting 117 different source and sink Kamelets and we are actively adding many more.

Allow configuration via traits annotations

We are aware that the CLI is not the only way to create an Integration. For this reason we’ve introduced a new way to simplify the setting of a trait directly in the Integration specification. Instead of specifying a trait in the .spec.integration.traits.trait-id.configuration.trait-property you will be now able to do so via .metadata.annotations.

More test coverage

Of course, we haven’t forgot to include more unit and integration tests to our code base. With this release we’ve introduced new test cases that are giving more confidence to the development lifecycle.

Polish documentation

We are happy to announce a few new improvements in the online documentation. We’re dedicating some more time to refresh the documentation that may be missing or that can be incomplete.

Versioned documentation

One little but great improvements we’ve introduced lately is the versioning of the Camel K documentation website. Just look on the left bottom bar of your browser and you will be able to select either latest or 1.4.x.

Generated API

Another thing that is worth to mention is a first version of our API that is now available through the documentation pages. Have a look at Camel K API resources documentation page in order to understand how to interact directly with them.

Thanks

Thanks to all contributors who made this possible. We’re happy to receive feedback on this version through our mailing list, our official chat or filing an issue on Camel K Github repository.

Camel K 1.2.0 Released

 , by

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.

Continue reading ❯

RELEASESCAMEL K

Camel K 1.0 is here

 , by

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.

Continue reading ❯

RELEASESCAMEL K