Chapter 1. Overview of Kamelets

Procedure

1. In the OpenShift Container Platform web console, log in by using an account with cluster administrator privileges.

2. Create a new OpenShift project:

   1. In the left navigation menu, click Home > Project > Create Project.
   2. Enter a project name, for example, my-camel-k-project, and then click Create.
3. In the left navigation menu, click Operators > OperatorHub.
4. In the Filter by keyword text box, type Camel K and then click the Red Hat Integration - Camel K Operator card.
5. Read the information about the operator and then click Install. The Operator installation page opens.

6. Select the following subscription settings:

   • Update Channel > 1.4.x
   • Installation Mode > A specific namespace on the cluster > my-camel-k-project

   • Approval Strategy > Automatic

     Note

     The Installation mode > All namespaces on the cluster and Approval Strategy > Manual settings are also available if required by your environment.

7. Click Install, and then wait a few moments until the Camel K Operator is ready for use.

8. Download and install the Camel K CLI tool:

   1. From the Help menu (?) at the top of the OpenShift web console, select Command line tools.
   2. Scroll down to the kamel - Red Hat Integration - Camel K - Command Line Interface section.
   3. Click the link to download the binary for your local operating system (Linux, Mac, Windows).
   4. Unzip and install the CLI in your system path.

   5. To verify that you can access the Kamel K CLI, open a command window and then type the following:

      kamel --help

      This command shows information about Camel K CLI commands.

1. In a Terminal window, login to your OpenShift cluster.

2. Viewing the list of available kamelets depends on how the Camel K operator was installed (in a specific namespace or cluster-mode):

   • If the Camel K operator is installed in cluster-mode, use this command to view the available kamelets:

     oc get kamelet -n openshift-operators

   • If the Camel K operator is installed in a specific namespace:

     1. Open a project in which the Camel K operator is installed.

        oc project <camelk-project>

        For example, if the Camel K operator is installed in the my-camel-k-project project:

        oc project my-camel-k-project

     2. Run the following command:

        oc get kamelets

Procedure

1. Login to your OpenShift cluster.

2. Open your working project where the Camel K operator is installed. If you installed the Camel K operator in cluster-mode, it is available to any project on the cluster.

   For example, to open an existing project named my-camel-k-project:

   oc project my-camel-k-project

3. Create a new KameletBinding resource:

   1. In an editor of your choice, create a YAML file with the following structure:

      apiVersion: camel.apache.org/v1alpha1
      kind: KameletBinding
      metadata:
        name:
      spec:
        source:
        sink:

   2. Add a name for the kamelet binding.

      For this example, the name is coffee-to-log because the binding connects the coffee-source kamelet to the log-sink kamelet.

      apiVersion: camel.apache.org/v1alpha1
      kind: KameletBinding
      metadata:
        name: coffee-to-log
      spec:
        source:
        sink:

4. Specify the source kamelet (for example, coffee-source) and configure any parameters for the kamelet.

   Note: For this example, the parameter is defined within the kamelet binding’s YAML file. Alternatively, you can configure a kamelet’s parameters in a property file, ConfigMap, or Secret as described in Configuring kamelet instance parameters.

   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: coffee-to-log
   spec:
     source:
       ref
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: coffee-source
       properties:
         period: 5000
     sink:

5. Specify the sink kamelet (for example, log-sink) and configure any parameters for the kamelet. The example log-sink kamelet does not have any required parameters.

   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: coffee-to-log
   spec:
     source:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: coffee-source
       properties:
         period: 5000
     sink:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: log-sink

6. Save the YAML file (for example, coffee-to-log.yaml).

7. Add the KameletBinding as a resource to your OpenShift namespace:

   oc apply -f <kamelet>.yaml

   For example:

   oc apply -f coffee-to-log.yaml

   The Camel K operator generates and runs a Camel K integration by using the KameletBinding resource.

8. To see the status of the KameletBinding:

   oc get kameletbindings

9. To see the status of the corresponding integration: oc get integrations

10. To view the output:

    • To view the logs from the command line, open a Terminal window and then type the following command:

      kamel log <integration-name>

      For example, if the integration name is coffee-to-log, use this command:

      kamel log coffee-to-log

    • To view the logs from OpenShift web console:

      1. Select Workloads > Pods.

      2. Click the name of the Camel K integration’s pod, and then click Logs.

         You should see a list of coffee events similar to the following example:

         INFO  [log-sink-E80C5C904418150-0000000000000001] (Camel (camel-1) thread #0 - timer://tick) {"id":7259,"uid":"a4ecb7c2-05b8-4a49-b0d2-d1e8db5bc5e2","blend_name":"Postmodern Symphony","origin":"Huila, Colombia","variety":"Kona","notes":"delicate, chewy, black currant, red apple, star fruit","intensifier":"balanced"}

11. To stop the integration, delete the kamelet binding:

    oc delete kameletbindings/<kameletbinding-name>

    For example:

    oc delete kameletbindings/coffee-to-log

Procedure

1. Open a KameletBinding file in an editor.

   For example, here are the contents of the coffee-to-log.yaml file:

   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: coffee-to-log
   spec:
     source:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: coffee-source
       properties:
         period: 5000
     sink:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: log-sink

2. Add an integration section above the source section and provide the following Builder trait configuration property (as required by the predicate-filter-action kamelet):

   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: coffee-to-log
   spec:
     integration:
            traits:
              builder:
                configuration:
                  properties:
                    - "quarkus.arc.unremovable- types=com.fasterxml.jackson.databind.ObjectMapper"
     source:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: coffee-source
       properties:
         period: 5000
     sink:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: log-sink

3. Add a steps section, between the source and sink sections and define the action kamelet. For example:

   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: coffee-to-log
     spec:
       integration:
              traits:
                builder:
                  configuration:
                    properties:
                      - "quarkus.arc.unremovable-types=com.fasterxml.jackson.databind.ObjectMapper"
     source:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: coffee-source
       properties:
         period: 5000
     steps:
     - ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: json-deserialize-action
     - ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: predicate-filter-action
       properties:
         expression: "@.intensifier =~ /.*deep/"
     - ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: json-serialize-action
     sink:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: log-sink

4. Save your changes.

5. Update the KameletBinding resource:

   oc apply -f coffee-to-log.yaml

   The Camel K operator re-generates and runs the CamelK integration that it generates based upon the updated KameletBinding resource.

6. To see the status of the kamelet binding:

   oc get kameletbindings

7. To see the status of its corresponding integration:

   oc get integrations

8. To view the log file output:

   1. Get the pod name for the integration:

      oc get pods

   2. View the log for the integration’s pod:

      oc logs <podname of the integration>

      For example, if the pod name is example-7885bdb9-84ht8:

      oc logs example-7885bdb9-84ht8

9. To stop the integration, delete the kamelet binding:

   oc delete kameletbindings/<kameletbinding-name>

   For example:

   oc delete kameletbindings/coffee-to-log

1. Open a KameletBinding YAML file in an editor.

2. Add an error handler section to the spec section, after the sink definition:

   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: example-kamelet-binding
   spec:
     source:
      ...
     sink:
      ...
     errorHandler: ...

   For example, in the coffee-to-log kamelet binding, specify the maximum number of times an error is sent to the log file by adding a log error handler:

   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: coffee-to-log
   spec:
     source:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: coffee-source
       properties:
         period: 5000
     sink:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: log-sink
     errorHandler: log: parameters: maximumRedeliveries: 3

3. Save your file.