Apache Camel is NOT using log4j for production Apache Camel does not directly depend on Log4j 2, so we are not affected by CVE-2021-44228. If you explicitly added the Log4j 2 dependency to your own applications, make sure to upgrade. Apache Camel is using log4j for testing itself Apache Camel does use log4j during testing itself, and therefore you can find that we have been using log4j v2.13.3 release in our latest LTS releases Camel 3.
Camel provides possibilities to define Integrations using Yaml language. It is the language often used for people dealing with Kubernetes/OpenShift. This language doesn’t have the same maturity than xml or java but there are tooling that can help a lot. Given that yaml specification doesn’t allow self-described yaml metadata, several conventions are introduced to provide edition support of Yaml files. This article will focus on Camel Yaml files, both plain Yaml and Custom Resource Definitions (CRD) inside VS Code.
New releases of VS Code Language support for Apache Camel 0.1.2 and VS Code Tooling for Apache Camel K 0.0.28 are available. It includes several version upgrades. Version upgrades The default Kamel binary used has been upgraded from 1.6.0 to 1.7.0. The language support contains these upgrades: Default Camel Catalog version from 3.12.0 to 3.13.0 Kamelet Catalog from 0.4.0 to 0.5.0 Camel Quarkus Catalog from 2.3.0 to 2.4.0 Camel K trait Catalog from 1.