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 2023/07/24 14:40:21 UTC
[camel-website] 09/10: chore: set release date and links
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 eb0188370e453207a543ed40b6fe566c04f03144
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Mon Jul 24 10:11:47 2023 +0200
chore: set release date and links
---
content/blog/2023/07/camel-k-2-0/index.md | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/content/blog/2023/07/camel-k-2-0/index.md b/content/blog/2023/07/camel-k-2-0/index.md
index 4193182e..3f16e00a 100644
--- a/content/blog/2023/07/camel-k-2-0/index.md
+++ b/content/blog/2023/07/camel-k-2-0/index.md
@@ -1,6 +1,6 @@
---
title: "Camel K 2.0"
-date: 2023-07-13
+date: 2023-07-24
draft: false
authors: [squakez]
categories: ["Releases", "Camel K", "Roadmap"]
@@ -14,6 +14,17 @@ This is the first important milestone reached, and we thought that the work done
Let's look at one by one the main new features or updates that Camel K 2.0 is introducing. We plan to work on more blogs and documentation dedicated to each of the new features introduced during next months.
+# Release details
+
+You can find all the CLIs and detailed changelog information in the [Camel K 2.0.0 release page](https://github.com/apache/camel-k/releases/tag/v2.0.0). Download the CLI for your operating system and architecture, `kamel install` and be ready to use the latest features available.
+
+As usual, we acknowledge the great work done in Apache Camel community. Camel K default runtime is based on the following projects:
+
+* Apache Camel K Runtime 2.16.0
+* Apache Camel Quarkus 2.16.0
+* Apache Camel 3.20.1
+* Apache Camel Kamelets 3.20.1.1
+
# Upgrade from V1
The first concern you may have is about compatibility to Camel K version 1 and how to upgrade: we have worked to make this process as smooth as possible. We introduced some important change in the Kubernetes API and we tried to make this in a backward compatible manner. In particular we have promoted the `v1alpha1.Kamelet/KameletBinding` API to `v1` as we now feel it's mature enough and we have renamed the `v1alpha1.KameletBinding` to `v1.Pipe`.