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

  • Apache Camel Kamelets 0.4.0

New Camel Quarkus version

We have a set of new exciting dependencies that we leverage. Among them we can see the fresh Camel Quarkus 2.2.0. Have a look at the dedicated blog to learn more about it.

Scalable KameletBinding

We’re more and more getting used to Kamelet and KameletBinding adoption. One of the new things introduced in version 1.6 is the possibility to scale a KameletBinding via kubectl (or oc) CLI. Learn more about how to scale a KameletBinding. One of the coolest thing is that you can even use HPA (Horizontal Pod Autoscaling)!

Kamel bind enhancement

The kamel bind subcommand was recently introduced to simplify the creation of binding between source and sinks. We are enriching it with new features at every release. With this version you will be able to use --error-handler parameter in order to set an error handler that will take over in case of an event fault.

Support https liveness and readiness probes

Security in transit is a must. Even for probes. We have improved the container trait in order to allow setting liveness and readiness probes with https scheme.

More Kamelet love

We have reached 150+ official Kamelet! If you need some connector to quickly source or sink your events, then, the Apache Camel Kamelet Catalog is the place.

Bug fixes, test coverage and documentation

And of course, last but not least, we have dedicated an important effort to close known bugs, keep raising the bar of quality adding tests and documentation.

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.5 release

 , by

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.

Continue reading ❯

RELEASESCAMEL K

New release of VS Code Tooling support for Apache Camel K 0.0.26

 , by

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.

Continue reading ❯

RELEASESTOOLINGCAMEL K

Camel K 1.5 - New configuration settings

 , by

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.

Continue reading ❯

FEATURESCAMEL K

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