In that week I had much customer conversations, but not much really interesting news to post here. Except the Camel K deprecation statements and some things I would like to add.

Camel K deprecation, Red Hat’s build of Apache Camel 4

A customer had some questions about the deprecation of Red Hat’s Camel K and the plans for Red Hat’s build of Apache Camel 4. For over six years, Camel K has pioneered cloud-native, low-code, and managed integration services. Recently, many of Camel K’s capabilities have been standardized and integrated into Camel Core. That’s just the way Red Hat does things, we want the innovation that comes from our own downstream projects (which often comes from customer requests) to also flow into the upstream community projects. This allows all Camel customers to benefit from cloud-native advancements. Kaoto is of course still supported and has only received some mixed messages regarding internal interaction with Camel.

We had a proof of concept at a customer and updated our deployment shell script to the new mechanisms, here’s the diff commit code. As you can see, we don’t use kamel run anymore, and call camel export statements instead. Afterwards we build the application as usual, here via maven.

All in all this is a statement of dedication to the community and a good signal from Red Hat.