In this patch release, the Kubernetes cron job functionality has been successfully incorporated.
Remove all existing configmaps and deployment of
reporting-connector before proceeding with the instructions in this guide
Follow the below commands to delete deployment and configmaps of
kubectl delete -f cim-solution/kubernetes/cim/Deployments/ef-reporting-connector-deployment.yaml -n expertflow
kubectl -n expertflow delete configmap ef-reporting-connector-conf
kubectl -n expertflow delete configmap ef-reporting-connector-cron
Delete the following files if exists
Configure reporting components connection with MySQL over SSL.
Optional:This patch 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.
Update the "fqdn, browser_language, connection_type and Database server connection parameters" in the file
Create a ConfigMap for the reporting connector configuration file.
kubectl -n expertflow create configmap ef-reporting-connector-conf --from-file=cim-solution/kubernetes/pre-deployment/reportingConnector/reporting-connector.conf
Download this file : ef-reporting-connector-cron.yaml and place it in
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.
Apply the configuration defined in this file by the below command.
kubectl apply -f cim-solution/kubernetes/pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml -n expertflow
These steps will effectively deploy the Kubernetes cron job for the reporting connector in the specified namespace expertflow.