© 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.
Apache Camel community is happy to announce the general availability of Camel K 2.2.0. This release has slipped finally in 2024 but here we are with a lot of new exciting developments. Enable source less Integrations This is the first step to onboard any Camel runtime. You may already have a process that build your application and containerize it in a container registry. From now on you can reference such container and use the operator to start that application without requiring the Integration to contain the source code:
It’s the time of the year when we take a look back at 2023, and compile a brief summary (by numbers) of the Apache Camel project(s). You can find previous year 2022 numbers here. Camel 2023 in Numbers Number of Camel Core releases in 2023: 33 Number of Camel Quarkus releases in 2023: 13 Number of Camel K releases in 2023: 7 Number of Camel Kafka Connector releases in 2023: 5
We have just released Apache Camel 3.22 as the last new minor release of Camel 3.x. This marks the end of new development of Camel 3, and there are no more releases planned. Camel 3.14 and 3.20 reached end of life by end of 2023. And therefore, the only supported releases of Camel 3.x are as follows: Version Supported Until 3.21.x Jun 2024 3.22.x Dec 2024 Camel 3.21.x is supported first half of 2024, and Camel 3.
Apache Camel community is happy to announce the general availability of Camel K 2.1. We have worked on the introduction of a lot of new exciting feature that will further simplify the deployment and management of Camel application on Kubernetes. Let’s see what you should expect from this release. Default Camel 4 runtime As Camel 4 is out since some time already, we’ve moved our default runtime to Camel K Runtime version 3.
This blog announce the availability of Camel K Runtime version 3.2.0 which will gives you the possibility to run Camel 4 workloads on Kubernetes with Camel K. Release details Apache Camel K Runtime 3.2.0 Apache Camel Quarkus 3.2.0 Apache Camel 4.0.0 How to run Camel 4 with Camel K If you are on Camel K 2.0, this is quite straightforward. If you recall, one of the major feature of version 2 is the ability to run any Camel K runtime.
© 2023, RoadTrafficSigns.com With a great level of excitement, on behalf of Apache Camel community, I’m proud to announce the general availability of Camel K 2.0. It’s been a long ride since the beginning of 2023 when we announced the desire to work on an heavy refactoring in order to introduce new shining features and be able to run the future Camel 4 runtimes. This is the first important milestone reached, and we thought that the work done so far is already mature to see general availability.
Signpost png from pngtree.com/ We’re in 2023 since a while (just if nobody has noticed yet…) and we’ve taken the month of January to think about how to move Camel K development forward. We had a very good discussion about the new features we’d like to see during this year and this blog is trying to resume those ideas collected. I am going to do my best to resume everybody’s comments in a shared view in order to inspire any contributor to understand the direction we’re willing to take.
(c) @TivadarDanka 2023 has come, and with that it is time to make a little retrospective on the work we have completed in 2022 in Camel K project. We are already collecting ideas to submit to the community for 2023 in order to define the new roadmap. Stay tuned, more is coming shortly… Camel K 2022 roadmap update It’s been a long ride and here a short resume of what we accomplished during the last year in Camel K project.
Apache Camel 4 is on the way for 1st half in 2023. The need for Camel 4 is mainly driven by Java open source projects migrating from javax to jakarta APIs and to keep up with popular runtimes such as Spring Boot and Quarkus. Primary Goals Migrate from javax -> jakarta (JEE 10) Java 17 as minimum Spring Framework 6 Spring Boot 3 Quarkus 3 Release Goals Release only what is ready (JEE10 / Java17) This means that Camel components that are not ready (yet) will be dropped in a release until they are ready.
It’s the time of the year when we take a look back at 2022, and compile a brief summary (by numbers) of the Apache Camel project(s). Camel 2022 in Numbers Number of Camel Core releases in 2022: 19 Number of Camel Quarkus releases in 2022: 15 Number of Camel K releases in 2022: 11 Number of Camel Kafka Connector releases in 2022: 4 Number of commits in 2022: 6162 [1]
Signpost png from pngtree.com/ During the last weeks we’ve been asked questions around the direction we’re willing to take on the future development of Camel K. I think it would be good to have some blog in order to let the community understand where our efforts are going. It will be useful for every Camel K user and Camel K developer, as a guide for the future development of the project.
All Camel projects will drop support for Java 8 by end of 2021. The next LTS release Camel 3.14, scheduled for December 2021, will be the last release to support Java 8. In light of this we will extend the support period of Camel 3.14 from 1 year to 2 years. This means Camel 3.14 will reach its end of life (EOL) at end of December 2023.
The Apache Camel project is moving to release schedule with Long Term Support (LTS) and non-LTS releases. The plan is to have 2 yearly LTS releases and then non-LTS releases in between. This allows the Camel project to innovate and move much faster in non-LTS releases. And as well to offer production stable branches (LTS) where end users can stay on for a longer period of time and get CVEs and important/critical bug fixes only.
It’s the time of the year where we take a look back at 2019, and compile a brief summary of the Apache Camel project. The big news of 2019 was the much anticipated release of Apache Camel 3. Family of projects It was also in 2019 that the Camel project became a family of projects by introducing: Camel K Camel Quarkus Making Apache Camel a trilogy. But it does not stop there; in early 2020 three will become five when we release:
The Apache Camel community introduces a new subproject in the ecosystem: Camel-Kafka-Connector. This project born as a PoC exploring the possibility of leveraging the Apache Camel components as Kafka source and sink connectors. The main idea behind the project is reusing the Camel Components’ flexibility in a simple way, through a configuration file mixing Kafka Connect configuration and Camel route definitions and options. What is Kafka Connect? It is an Apache Kafka’s framework that defines a standardized way to stream data in and out a kafka broker.
The Camel team is busy working on the last set of work for Apache Camel 3. Today the 2nd release candidate was built and published on a staging repository for early adopters to give it a try. As I am busy myself then I just wanted to write a short blog post to keep the community posted that Apache Camel 3 is on the way, and that we expect it to be released by end of this year (sometime in November or December).