Chapter 4. Skupper Camel Integration Example

• A Twitter Camel integration that searches in the Twitter feed for results containing the word skupper (public).
• A PostgreSQL Camel sink that receives the data from the Twitter Camel router and sends it to the database (public).
• A PostgreSQL database that contains the results (private).
• A Telegram Camel integration that polls the database and sends the results to a Telegram channel (public).

Prerequisites

• The kubectl command-line tool, version 1.15 or later
• The skupper command-line tool, the latest version
• Access to at least one Kubernetes cluster, from any provider you choose

• Kamel installation to deploy the Camel integrations per namespace.

  kamel install

  Copy to Clipboard Toggle word wrap
• A Twitter Developer Account in order to use the Twiter API (you need to add the credentials in config.properties file)
• Create a Telegram Bot and Channel to publish messages (you need to add the credentials in config.properties file)

Procedure

• Configure separate console sessions
• Access your clusters
• Set up your namespaces
• Install Skupper in your namespaces
• Check the status of your namespaces
• Link your namespaces
• Deploy and expose the database in the private cluster
• Create the table to store the tweets
• Deploy Twitter Camel Integration in the public cluster
• Deploy Telegram Camel integration in the public cluster

• Test the application

  1. Configure separate console sessions

     Skupper is designed for use with multiple namespaces, typically on different clusters. The skupper command uses your kubeconfig and current context to select the namespace where it operates.

     Your kubeconfig is stored in a file in your home directory. The skupper and kubectl commands use the KUBECONFIG environment variable to locate it.

     A single kubeconfig supports only one active context per user. Since you will be using multiple contexts at once in this exercise, you need to create distinct kubeconfigs.

     Start a console session for each of your namespaces. Set the KUBECONFIG environment variable to a different path in each session.

     Console for private1:

     export KUBECONFIG=~/.kube/config-private1

     Copy to Clipboard Toggle word wrap

     Console for public1:

     export KUBECONFIG=~/.kube/config-public1

     Copy to Clipboard Toggle word wrap

     Console for public2:

     export KUBECONFIG=~/.kube/config-public2

     Copy to Clipboard Toggle word wrap

  2. Access your clusters

     The methods for accessing your clusters vary by Kubernetes provider. Find the instructions for your chosen providers and use them to authenticate and configure access for each console session. See the following links for more information:

     • Amazon Elastic Kubernetes Service (EKS)
     • Azure Kubernetes Service (AKS)
     • Google Kubernetes Engine (GKE)
     • IBM Kubernetes Service
     • OpenShift
     • More providers

  3. Set up your namespaces

     Use kubectl create namespace to create the namespaces you wish to use (or use existing namespaces). Use kubectl config set-context to set the current namespace for each session.

     Console for private1:

     kubectl create namespace private1
     kubectl config set-context --current --namespace private1

     Copy to Clipboard Toggle word wrap

     Console for public1:

     kubectl create namespace public1
     kubectl config set-context --current --namespace public1

     Copy to Clipboard Toggle word wrap

     Console for public2:

     kubectl create namespace public2
     kubectl config set-context --current --namespace public2

     Copy to Clipboard Toggle word wrap

  4. Install Skupper in your namespaces

     The skupper init command installs the Skupper router and service controller in the current namespace. Run the skupper init command in each namespace.

     Console for private1:

     skupper init

     Copy to Clipboard Toggle word wrap

     Console for public1:

     skupper init

     Copy to Clipboard Toggle word wrap

     Console for public2:

     skupper init

     Copy to Clipboard Toggle word wrap

  5. Check the status of your namespaces

     Use skupper status in each console to check that Skupper is installed.

     Console for private1:

     skupper status

     Copy to Clipboard Toggle word wrap

     Console for public1:

     skupper status

     Copy to Clipboard Toggle word wrap

     Console for public2:

     skupper status

     Copy to Clipboard Toggle word wrap

     You should see output like this for each namespace:

     Skupper is enabled for namespace "<namespace>" in interior mode. It is not connected to any other sites. It has no exposed services.
     The site console url is: http://<address>:8080
     The credentials for internal console-auth mode are held in secret: 'skupper-console-users'

     Copy to Clipboard Toggle word wrap

     As you move through the steps below, you can use skupper status at any time to check your progress.

  6. Link your namespaces

     Creating a link requires use of two skupper commands in conjunction, skupper token create and skupper link create.

     The skupper token create command generates a secret token that signifies permission to create a link. The token also carries the link details. Then, in a remote namespace, The skupper link create command uses the token to create a link to the namespace that generated it.

     Note

     The link token is truly a secret. Anyone who has the token can link to your namespace. Make sure that only those you trust have access to it.

     First, use skupper token create in one namespace to generate the token. Then, use skupper link create in the other to create a link.

     Console for public1:

     skupper token create ~/public1.token --uses 2

     Copy to Clipboard Toggle word wrap

     Console for public2:

     skupper link create ~/public1.token
     skupper link status --wait 30
     skupper token create ~/public2.token

     Copy to Clipboard Toggle word wrap

     Console for private1:

     skupper link create ~/public1.token
     skupper link create ~/public2.token
     skupper link status --wait 30

     Copy to Clipboard Toggle word wrap

     If your console sessions are on different machines, you may need to use scp or a similar tool to transfer the token.

  7. Deploy and expose the database in the private cluster

     Use kubectl apply to deploy the database in private1. Then expose the deployment.

     Console for private1:

     kubectl create -f src/main/resources/database/postgres-svc.yaml
     skupper expose deployment postgres --address postgres --port 5432 -n private1

     Copy to Clipboard Toggle word wrap

  8. Create the table to store the tweets

     Console for private1:

     kubectl run pg-shell -i --tty --image quay.io/skupper/simple-pg --env="PGUSER=postgresadmin" --env="PGPASSWORD=admin123" --env="PGHOST=$(kubectl get service postgres -o=jsonpath='{.spec.clusterIP}')" -- bash
     psql --dbname=postgresdb
     CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
     CREATE TABLE tw_feedback (id uuid DEFAULT uuid_generatev4 (),sigthning VARCHAR(255),created TIMESTAMP default CURRENTTIMESTAMP,PRIMARY KEY(id));

     Copy to Clipboard Toggle word wrap

  9. Deploy Twitter Camel Integration in the public cluster

     First, we need to deploy the TwitterRoute component in Kubernetes by using kamel. This component will poll Twitter every 5000 ms for tweets that include the word skupper. Subsequently, it will send the results to the postgresql-sink, that should be installed in the same cluster as well. The kamelet sink will insert the results in the postgreSQL database.

     Console for public1:

     src/main/resources/scripts/setUpPublic1Cluster.sh

     Copy to Clipboard Toggle word wrap

  10. Deploy Telegram Camel integration in the public cluster

      In this step we will install the secret in Kubernetes that contains the database credentials, in order to be used by the TelegramRoute component. After that we will deploy TelegramRoute using kamel in the Kubernetes cluster. This component will poll the database every 3 seconds and gather the results inserted during the last 3 seconds.

      Console for public2:

      src/main/resources/scripts/setUpPublic2Cluster.sh

      Copy to Clipboard Toggle word wrap

  11. Test the application

      To be able to see the whole flow at work, you need to post a tweet containing the word skupper and after that you will see a new message in the Telegram channel with the title New feedback about Skupper

      Console for private1:

      kubectl attach pg-shell -c pg-shell -i -t
      psql --dbname=postgresdb
      SELECT * FROM twfeedback;

      Copy to Clipboard Toggle word wrap

      Sample output:

      id                                    | sigthning       |          created
      --------------------------------------+-----------------+----------------------------
       95655229-747a-4787-8133-923ef0a1b2ca | Testing skupper | 2022-03-10 19:35:08.412542

      Copy to Clipboard Toggle word wrap

      Console for public1:

      kamel logs twitter-route

      Copy to Clipboard Toggle word wrap

      Sample output:

      "[1] 2022-03-10 19:35:08,397 INFO  [postgresql-sink-1] (Camel (camel-1) thread #0 - twitter-search://skupper) Testing skupper"

      Copy to Clipboard Toggle word wrap