Chapter 1. Camel K release notes

Camel K is a lightweight integration framework built from Apache Camel K that runs natively in the cloud on OpenShift. Camel K is specifically designed for serverless and microservice architectures. You can use Camel K to instantly run integration code written in Camel Domain Specific Language (DSL) directly on OpenShift.

Using Camel K with OpenShift Serverless and Knative, containers are automatically created only as needed and are autoscaled under load up and down to zero. This removes the overhead of server provisioning and maintenance and enables you to focus instead on application development.

Using Camel K with OpenShift Serverless and Knative Eventing, you can manage how components in your system communicate in an event-driven architecture for serverless applications. This provides flexibility and creates efficiencies using a publish/subscribe or event-streaming model with decoupled relationships between event producers and consumers.

1.1. Camel K features

The Camel K provides cloud-native integration with the following main features:

Knative Serving for autoscaling and scale-to-zero
Knative Eventing for event-driven architectures
Performance optimizations using Quarkus runtime by default
Camel integrations written in Java or YAML DSL
Monitoring of integrations using Prometheus in OpenShift
Quickstart tutorials
Kamelet Catalog for connectors to external systems such as AWS, Jira, and Salesforce
Support for Timer and Log Kamelets
Metering for Camel K Operator and pods
Support for IBM MQ connector
Support for Oracle 19 database

1.2. Supported Configurations

For information about Camel K supported configurations, standards, and components, see the following Customer Portal articles:

1.2.1. Camel K Operator metadata

The Camel K includes updated Operator metadata used to install Camel K from the OpenShift OperatorHub. This Operator metadata includes the Operator bundle format for release packaging, which is designed for use with OpenShift Container Platform 4.6 or later.

Additional resources

Operator bundle format in the OpenShift documentation.

1.3. Important notes

Important notes for the Red Hat Integration - Camel K release:

Support to run Camel K on ROSA: Camel K is now supported to run on Red Hat OpenShift Service on AWS (ROSA).
Support for IBM MQ source connector in Camel K: IBM MQ source connector kamelet is added to latest Camel K.
Support for Oracle 19: Oracle 19 is now supported in Camel K. Refer Supported configurations page for more information.
Using Camel K CLI commands on Windows machine: When using kamel cli commands on Windows machine, the path in the resource option in the command must use linux format. For example,

//Windows path
kamel run file.groovy --dev --resource file:C:\user\folder\tempfile@/tmp/file.txt

//Must be converted to
kamel run file.groovy --dev --resource file:C:/user/folder/tempfile@/tmp/file.txt

Red Hat Integration - Camel K Operator image size is increased: Since Red Hat Integration - Camel K 1.8.1.redhat-00024, the size of the Camel K Operator image is doubled.
Accepted Camel case notations in YAML DSL: Since Red Hat Integration - Camel K 1.8.1.redhat-00024, the YAML DSL will accept camel case notation (i.e, setBody) as well as snake case (i.e set-body). Please note that there are some differences in the syntax as schema is subject to changes within Camel versions.

1.4. Supported Camel Quarkus extensions

This section lists the Camel Quarkus extensions that are supported for this release of Camel K (only when used inside a Camel K application).

Note

These Camel Quarkus extensions are supported only when used inside a Camel K application. These Camel Quarkus extensions are not supported for use in standalone mode (without Camel K).

1.4.1. Supported Camel Quarkus connector extensions

The following table shows the Camel Quarkus connector extensions that are supported for this release of Camel K (only when used inside a Camel K application).

Name	Package
AWS 2 Kinesis	`camel-quarkus-aws2-kinesis`
AWS 2 Lambda	`camel-quarkus-aws2-lambda`
AWS 2 S3 Storage Service	`camel-quarkus-aws2-s3`
AWS 2 Simple Notification System (SNS)	`camel-quarkus-aws2-sns`
AWS 2 Simple Queue Service (SQS)	`camel-quarkus-aws2-sqs`
Cassandra CQL	`camel-quarkus-cassandraql`
File	`camel-quarkus-file`
FTP	`camel-quarkus-ftp`
FTPS	`camel-quarkus-ftp`
SFTP	`camel-quarkus-ftp`
HTTP	`camel-quarkus-http`
JMS	`camel-quarkus-jms`
Kafka	`camel-quarkus-kafka`
Kamelets	`camel-quarkus-kamelet`
Metrics	`camel-quarkus-microprofile-metrics`
MongoDB	`camel-quarkus-mongodb`
Salesforce	`camel-quarkus-salesforce`
SQL	`camel-quarkus-sql`
Timer	`camel-quarkus-timer`

1.4.2. Supported Camel Quarkus dataformat extensions

The following table shows the Camel Quarkus dataformat extensions that are supported for this release of Camel K (only when used inside a Camel K application).

Name	Package
Avro	`camel-quarkus-avro`
Bindy (for CSV)	`camel-qaurkus-bindy`
Gson	`camel-quarkus-gson`
JSON Jackson	`camel-quarkus-jackson`
Jackson Avro	`camel-quarkus-jackson-avro`

1.4.3. Supported Camel Quarkus language extensions

In this release, Camel K supports the following Camel Quarkus language extensions (for use in Camel expressions and predicates):

Constant
ExchangeProperty
File
Header
Ref
Simple
Tokenize
JsonPath

1.4.4. Supported Camel K traits

In this release, Camel K supports the following Camel K traits.

Builder trait
Camel trait
Container trait
Dependencies trait
Deployer trait
Deployment trait
Environment trait
Jvm trait
Kamelets trait
Owner trait
Platform trait
Pull Secret trait
Prometheus trait
Quarkus trait
Route trait
Service trait
Error Handler trait

1.5. Supported Kamelets

The following table lists the kamelets that are provided as OpenShift resources when you install the Camel K operator.

For details about these kamelets, go to: https://github.com/openshift-integration/kamelet-catalog/tree/kamelet-catalog-1.8

For information about how to use kamelets to connect applications and services, see https://access.redhat.com/documentation/en-us/red_hat_integration/2022.q3/html-single/integrating_applications_with_kamelets.

Important

Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production.

These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview.

Table 1.1. Kamelets provided with the Camel K operator
Kamelet	File name	Type (Sink, Source, Action)
Ceph sink	`ceph-sink.kamelet.yaml`	Sink
Ceph Source	`ceph-source.kamelet.yaml`	Source
Jira Add Comment sink	`jira-add-comment-sink.kamelet.yaml`	Sink
Jira Add Issue sink	`jira-add-issue-sink.kamelet.yaml`	Sink
Jira Transition Issue sink	`jira-transition-issue-sink.kamelet.yaml`	Sink
Jira Update Issue sink	`jira-update-issue-sink.kamelet.yaml`	Sink
Avro Deserialize action	`avro-deserialize-action.kamelet.yaml`	Action (data conversion)
Avro Serialize action	`avro-serialize-action.kamelet.yaml`	Action (data conversion)
AWS DynamoDB sink	`aws-ddb-sink.kamelet.yaml`	Sink
AWS Redshift sink	`aws-redshift-sink.kamelet.yaml`	Sink
AWS 2 Kinesis sink	`aws-kinesis-sink.kamelet.yaml`	Sink
AWS 2 Kinesis source	`aws-kinesis-source.kamelet.yaml`	Source
AWS 2 Lambda sink	`aws-lambda-sink.kamelet.yaml`	Sink
AWS 2 Simple Notification System sink	`aws-sns-sink.kamelet.yaml`	Sink
AWS 2 Simple Queue Service sink	`aws-sqs-sink.kamelet.yaml`	Sink
AWS 2 Simple Queue Service source	`aws-sqs-source.kamelet.yaml`	Source
AWS 2 Simple Queue Service FIFO sink	`aws-sqs-fifo-sink.kamelet.yaml`	Sink
AWS 2 S3 sink	`aws-s3-sink.kamelet.yaml`	Sink
AWS 2 S3 source	`aws-s3-source.kamelet.yaml`	Source
AWS 2 S3 Streaming Upload sink	`aws-s3-streaming-upload-sink.kamelet.yaml`	Sink
Azure Storage Blob Source (Technology Preview)	`azure-storage-blob-source.kamelet.yaml`	Source
Azure Storage Blob Sink (Technology Preview)	`azure-storage-blob-sink.kamelet.yaml`	Sink
Azure Storage Queue Source (Technology Preview)	`azure-storage-queue-source.kamelet.yaml`	Source
Azure Storage Queue Sink (Technology Preview)	`azure-storage-queue-sink.kamelet.yaml`	Sink
Cassandra sink	`cassandra-sink.kamelet.yaml`	Sink
Cassandra source	`cassandra-source.kamelet.yaml`	Source
Extract Field action	`extract-field-action.kamelet.yaml`	Action
FTP sink	`ftp-sink.kamelet.yaml`	Sink
FTP source	`ftp-source.kamelet.yaml`	Source
Has Header Key Filter action	`has-header-filter-action.kamelet.yaml`	Action (data transformation)
Hoist Field action	`hoist-field-action.kamelet.yaml`	Action
HTTP sink	`http-sink.kamelet.yaml`	Sink
Insert Field action	`insert-field-action.kamelet.yaml`	Action (data transformation)
Insert Header action	`insert-header-action.kamelet.yaml`	Action (data transformation)
Is Tombstone Filter action	`is-tombstone-filter-action.kamelet.yaml`	Action (data transformation)
Jira source	`jira-source.kamelet.yaml`	Source
JMS sink	`jms-amqp-10-sink.kamelet.yaml`	Sink
JMS source	`jms-amqp-10-source.kamelet.yaml`	Source
JMS IBM MQ sink	`jms-ibm-mq-sink.kamelet.yaml`	Sink
JMS IBM MQ source	`jms-ibm-mq-source.kamelet.yaml`	Source
JSON Deserialize action	`json-deserialize-action.kamelet.yaml`	Action (data conversion)
JSON Serialize action	`json-serialize-action.kamelet.yaml`	Action (data conversion)
Kafka sink	`kafka-sink.kamelet.yaml`	Sink
Kafka source	`kafka-source.kamelet.yaml`	Source
Kafka Topic Name Filter action	`topic-name-matches-filter-action.kamelet.yaml`	Action (data transformation)
Log sink (for development and testing purposes)	`log-sink.kamelet.yaml`	Sink
MariaDB sink	`mariadb-sink.kamelet.yaml`	Sink
Mask Fields action	`mask-field-action.kamelet.yaml`	Action (data transformation)
Message TimeStamp Router action	`message-timestamp-router-action.kamelet.yaml`	Action (router)
MongoDB sink	`mongodb-sink.kamelet.yaml`	Sink
MongoDB source	`mongodb-source.kamelet.yaml`	Source
MySQL sink	`mysql-sink.kamelet.yaml`	Sink
PostgreSQL sink	`postgresql-sink.kamelet.yaml`	Sink
Predicate filter action	`predicate-filter-action.kamelet.yaml`	Action (router/filter)
Protobuf Deserialize action	`protobuf-deserialize-action.kamelet.yaml`	Action (data conversion)
Protobuf Serialize action	`protobuf-serialize-action.kamelet.yaml`	Action (data conversion)
Regex Router action	`regex-router-action.kamelet.yaml`	Action (router)
Replace Field action	`replace-field-action.kamelet.yaml`	Action
Salesforce Create	`salesforce-create-sink.kamelet.yaml`	Sink
Salesforce Delete	`salesforce-delete-sink.kamelet.yaml`	Sink
Salesforce Update	`salesforce-update-sink.kamelet.yaml`	Sink
SFTP sink	`sftp-sink.kamelet.yaml`	Sink
SFTP source	`sftp-source.kamelet.yaml`	Source
Slack source	`slack-source.kamelet.yaml`	Source
SQL Server Database sink	`sqlserver-sink.kamelet.yaml`	Sink
Telegram source	`telegram-source.kamelet.yaml`	Source
Throttle action	`throttle-action.kamelet.yaml`	Action
Timer source (for development and testing purposes)	`timer-source.kamelet.yaml`	Source
TimeStamp Router action	`timestamp-router-action.kamelet.yaml`	Action (router)
Value to Key action	`value-to-key-action.kamelet.yaml`	Action (data transformation)

1.6. Camel K known issues

The following known issues apply to the Camel K:

ENTESB-15306 - CRD conflicts between Camel K and Fuse Online

If an older version of Camel K has ever been installed in the same OpenShift cluster, installing Camel K from the OperatorHub fails due to conflicts with custom resource definitions. For example, this includes older versions of Camel K previously available in Fuse Online.

For a workaround, you can install Camel K in a different OpenShift cluster, or enter the following command before installing Camel K:

$ oc get crds -l app=camel-k -o json | oc delete -f -

ENTESB-15858 - Added ability to package and run Camel integrations locally or as container images

Packaging and running Camel integrations locally or as container images is not currently included in the Camel K and has community-only support.

For more details, see the Apache Camel K community.

ENTESB-16477 - Unable to download jira client dependency with productized build

When using Camel K operator, the integration is unable to find dependencies for jira client. The work around is to add the atlassian repo manually.

apiVersion: camel.apache.org/v1
kind: IntegrationPlatform
metadata:
  labels:
    app: camel-k
  name: camel-k
spec:
  configuration:
  - type: repository
    value: <atlassian repo here>

ENTESB-17033 - Camel-K ElasticsearchComponent options ignored

When configuring the Elasticsearch component, the Camel K ElasticsearchComponent options are ignored. The work around is to add getContext().setAutowiredEnabled(false) when using the Elasticsearch component.

ENTESB-17061 - Can’t run mongo-db-source kamelet route with non-admin user - Failed to start route mongodb-source-1 because of null

It is not possible to run mongo-db-source kamelet route with non-admin user credentials. Some part of the component require admin credentials hence it is not possible run the route as a non-admin user.

1.7. Camel K Fixed Issues

The following sections list the issues that have been fixed in Red Hat Integration - Camel K 1.8.1.redhat-00024.

1.7.1. Feature requests in Camel K 1.8.1.redhat-00024

The following table lists the feature requests in Camel K 1.8.1.redhat-00024.

Table 1.2. Camel K 1.8.1.redhat-00024 Enhancements
Issue	Description
ENTESB-19061	Camel K - Kamelet for Red Hat Ceph Storage Object (S3)
ENTESB-19366	Create Jira Sink kamelets

1.7.2. Enhancements in Camel K 1.8.1.redhat-00024

The following table lists the enhancements in Camel K 1.8.1.redhat-00024.

Table 1.3. Camel K 1.8.1.redhat-00024 Enhancements
Issue	Description
ENTESB-16888	Synchronize Camel K productization version with the actual product version
ENTESB-16931	Consider migration of Camel-K operator to ALL-NAMESPACES
ENTESB-17173	Publish operator to 1.x and 1.6.x channel moving forward
ENTESB-19598	Add unit tests for camel-kamelet-utils

1.7.3. Bugs resolved in Camel K 1.8.1.redhat-00024

The following table lists the resolved bugs in Camel K 1.8.1.redhat-00024.

Table 1.4. Camel K 1.8.1.redhat-00024 Resolved Bugs
Issue	Description
ENTESB-16168	CVE-2021-22135 elasticsearch: Document disclosure flaw in the Elasticsearch suggester [rhint-camel-k-1]
ENTESB-16326	CVE-2021-29427 gradle: repository content filters do not work in Settings pluginManagement [rhint-camel-k-1]
ENTESB-16746	CVE-2021-28169 jetty: requests to the ConcatServlet and WelcomeFilter are able to access protected resources within the WEB-INF directory [rhint-camel-k-1]
ENTESB-16924	CVE-2021-34428 jetty: SessionListener can prevent a session from being invalidated breaking logout [rhint-camel-k-1]
ENTESB-17037	CVE-2021-3642 wildfly-elytron: possible timing attack in ScramServer [rhint-camel-k-1]
ENTESB-17559	Kamelet has-header-filter-action differs in upstream.
ENTESB-17672	Camel K images don't create PST manifest for golang code
ENTESB-17931	Camel K 1.6.0 Sources contain multiple defects (tech-preview + wrong versions)
ENTESB-19222	AWS Redshift Sink kamelet dependency mvn:com.amazon.redshift:redshift-jdbc42:2.1.0.5 missing in bom
ENTESB-19336	Salesforce Source kamelet: notifyForFields isnt very usable
ENTESB-19344	AWS S3 Streaming upload kamelet: streamingUploadMode probably shouldnt be configurable
ENTESB-19392	CVE-2022-30973 tika-core: incomplete fix for CVE-2022-30126 [rhint-camel-k-1]
ENTESB-19417	Upgrade test to channel 1.8.x fails with "2 replacement chains were found"
ENTESB-19536	Action kamelet tests fail on Unsupported field: unmarshalTypeName
ENTESB-19670	Default maven repositories are overridden when using kamel install
ENTESB-19727	Camel-K 1.8.1.CK1 unaligned versions
ENTESB-19744	Cannot run kameletBinding with the native mode
ENTESB-19830	Wrong snakeyaml dependency in MRRC
ENTESB-19875	Elasticsearch source Kamelet would not work with basic authentication