Expertflow CX Upgrade Guide CX-4.3 to CX-4.3_f-CIM-8242
The upgrade must be done while the system is inactive. Active state of the system is removed as the application's Object model is changed.
Remove any active state of the system.
BASH# Open the redis shell kubectl exec -n ef-external -it redis-master-0 -- redis-cli -a Expertflow123 # Inside the redis shell flushall # ctrl + c (to get out of the shell)
Remove the current solution deployment
BASH# Navigate to the following folder of the existing release i.e. CX-4.3 cd cim-solution/kubernetes kubectl delete -f cim/StatefulSet/ kubectl delete -f cim/ConfigMaps/ kubectl delete -f cim/Deployments/ kubectl delete -f cim/Services/ #if you are using nginx (RKE) kubectl delete -f cim/Ingresses/nginx #if you are using traefik kubectl delete -f cim/Ingresses/traefik
Make backup of the current cim-solution folder.
BASH# Navigate to the parent directory where the cim-solution folder is placed and run: mv cim-solution cim-solution-old
Clone the CX-4.3 release from gitlab and place it on target server.
BASHgit clone -b CX-4.3_f-CIM-8242 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git
Navigate to the
cim-solution/kubernetes
directory in the newly cloned release.BASHcd cim-solution/kubernetes
Update the FQDN.
BASH# Change the <FQDN> in the below given commands to your actual FQDN. sed -i 's/devops[0-9]*.ef.com/<FQDN>/g' cim/ConfigMaps/* pre-deployment/grafana/* pre-deployment/keycloak/* cim/Ingresses/traefik/* cim/Ingresses/nginx/* sed -i -e 's@value: http://devops.ef.com/bot-framework@value: https://<FQDN>/bot-framework@' external/rasa-x/values-small.yaml sed -i -e 's@value: https://devops.ef.com@value: https://<FQDN>@' external/rasa-x/values-small.yaml
Update the solution deployment
BASHkubectl apply -f cim/ConfigMaps/ kubectl apply -f cim/StatefulSet/ kubectl apply -f cim/Services/ kubectl apply -f cim/Deployments/ #if you are using nginx kubectl apply -f cim/Ingresses/nginx #if you are using traefik kubectl apply -f cim/Ingresses/traefik
Note
In case any of the deployment is giving exception related to MONGO DB URL or PORT, then please try to update the "ImagePullPolicy" value of that deployment from "IfNotPresent" to "Always".
If every thing worked fine until this point, you may remove the cim-solution-old directory
# Navigate to the parent directory and run
rm -rf cim-solution-old
Configurations
- To configure Instagram Connector
Instagram Connector Configuration & Deployment Guide