You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2026/04/14 06:58:34 UTC

(camel-website) branch main updated (5860695d -> 2af6cfe4)

This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git


    from 5860695d chore(deps): bump convict from 6.2.4 to 6.2.5
     new 31a25b17 feat(doc): camel k 2.10 release
     new 2af6cfe4 chore: add release info

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 antora-playbook-snippets/antora-playbook.yml   |   1 +
 content/blog/2026/04/camel-k-2-10/featured.png | Bin 0 -> 1021173 bytes
 content/blog/2026/04/camel-k-2-10/index.md     |  56 +++++++++++++++++++++++++
 content/releases/k/release-2.10.0.md           |  12 ++++++
 content/releases/k/release-2.9.1.md            |  12 ++++++
 5 files changed, 81 insertions(+)
 create mode 100644 content/blog/2026/04/camel-k-2-10/featured.png
 create mode 100644 content/blog/2026/04/camel-k-2-10/index.md
 create mode 100644 content/releases/k/release-2.10.0.md
 create mode 100644 content/releases/k/release-2.9.1.md


(camel-website) 02/02: chore: add release info

Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit 2af6cfe402ac46ec3ba7ab6c8be541f94c00c900
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Sun Apr 12 09:46:27 2026 +0200

    chore: add release info
---
 antora-playbook-snippets/antora-playbook.yml |  1 +
 content/releases/k/release-2.10.0.md         | 12 ++++++++++++
 content/releases/k/release-2.9.1.md          | 12 ++++++++++++
 3 files changed, 25 insertions(+)

diff --git a/antora-playbook-snippets/antora-playbook.yml b/antora-playbook-snippets/antora-playbook.yml
index 6975c585..bac5e89e 100644
--- a/antora-playbook-snippets/antora-playbook.yml
+++ b/antora-playbook-snippets/antora-playbook.yml
@@ -32,6 +32,7 @@ content:
       branches:
         - main
         - release-2.9.x
+        - release-2.10.x
       start_path: docs
 
     - url: https://github.com/apache/camel-kamelets.git
diff --git a/content/releases/k/release-2.10.0.md b/content/releases/k/release-2.10.0.md
new file mode 100644
index 00000000..a60200eb
--- /dev/null
+++ b/content/releases/k/release-2.10.0.md
@@ -0,0 +1,12 @@
+---
+url: "/releases/k-2.10.0/"
+date: 2026-04-13
+type: release-note
+version: "2.10.0"
+title: "Camel-K 2.10.0"
+preview: ""
+changelog: ""
+category: "camel-k"
+milestone: 60
+jdk: [17,21]
+---
diff --git a/content/releases/k/release-2.9.1.md b/content/releases/k/release-2.9.1.md
new file mode 100644
index 00000000..adcf999b
--- /dev/null
+++ b/content/releases/k/release-2.9.1.md
@@ -0,0 +1,12 @@
+---
+url: "/releases/k-2.9.1/"
+date: 2026-02-11
+type: release-note
+version: "2.9.1"
+title: "Camel-K 2.9.1"
+preview: ""
+changelog: ""
+category: "camel-k"
+milestone: 61
+jdk: [17,21]
+---


(camel-website) 01/02: feat(doc): camel k 2.10 release

Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit 31a25b17f72ca201bea62c329cadb3b82ab5d28b
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Sat Apr 11 09:56:44 2026 +0200

    feat(doc): camel k 2.10 release
---
 content/blog/2026/04/camel-k-2-10/featured.png | Bin 0 -> 1021173 bytes
 content/blog/2026/04/camel-k-2-10/index.md     |  56 +++++++++++++++++++++++++
 2 files changed, 56 insertions(+)

diff --git a/content/blog/2026/04/camel-k-2-10/featured.png b/content/blog/2026/04/camel-k-2-10/featured.png
new file mode 100644
index 00000000..70ad1950
Binary files /dev/null and b/content/blog/2026/04/camel-k-2-10/featured.png differ
diff --git a/content/blog/2026/04/camel-k-2-10/index.md b/content/blog/2026/04/camel-k-2-10/index.md
new file mode 100644
index 00000000..e61b9979
--- /dev/null
+++ b/content/blog/2026/04/camel-k-2-10/index.md
@@ -0,0 +1,56 @@
+---
+title: "Camel K 2.10.0"
+date: 2025-04-13
+draft: false
+authors: [squakez]
+categories: ["Releases", "Camel K", "Roadmap"]
+preview: "What's new in Camel K 2.10.0!"
+---
+
+*© Smithsonian Magazine*
+
+Here a new fresh release of Camel K: version 2.10.0 is ready to go. We've worked to several improvements around the GitOps and Git features introduced lately. We've stabilized a few bugs discovered and upgraded dependencies as well.
+
+## GitOps Pipe
+
+We've worked to make sure the **Camel GitOps** is available not only for Integrations but also for Pipes. The principle is exactly the same. You need to configure the `gitops` trait on the Pipe you want to include in your GitOps flow and the operator will be in charge to provide a PR on the Git repository with the Pipe custom resource.
+
+## GitOps and dry build
+
+We had this work pending in the last release. From version 2.10 onward you'll be able to join the GitOps feature with the "dry-build" feature. I.E. you can do a **complete build and deployment system** without the need to run the application on a development environment. With this flexibility you can compose your pipelines to include any testing and staging environments before the Camel application reaches production environment.
+
+## Build from Git monorepo
+
+Another Git based feature is the possibility to select a path from where you want to build your application. This is nice if you have a monorepo with several internal applications. You can now configure the Integration to build from a Git repo pointing also to a specific directory.
+
+## Kubernetes Gateway API support
+
+There were recently some discussion around Kubernetes Ingress and we decided to prioritize the work we had pending around the new **Kubernetes Gateway API**. From version 2.10 onward we're fully supporting it. The Ingress is still an important piece of K8S architecture but it will be likely replaced in the long term by the Gateway. We're ready for anyone wanting to use this API as well.
+
+## IntegrationProfile dependencies
+
+IntegrationProfile custom resource is the future way we'll support to collect **common configuration** for all Integrations. We were missing the possibility to include here dependencies. Now we have it!
+
+## Deprecations
+
+In this release we're deprecating what we have experimentally developed some time ago which we called "Synthetic Integrations". This feature allowed you to be able to monitor in Camel K any Camel application that was deployed externally from the operator. We are replacing it with a new project (we're temporarily calling it ["Camel Dashboard"](https://camel-tooling.github.io/camel-dashboard/)) that is going to be a great complementary service to Camel K. During 2026 you'll surely hear mor [...]
+
+## Main dependencies
+
+The operator was built with Golang 1.25 and the Kubernetes API is aligned with version 1.35. We haven't changed the Camel K Runtime LTS version (3.15.3, based on Camel 4.8.5): this is for backward compatibility reasons. As mentioned already since version 2.7, we're pushing to the usage of `plain-quarkus` provider, which allow you to **use any released Camel Quarkus version**, or Git stored Camel projects.
+
+## Full release notes
+
+We had done more stuff, here the full [2.10.0 release notes](https://github.com/apache/camel-k/releases/tag/v2.10.0) if you want to learn more about this release.
+
+## Stats
+
+Here some stats that may be useful for development team to track the health of the project (release over release diff percentage):
+
+* Github project stars: 916 (+1,5 %)
+* [Docker pulls over time](https://hub.docker.com/v2/repositories/apache/camel-k/): 2479009 (+1,8 %)
+* Unit test coverage: 62.2 % (+1,8 %)
+
+# Thanks
+
+Thanks a lot to our contributors and the hard work happening in the community. Feel free to provide any feedback or comment using the Apache Camel available channels.