Update Cluster ID in an existing IraDialer setup

To update an cluster ID in an existing IraDialer setup, Follow the below steps.

Download the Cluster Update script from the below link. 

Give the downloaded file executable permission by running the below command

sudo chmod +x update_clusterid.sh

 Note: change the ownership of the file if required and run with sudo privledges.

Enter the new cluster_id when prompted by the script.
Note: Please make sure to keep the deployment files ready in the machine. The existing deployed files will be deleted from Kubernetes and will have to be manually re-deployed in a sequential manner. 

To make sure the change has taken effect, Please make sure to check the common_config.json located in /usr/local/epi/conf/common_config.json and verify that the new cluster name is in place.

Make sure to download the new sitekey.pem file of the new cluster_id from License.epicode.in and replace the existing sitekey.pem file located in /usr/local/epi/conf directory.

Order in which the YAMLS are to be deployed. 

kubectl apply -f deployments/watcher.yaml
kubectl apply -f deployments/tracker.yaml
kubectl apply -f deployments/cpatracker.yaml
kubectl apply -f deployments/irapass.yaml
kubectl apply -f deployments/collector.yaml
kubectl apply -f deployments/analyser-depl.yaml
kubectl apply -f deployments/iradialer-exporter.yaml
kubectl apply -f deployments/iramonitor.yaml
kubectl apply -f deployments/iradialerweb.yaml
kubectl apply -f deployments/iracpa.yaml
kubectl apply -f deployments/event-dispatcher.yaml

Once the deployment is complete, Make sure all the pods are in the running state and check the latest IraPass log located at /var/log/epi/k8s/ directory and that it has obtained the license successfully. It should look like the image attached below.


Sequentially make sure to check the analyser pod, collector and exporter pod logs as well ( use kubectl logs *pod-name to check the pod logs ) and verify there are no errors.