More Camel K resources available on the awesome-camel-k repository

Run Knative and Camel K on minikube

This repository contains the instructions to install and run knative, istio, camel k on minikube.

Create a minikube cluster

minikube start --driver=virtualbox \
    --addons=dashboard \
    --addons=ingress \
    --addons=metrics-server \
    --addons=registry \
    --cpus 4

Install Knative Resources and Components

kubectl apply --filename https://github.com/knative/serving/releases/download/v0.21.0/serving-crds.yaml

kubectl apply --filename https://github.com/knative/serving/releases/download/v0.21.0/serving-core.yaml

Install Istio

Download and install the istioctl following the instructions here

Install istio without sidecar injection :

istioctl install -f istio/install.yml

kubectl label namespace knative-serving istio-injection=enabled

Set peer authentication to permissive on knative-serving namespace :

kubectl apply -f istio/permissive.yml

Install Knative Istio Controller

kubectl apply --filename https://github.com/knative/net-istio/releases/download/v0.21.0/release.yaml

Check PODs are running :

kubectl get pods --namespace knative-serving

It should look like this :

$ kubectl get pods --namespace knative-serving
NAME                                READY   STATUS    RESTARTS   AGE
activator-86956bbd6f-jz8jc          1/1     Running   0          5m12s
autoscaler-54cbd576f6-fc9kw         1/1     Running   0          5m12s
controller-79c9cccd6f-5l4f8         1/1     Running   0          5m12s
istio-webhook-56748b47-2rpvw        1/1     Running   0          4m3s
networking-istio-5db557d5c4-djp8m   1/1     Running   0          4m3s
webhook-5fd484cf4-z8zp5             1/1     Running   0          5m12s

Install Knative Eventing Resources and Components

kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/eventing-crds.yaml

kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/eventing-core.yaml

Install a default InMemory channel

kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/in-memory-channel.yaml

And a default broker

kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/mt-channel-broker.yaml

Check the Knative Eventing pods

kubectl get pods --namespace knative-eventing

And it should look like the following

$ kubectl get pods --namespace knative-eventing
NAME                                   READY   STATUS    RESTARTS   AGE
eventing-controller-d666b4657-tbrxf    1/1     Running   0          3m34s
eventing-webhook-778b6b8cf4-hj8cs      1/1     Running   0          3m34s
eventing-webhook-778b6b8cf4-qhdvh      1/1     Running   0          2m2s
imc-controller-5f4bdf86cf-znfjj        1/1     Running   0          3m31s
imc-dispatcher-54bfc97957-xk2tz        1/1     Running   0          3m31s
mt-broker-controller-ff696f56c-c9sjb   1/1     Running   0          3m30s
mt-broker-filter-d44b776d8-qg4pt       1/1     Running   0          3m30s
mt-broker-ingress-6c8487b74c-fw6jb     1/1     Running   0          3m30s

Install Camel K

Download the Camel K CLI tool following the instructions here

Install camel k on the kubernetes cluster

kamel install --force

Check the operator is up and running

$ kubectl get po
NAME                                READY   STATUS    RESTARTS   AGE
camel-k-operator-57bbcbd6dc-49nl5   1/1     Running   0          2m22s

Configure the default broker

kubectl apply -f knative/broker.yml

Run integrations

Run a test integration that just prints a line to the console logs :

kamel run integrations/hello.groovy --dev

After some time, the integration will run and will start to log outputs

...
[1] 2020-12-31 11:47:11,624 INFO  [io.quarkus] (main) Profile prod activated.
[1] 2020-12-31 11:47:11,625 INFO  [io.quarkus] (main) Installed features: [camel-bean, camel-core, camel-endpointdsl, camel-k-core, camel-k-loader-groovy, camel-k-runtime, camel-log, camel-main, camel-support-common, camel-timer, cdi]
[1] 2020-12-31 11:47:12,634 INFO  [info] (Camel (camel-1) thread #0 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world from Camel K]
[1] 2020-12-31 11:47:15,619 INFO  [info] (Camel (camel-1) thread #0 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world from Camel K]

Now, let's run an integration that will listen to cloudevents of type camel in the default broker :

kamel run integrations/kn.groovy --dev

The integration will start and remain idle, waiting for events to arrive :

[1] 2020-12-31 11:49:11,634 INFO  [io.quarkus] (main) Profile prod activated.
[1] 2020-12-31 11:49:11,634 INFO  [io.quarkus] (main) Installed features: [camel-attachments, camel-bean, camel-core, camel-endpointdsl, camel-k-core, camel-k-knative, camel-k-knative-consumer, camel-k-loader-groovy, camel-k-runtime, camel-log, camel-main, camel-platform-http, camel-support-common, cdi, mutiny, smallrye-context-propagation, vertx, vertx-web]
Condition "Ready" is "True" for Integration kn

To send events on the broker, we will deploy a curl pod, attach to it and send events with curl.

Open a new terminal window.

Deploy the curl pod :

kubectl apply -f pods/curl.yml

Attach to the container

kubectl attach curl -it

And send a cloud event from it with the camel type :

curl -v "http://broker-ingress.knative-eventing.svc.cluster.local/default/default" \
  -X POST \
  -H "ce-Id: 2222-ddd" \
  -H "ce-Specversion: 1.0" \
  -H "ce-Type: camel" \
  -H "content-type: application/json" \
  -d '{"firstName":"John", "lastName":"Doe"}'

And you should see the event logged from the integration :

[2] 2020-12-31 11:52:57,190 INFO  [io.quarkus] (main) Installed features: [camel-attachments, camel-bean, camel-core, camel-endpointdsl, camel-k-core, camel-k-knative, camel-k-knative-consumer, camel-k-loader-groovy, camel-k-runtime, camel-log, camel-main, camel-platform-http, camel-support-common, cdi, mutiny, smallrye-context-propagation, vertx, vertx-web]
[2] 2020-12-31 11:52:57,309 INFO  [info] (vert.x-worker-thread-0) Exchange[ExchangePattern: InOnly, BodyType: byte[], Body: {"firstName":"John", "lastName":"Doe"}]

Using Kamelets

This repository contains the same example as in the Camel K docs for the Telegram kamelet but instead make use of knative eventing without manually creating channels.

Deploy the telegram kamelet :

kubectl apply -f kamelets/kamelet-telegram.yml

Create the bot token secret :

kubectl create secret generic telegram --from-literal=BOT_TOKEN=XXXXXXXXX

Label the secret so it will be picked up by the integration

kubectl label secret telegram camel.apache.org/kamelet=telegram-text-source

Run the kamelet binding ( which will create an integration under the hood )

kubectl apply -f kamelets/kamelet-binding.yml

Inspect the logs of the integration :

kamel log telegram-text-source-to-channel

[3] 2020-12-31 13:47:06,625 INFO  [io.quarkus] (main) Profile prod activated.
[3] 2020-12-31 13:47:06,626 INFO  [io.quarkus] (main) Installed features: [camel-attachments, camel-bean, camel-core, camel-direct, camel-endpointdsl, camel-k-core, camel-k-kamelet, camel-k-knative, camel-k-knative-producer, camel-k-loader-yaml, camel-k-runtime, camel-main, camel-platform-http, camel-support-ahc, camel-support-common, camel-support-webhook, camel-telegram, cdi, mutiny, smallrye-context-propagation, vertx, vertx-web]
[3] 2020-12-31 13:47:14,464 INFO  [telegram-text-source-695F2126EC562F3-0000000000000000] (Camel (camel-1) thread #0 - telegram://bots) john
[3] 2020-12-31 13:47:14,466 INFO  [telegram-text-source-695F2126EC562F3-0000000000000000] (Camel (camel-1) thread #0 - telegram://bots) {"firstName": "john", "lastName": "Joe"}

The logs you're seeing here are the logs of the kamelet itself and to verify events are received by the cloudevents consumer, just run the kn integration again :

kamel run integrations/kn.groovy --dev

[1] 2020-12-31 13:59:02,155 INFO  [io.quarkus] (main) Installed features: [camel-attachments, camel-bean, camel-core, camel-endpointdsl, camel-k-core, camel-k-knative, camel-k-knative-consumer, camel-k-loader-groovy, camel-k-runtime, camel-log, camel-main, camel-platform-http, camel-support-common, cdi, mutiny, smallrye-context-propagation, vertx, vertx-web]
Condition "Ready" is "True" for Integration kn
[1] 2020-12-31 13:59:32,198 INFO  [info] (vert.x-worker-thread-0) Exchange[ExchangePattern: InOnly, BodyType: byte[], Body: {"firstName": "bot", "lastName": "Joe"}]

---