Camel K deprecated.

Author: brunoNetId

.github/workflows/docs.yml

@@ -19,7 +19,7 @@ jobs:
         with:
           antora_playbook: site.yml
       - name: "Upload generated site"
-        uses: actions/upload-artifact@v1.0.0
+        uses: actions/upload-artifact@v4
         with:
           name: site
           path: "${{ github.workspace }}/${{ env.SITE_DIR }}"
@@ -31,7 +31,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v2
       - name: Download generated site
-        uses: actions/download-artifact@v1
+        uses: actions/download-artifact@v4
         with:
           name: site
           path: "${{ github.workspace }}/${{ env.SITE_DIR }}"

README.adoc

@@ -3,7 +3,7 @@ Application Development is evolving as the modern Hybrid Cloud and cloud-native
 
 As  Red Hat Fuse approaches product End of Life (EOL) on June 30, 2024,  Red Hat build of Apache Camel is the natural go-forward solution for integrations built around Red Hat Fuse which is based on an older version of Apache Camel. Fuse will remain in the https://access.redhat.com/support/policy/updates/jboss_notes#phases[maintenance life cycle^] until its EOL. 
 
-The https://developers.redhat.com/products/redhat-build-of-apache-camel/overview[Red Hat build of Apache Camel^] is the evolution for Red Hat Fuse, and  is a powerful, versatile framework for application integration. It also includes running Camel on Quarkus and Spring Boot runtimes in both on-premise and cloud environments, including the Camel K operator which streamlines building, deploying and operating Camel integrations on OpenShift.
+The https://developers.redhat.com/products/redhat-build-of-apache-camel/overview[Red Hat build of Apache Camel^] is the evolution for Red Hat Fuse, and  is a powerful, versatile framework for application integration. It also includes running Camel on Quarkus and Spring Boot runtimes in both on-premise and cloud environments.
 
 Performing such a migration can be scary as the effort is not just limited to migrating the high level Camel routes. Indeed, many other underlying technical components (JDK version, Runtime type, XML format etc.) are involved in the migration.
 

documentation/modules/ROOT/assets/images/runtimes-0.png

@@ -36,11 +36,10 @@ As a migration does not bring immediate new business value, it's important that
 == An in-depth look at the solution's architecture
 
 The Red Hat build of Apache Camel is an Cloud-native, multi-language and a multi-runtime integration stack.
-Camel-based integration logic can be written in XML or Java, and can behave as a Spring Boot, a Quarkus, or a Serverless artifact. 
+Camel-based integration logic can be written in YAML, XML or Java, and can behave as a Spring Boot or Quarkus. 
 
 The present demo will take a legacy API developed in JBoss Fuse 6.2 on Karaf, in Blueprint XML.
 It's suggested that such an application targets the Quarkus runtime.
-The provided Quarkus template is 100% compatible with Camel K, so the resulting migrated application is immediately ready to be added to a serverless stack.
 
 The material can be used to migrate any Fuse 6 or 7 distribution to the Red Hat build of Apache Camel.
 The demos will however focus on migrating a Fuse 6 application, and more concretely a Camel v2.17 one, in Blueprint XML format, running on Karaf 2. The XML format will be converted to the optimized IO XML one.
@@ -60,8 +59,8 @@ In general, the following migration strategy should be considered:
 
 * *Target*
 
-Probably, the target should remain a "standard" container application, ready for Serverless but not mandatorily a Function. +
-Thus, the demos will showcase several migrations to "plain" Spring Boot or quarkus applications, and there will be one extra demo to showcase a migration from that result to Camel K.  
+Probably, the target should remain a "standard" container application. +
+The demos will showcase several migrations to "plain" Spring Boot or quarkus applications.  
 
 
 [#more_tech]

documentation/modules/ROOT/assets/images/runtimes-1.png

@@ -5,6 +5,15 @@
 
 = See the Solution in Action
 
+[IMPORTANT]
+--
+The solution and examples in this chapter utilize integrations based on _Apache Camel K_. While _Camel K_ is still active within upstream _Apache Camel_, Red Hat has shifted its support to a cloud-native approach, focusing on https://camel.apache.org/manual/camel-jbang.html[_Camel JBang_^] and https://kaoto.io[_Kaoto_^] as primary development tools.
+
+As a result, all Camel K instances in this Solution Pattern will transition to the https://developers.redhat.com/products/redhat-build-of-apache-camel/overview[Red Hat build of Apache Camel^], aligning with Red Hat's new strategic direction.
+--
+
+{empty} +
+
 == Demonstration
 
 [#demo-video]

documentation/modules/ROOT/pages/02-architecture.adoc

@@ -8,7 +8,7 @@ Application Development is evolving as the modern Hybrid Cloud and cloud-native
 
 As  Red Hat Fuse approaches product End of Life (EOL) on June 30, 2024,  Red Hat build of Apache Camel is the natural go-forward solution for integrations built around Red Hat Fuse which is based on an older version of Apache Camel. Fuse will remain in the https://access.redhat.com/support/policy/updates/jboss_notes#phases[maintenance life cycle^] until its EOL. 
 
-The https://developers.redhat.com/products/redhat-build-of-apache-camel/overview[Red Hat build of Apache Camel^] is the evolution for Red Hat Fuse, and  is a powerful, versatile framework for application integration. It also includes running Camel on Quarkus and Spring Boot runtimes in both on-premise and cloud environments, including the Camel K operator which streamlines building, deploying and operating Camel integrations on OpenShift.
+The https://developers.redhat.com/products/redhat-build-of-apache-camel/overview[Red Hat build of Apache Camel^] is the evolution for Red Hat Fuse, and  is a powerful, versatile framework for application integration. It also includes running Camel on Quarkus and Spring Boot runtimes in both on-premise and cloud environments.
 
 Performing such a migration can be scary as the effort is not just limited to migrating the high level Camel routes. Indeed, many other underlying technical components (JDK version, Runtime type, XML format etc.) are involved in the migration.
 
@@ -22,8 +22,8 @@ Contributors: _Michael Thirion (Red Hat)_
 
 Common use cases that can be address with this solution are:
 
-- Migrate Fuse 6.x (Blueprint XML, Spring XML or Java) applications to the Red Hat build of Apache Camel, targeting either Sprin Boot 3, Quarkus or Camel K.
-- Migrate Fuse 7 (Karaf or Spring Boot) applications to the Red Hat build of Apache Camel, targeting either Spring Boot 3, Quarkus or Camel K.
+- Migrate Fuse 6.x (Blueprint XML, Spring XML or Java) applications to the Red Hat build of Apache Camel, targeting either Sprin Boot 3, Quarkus.
+- Migrate Fuse 7 (Karaf or Spring Boot) applications to the Red Hat build of Apache Camel, targeting either Spring Boot 3, Quarkus.
 - Start writing Camel 4.x applications right away with no effort