Skip to main content
Skip table of contents

Deployment Guide - Kubernetes Cron Job For Custom Connector

In this release, the Kubernetes cron job functionality has been successfully incorporated.

Remove all existing configmaps and deployment of custom-connector before proceeding with the instructions in this guide

Follow the below commands to delete deployment and configmaps of custom-connector.

JS
kubectl -n ef-cti delete -f customConnector/ef-reporting-connector-cron.yaml
kubectl -n ef-cti delete configmap ef-reporting-connector-conf


Delete the following files if exists

  1. rm customConnector/reporting-connector.conf

  2. rm customConnector/ef-reporting-connector-cron.yaml

Configure reporting components connection with MySQL over SSL.

This release, support the reporting components connection with MySQL on SSL. To configure the reporting connector with MySQL over SSL, consult this guide. To configure Superset with MySQL over SSL, refer to the Superset SSL Configuration section of this guide.
To deploy the Kubernetes cron job for the reporting connector, follow these deployment steps using the provided commands.

If you are using TLS enabled external components (mongo etc), copy the tls secrets to ef-cti namespace before deploying the custom connector using the following commands:-

CODE
kubectl get secret mongo-mongodb-ca -n ef-external  -o yaml | sed 's/namespace: ef-external/namespace: ef-cti/' | kubectl create -f -
  1. Download this file: ef-connection-env-configmap.yaml and place it in customConnector/directory.

  2. Update the keystore and trustore passwords and create a ConfigMap from the ef-connection-env configmap file.

    CODE
    kubectl -n ef-cti apply -f customConnector/ef-connection-env-configmap.yaml

  3. Download this file : reporting-connector.conf and place it incustomConnector/directory.

Update the "fqdn, browser_language, and Database server connection parameters"  in the file customConnector/custom-connector.conf

  1. Create a ConfigMap for the custom connector configuration file.

CODE
kubectl -n ef-cti create configmap ef-reporting-connector-conf --from-file=customConnector/reporting-connector.conf

  1. Download this file : ef-imagePullSecret-ef-cti.yamland place it incustomConnector/directory.

  2. Run the following commands for applying ImagePullSecrets of Expertflow CX images for ef-cti namespace.

    CODE
    kubectl apply -f customConnector/ef-imagePullSecret-ef-cti.yaml
  3. Download this file : ef-reporting-connector-cron.yaml and place it incustomConnector/directory.

  4. You can specify the schedule for your cron job by setting the parameter schedule: "*/5 * * * *" in the above downloaded yaml file where the value '5' is a default time which corresponds to the interval in minutes. Replace the value by replacing '5' with your specified minutes.

  5. Apply the configuration defined in this file by the below command.

JS
kubectl -n ef-cti apply -f customConnector/ef-reporting-connector-cron.yaml

These steps will effectively deploy the Kubernetes cron job for the custom connector in the specified namespace ef-cti.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.