Before upgrading, ensure that the system is idle, i.e, all agents are logged out of the AgentDesk.
Flush Redis before upgrading
Custom Configuration Strategy
For detailed guidelines on applying environment-specific configurations using custom values.yaml layering,
Refer to the CX Helm Chart Custom Configuration Strategy guide.
-
Update Helm repo
helm repo update expertflow -
Clone the CX repository on the target server
Bash# Create CX-5.13.0 directory from root mkdir CX-5.13.0 # Navigate to CX-5.13.0 cd CX-5.13.0 # Clone the CX-5.13.0 branch of the cim-solution repository git clone -b CX-5.13.0 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git $HOME/CX-5.13.0 # Navigate to the current release /kubernetes cd <current-release>/kubernetes -
Deploy the AgentDesk Helm chart
SQL# Deploy the new chart version using the helm-values/cx-agent-desk-custom-values.yaml helm upgrade --install --namespace expertflow --set global.efCxReleaseName="ef-cx" cx-agent-desk --debug --values helm-values/cx-agent-desk-custom-values.yaml expertflow/agent-desk --version 5.13.0 -
Deploy the Campaigns Helm chart
# Deploy the new chart version using the helm-values/cx-campaigns-custom-values.yaml helm upgrade --install --namespace expertflow --set global.efCxReleaseName="ef-cx" cx-campaigns --debug --values helm-values/cx-campaigns-custom-values.yaml expertflow/campaigns --version 5.13.0 -
Deploy the Core Helm chart
# Deploy the new chart version using the helm-values/ef-cx-custom-values.yaml helm upgrade --install --namespace expertflow --create-namespace ef-cx --debug --values helm-values/ef-cx-custom-values.yaml expertflow/cx --version 5.13.0 -
Deploy the MTT Helm chart
# Deploy the new chart version using the helm-values/mtt-single-custom-values.yaml helm upgrade --install --namespace <tenant-ns> --debug <tenant-id> --values helm-values/mtt-single-custom-values.yaml expertflow/MTT-single --version 5.13.0 -
Deploy the Transflux Helm Chart
git clone -b 5.13.0 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/transflux.git 5.13.0 # Copy the following files to your current directory config/bulk_upload_config_template.yaml to <transflux-current-dir>/config/ # Delete the existing configmaps ‘ef-transflux-config-cm' using the commands: kubectl -n expertflow delete configmap ef-transflux-config-cm # Now re-create the configmap using the following commands from the transflux directory: kubectl -n expertflow create configmap ef-transflux-config-cm --from-file=config # Re-deploy CX-Transflux helm upgrade --install --namespace expertflow --set global.efCxReleaseName="ef-cx" cx-transflux --debug --values helm-values/cx-transflux-custom-values.yaml expertflow/transflux --version 5.13.0
Once the airflow_metadata_cleanup DAG has completed the 1st run, it is required to reclaim the freed space from the DB:
kubectl exec -it -n ef-external ef-postgresql-0 -- psql -U postgres -d airflow -c "
VACUUM (FULL, ANALYZE, VERBOSE) task_instance;
VACUUM (FULL, ANALYZE, VERBOSE) log;
VACUUM (FULL, ANALYZE, VERBOSE) xcom;
VACUUM (FULL, ANALYZE, VERBOSE) job;
VACUUM (FULL, ANALYZE, VERBOSE) dag_run;
"
Then verify the DB size after the cleanup:
kubectl exec -it -n ef-external ef-postgresql-0 -- psql -U postgres -d airflow -c "
SELECT pg_size_pretty(pg_database_size('airflow')) AS db_size;"
-
Deploy the Survey Reports
-
Clone the Repo
# Clone the repo git clone -b CX-5.13.0 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git CX-5.13.0 -
Survey Reports
Bash# Copy CX-5.13.0/kubernetes/external/metabase-reports/metabase_reporting_update_tool/survey/ To <current-active-directory>/external/metabase-reports/metabase_reporting_update_tool/ cd <current-active-directory>/external/metabase-reports/metabase_reporting_update_tool/ python3 metabase_import.py https://FQDN/metabase/api/ "email" "password" "database" "survey" "Collection Name"
-